Hacker News new | past | comments | ask | show | jobs | submit login

I've built a number of teams, and have repeatedly had the fortune of anchoring the back-end with a senior engineer over age 50. Experience matters, and it helps the entire team from a morale, design, and process perspective. You don't want to work for someone who doesn't recognize that anyway...

I wish I could be so lucky to attract senior candidates at my current gig; they're hard to come by at a trendy downtown-SF mobile commerce pre-series-A startup. Instead, I'm inundated with fresh code-bootcamp graduates. I'd be much more comfortable hiring those junior developers if I knew they would be able to sit next to a reliable senior teammate...

That said, if you're worried about being hired, start by building something on your own! You'll make yourself much more marketable if you show that you can pick up new technologies and actually release something.




Absolutely. I have had the pleasure of being the junior person sitting next to someone who was close to retirement. His perspective of, "Ok, what are we really trying to do here?" was invaluable. The best teams are always genuinely diverse and seek to really get to know what's special about each other.

One suggestion: don't worry about dating yourself by talking about old tech you once worked on. For some reason the older developers I've worked with take a while to getting around to telling you about the time they wrote LISP in Genera on a Symbolics 3640 for cutting edge CAD/CAM/simulation tools at Boeing in the mid 80s or whatever (such cred!).


100% agree.

Senior engineers with experience are hard as hell to come by. They offer perspective and focus: something that is often needed but hard to find.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: