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

>- desire to grow -- does this person have clear career growth goals. Ideally these are not tied to titles or bossing others around, which are negatives.

Can you give an example of what you WOULD like to see here? There's some selection bias among the kinds of developers who tend to hang out on online technical communities and learn new things, but what IS the right long term goal, and how is this different from "desire to ship"? Sure, I'd like to work on meaningful projects and have enough breadth and depth of knowledge to design and contribute in a meaningful way in them, but if we're being totally honest my career goals are absolutely "make enough money to pay the mortgage, go on the occasional vacation, and save for retirement". I'm not in this to be a rock star who works 100 hours a week for the chance to be a multimillionaire, and I'm not in this to achieve fame in the developer community. I'm in it to get a paycheck doing work that is intellectually stimulating while still having enough free time to do things OTHER than work, but it's long been obvious that you're not allowed to say that in a job interview, so what ARE you looking for people to say?

To put it another way, in the title terms you don't want to discuss, I have no desire to be a principle architect or C*O. I'm perfectly content being a good-to-great senior-level engineer who's a solid team contributor if not in control of everything. I'm on board with your other qualifications - continual learning, adapting, and gaining exposure to new technologies is great - but is there a limit to career growth? Based simply on number of positions in existence, it's impossible for everyone in the field to keep growing and advancing indefinitely.




Well, I ideally like to see some interests that are on the edge of the candidate's current skill-set which indicate that he/she is aware that technology is changing and that we must all plan ahead a bit to remain relevant and employable in 5 years. Not trend-tracking, but deepening and broadening the skill-set.


Why do you care how good a candidate will be at getting a new job after yours?


Because I'm going to be in the game for at least another 30 years and who knows how many opportunities to work together again might exist.

Also, the idea that an employee is a specific cog that will indefinitely fit into the mechanism in the same way is an outdated relic of using a machine as a metaphor for a firm.

While some employees reach limits, others will continue to evolve, particularly those at the beginning of their career. I have not ever been in a position where I prefer a less ambitious/promising candidate out of fear they will leave after a few years, though I know some people in HR look at the world that way.


I've been doing the same work for 15 years. Everything old is new again.

Linus is right, a plus for C is filtering out developers.




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

Search: