undefined | Better HN

0 pointscaskstrength2y ago0 comments

> A few years back I failed an interview because I gave the impression that I didn't know much about full stack web dev. (To be entirely fair, I didn't at the time).

> I have no doubt that I'd have been a productive member of their team within a month.

Did you consider that they might have skipped you not because you were "fuzzy on implementation details" but because you projected that vibe "I don't know much about what you do but I bet I can be ask good as you at it in a month"?

0 comments

epiccoleman2y ago

I don't think I projected that vibe. I knew ahead of time that the architecture interview was going to be the hardest part for me, and made an effort to show that while I had gaps in my knowledge, I wasn't going to be afraid to ask questions and have discussions to make it possible to get work done. I have a bit of an aversion to unearned overconfidence so I like to think that I did not project that in the interview, but obviously I can't experience myself from the interviewers perspective.

When I interview junior candidates, attitude, interest, and capacity for learning are more important to me than specific knowledge.

Anyway though, it was their choice, and I clearly didn't demonstrate what they wanted to see. Not getting that job left me in the right place at the right time for a job that I really love, so... ¯ \ _ ( ツ ) _ / ¯

j / k navigate · click thread line to collapse

0 comments

epiccoleman2y ago

When I interview junior candidates, attitude, interest, and capacity for learning are more important to me than specific knowledge.

j / k navigate · click thread line to collapse