Things I Learned from a Job Hunt for a Senior Engineering Role

Re:Things I Learned from a Job Hunt for a Senior Engineering... by d1zzy on Tuesday April 24, 2018 @02:05PM (#16915005)

I would say that if you know the answers to 100 top coding questions (and understand them, a good interviewer will poke you to determine that) then you are a pretty good coder and you should be hired. Seems working as intended :)

For many tech companies where they get a lot more candidate applications than they have positions for, the goal of the interview process isn't to avoid losing good candidates, it's to not hire bad candidates.

[ Parent | on HN ]

Re:Things I Learned from a Job Hunt for a Senior Engineering... by jaggederest on Tuesday April 24, 2018 @02:38PM (#16915367)

That's like saying that if you can retype The Great Gatsby, then you're a great writer.

So much more goes into software engineering than "Can solve tiny example problems in an examination system"

[ Parent | on HN ]

Re:Things I Learned from a Job Hunt for a Senior Engineering... by d1zzy on Tuesday April 24, 2018 @03:30PM (#16915798)

Like I said, a good interviewer ensures you understand the solutions of those problems (the problem might even be formulated in a different form than the exact form you learned) not just typing out text verbatim. If you do understand the solutions of top 100 coding questions, I think you have a good start. Part of solving the problem in an interview will also be being able to code, so it's also testing your coding ability in a given programming language.

True that software engineering is more than that, but those other things largely depend on in-house company processes, tools and policies so you would learn them afterwards.

[ Parent | on HN ]