Companies that ask, “What do you want to do?”
The question comes in the form of, "What are you looking for?" or "What do you want to do here, ideally?"
I find this question incredibly difficult to answer when interviewing with startups for engineering positions. It seems incredibly rhetorical. Obviously if I could do whatever I want I wouldn't be applying for jobs in the first place!
It seems like a trick question. Am I really supposed to say, "I'm looking to get paid to program. That's why I applied here and am being interviewed now."
4 comments
[ 0.22 ms ] story [ 21.5 ms ] threadI also ask this because I want to know if you are a curious, growing, learning organism. We want those. We don't want 9 to 5 people. Tell the truth. Why start off lying?
The truth will come out soon enough. Why hang out for a few weeks and get bounced because of a wrong fit? It's bad for everyone.
But then that's our shop. We do it our way. In Dilbertville it is probably different. But you get to choose your life, so why not do it right?
EDIT: if you answered me "I like programming. You're hiring programmers" and you showed me you really did like it, that would be a winning answer in my book. I hire tax professionals. Someone who says they really really like the hard core "work out the numbers" paperwork would be exactly what I want. Or someone who loves to figure out seemingly intractable problems.
So I think your throwaway answer is probably the best one. Say it with a laugh and then follow up with something that shows you REALLY like programming. Winner.
EDIT: If you are interviewing for a startup, a good answer is that you are excited to be a part of something from the very beginning, and being able to shape it as it grows. If it is an established company you can say you are excited to see how an established player has dealt with the challenges of serving a large customer base, etc.
Here are some things to consider when answering this question:
- What areas of programming do you like? Do you want to work on databases, low level coding, front end web dev stuff, etc.
- Do you like starting things from scratch or would you rather work on adding features to an established code base?
- What type of scheduling do you like? Are you okay with tasks changing rapidly or do you prefer your work schedule to be more planned in advance?
- What size of team do you like to work with? How do you prefer to interact with your other team members?
- Are you hoping to learn from more senior devs? Do you want to move up to take on more responsibility (senior or lead positions)?