Tip of the Day
When you’re asked a coding question, it’s important to remember that you’re not being judged by the code you write on the spot, but by the way you approach the problem. For example, depending on the job you’re applying for, using some known algorithm might be the right approach—or it might not be. What the manager really wants to see is whether you get to that algorithm.
After all, algorithms and patterns are relatively easy to find. There are libraries that implement many of them, and there are textbooks that tell you how to accomplish them in numerous languages. The hard part is knowing when it’s right to use a particular pattern or algorithm.
So you probably won’t be asked, “Can you write a Quicksort algorithm?” Rather, the question might be, “We’re doing a project involving language analysis and want to look at phrase frequency. Can you write a utility that takes a list of phrases and orders them according to how frequently they’re used?”
A good answer will probably involve using a Quicksort implementation. In this case, what the manager’s most interested in is whether you recognize that. She’s looking for things like how you structure the code, how you approach the problem and what patterns you choose to apply.
Coding questions aren’t trick questions. They’re opportunities for you to show the hiring manager how you think.
- Watch a Cisco Manager Conduct a Whiteboard Test
- 3 Interview Questions for Scrum Masters
- 4 Interview Questions for DevOps Engineers