I’ve heard technical interviews are just as much about seeing how you approach a problem as they are about you knowing the answer beforehand. But apparently seeing what I do and don’t need to google is not included in that sentiment.
They’re usually testing your problem solving skills rather than whether you’ve memorized a particular question - for example, how you approach the problem, how you break it down, etc. Having a good approach to problem solving in general is way more useful than memorizing common programming problems.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
This was me last week during an interview…
I’ve heard technical interviews are just as much about seeing how you approach a problem as they are about you knowing the answer beforehand. But apparently seeing what I do and don’t need to google is not included in that sentiment.
I’m usually trying to find out if the person will try to BS me, or if they will admit when they don’t know.
They’re usually testing your problem solving skills rather than whether you’ve memorized a particular question - for example, how you approach the problem, how you break it down, etc. Having a good approach to problem solving in general is way more useful than memorizing common programming problems.