Interviews are always hard. It’s especially hard if we have to get technical and solve problems on the fly with code.
In this article, we’ll look at some tips to get good at interviews and nail them.
Get Good at Least One Language
Getting good at one language we don’t have to worry about language syntax in technical interviews.
Although many will allow pseudocode, we still have to know basic syntaxes like loops and how to create objects and hashes.
Therefore, we should just practice coding with one language until it’s muscle memory.
Books like Clean Code and The Mythical Man-Month are always good reads so that we can write clean code and answer design problems that may be asked in technical interviews.
At least we’ll know enough to talk about something in them to make us sound more knowledgable.
Study Trivia Questions
There’re lots of trivia questions that interviewers may ask. They include things like functions that are in a language’s standard library and trick questions about the language.
However, they still linger today, so that someone may still ask about them.
Multiple Practice Projects
We need to practice with projects so that we know what building real apps are like in a job.
They should do things like a real business app would do like calculations and saving things to a database.
There’re plenty of app ideas that we can use to build practice apps with, so we just have to start building with our favorite language and libraries and frameworks to need it.
Also, we should write some tests so that we’re familiar with writing automated tests and we can even should those off to interviewers to show how much we care about writing software.
Then we can host them all in the cloud so that people can see them when we show them off to people.
Learn About What the Company is Doing
We often get asked about what the company we’re interviewing for does. Therefore, we should know what they do before we go into an interview.
This is basic knowledge so we should definitely before going in.
Travel to Interview Early
We should go to the interview location early to reduce the chance that anything bad like traffic jams or bus delays make us late.
Then we wait until around 15 minutes before the interview starts before going into the office so that we won’t be waiting in the workplace for too long.
Start a Conversation
Nobody likes a boring person, so we should start some conversation with the interviewer so that we have a 2-way dialog.
Having silence isn’t good as it makes for an awkward presence. Keep silent doesn’t bode well for how we’ll fit on the team.
If we have questions, we should ask. However, we should probably leave the pay and benefits questions until we get an offer. Since getting an offer is far from a sure thing, we should put those until we actually get an offer.
However, anything else is pretty much fair. We may ask about things like the development process, how code is managed, length of sprints, project timelines, etc.
Showcase Non-Technical Skills
Technical and non-technical skills are equally important. Soft skills is a must-have, so we should show them to our interviewers.
Also, it’s good for interviewers to know that we may potentially fit in their team.
We should think about our soft skills, in addition to our technical skills. Whether the interviewers choose us or not probably depends on both technical and soft skills.
Soft skills include things like communication and thinking, which we can show to interviewers in an interview readily.
Practicing our technical skills with projects and sites like LeetCode and Hackerrank is probably a good idea before an interview.
Also, we should be good at our soft skills as well. Skills like communication and thinking are great assets.
We should have lively and not awkward conversations.