I hope that the below tips would be useful for you and you’ll rock your interview!
Before the technical interview:
1. Your technical interview will be (most probably) after the meeting with a Recruiter / Talent Sourcer, so use this opportunity to ask him/her what you can expect during the technical part:
- Who will be interviewing you (is this technical person / Software Engineer from the team you want to work in?)
- How long will the interview last?
- Will it be only the theoretical part (questions) or you can expect “live coding” (if yes, in what programming language can you write your solution? Can you use your IDE?)
- Should you review any additional materials?
- Additional questions – you might be interested in knowing:
– What are the next steps in the recruitment process?
– Will I receive some materials from you so I can prepare?
– How my work will look like?
– How many Engineers are on this team? Will I work only with them or maybe with PMs, Designers, etc?
– What technology stack do you use?
– Do you offer flexible working hours?
– How does a career path look like?
& more. If you forgot to ask your questions, you should always have an option to get back to Recruiter / Talent Sourcer or ask them during the next steps
- Make sure to choose the most convenient time for a technical interview (the best time is before/after working hours when you’ll be at home and nobody will disturb you).
2. Practice, practice, practice…
- Review all the additional information you’ve received. If you have asked for it and still didn’t receive any, ask yourself do you want to continue with interviewing (for me it would be a “red flag” and I’d think twice before going forward). If you want to proceed, visit e.g., the glassdoor.com website, where you can find questions that may appear during the interview.
- Practice your coding skills – no matter if you’ve got 1+ or 10+ years of experience as a Developer, it’s always good to take some time and prepare (especially if you know that you’ll be asked to code!). A limited amount of time and/or stress can make it harder for you to concentrate. There’re plenty of websites where you can check your programming skills.
You can also ask a more experienced colleague to help you and do a “mock interview” with you.
- Some companies will test your Algorithms and Data Structures knowledge so make sure to refresh them as well.
- Prepare questions: you may just want to know more about technologies that will be used, a product that you’ll be working on, or just found out about the teammates? By asking questions you show interviewers that you’re interested in the role!
During the technical interview/”live coding” part:
- After receiving a task, do not start right away with coding. First, make sure that you understood what is expected of you. Don’t be afraid to ask questions, seek clarification!
I’ve seen many candidates who failed live coding because they either didn’t understand the task or didn’t ask enough questions and just made some assumptions – never do that.
- Be communicative while writing a code. As you’re probably being interviewed by your future colleague, he/she needs to understand your ways of thinking while solving a problem, what kind of approach you take, would you be a good fit for the team, etc. And staying silent does not help in that.
- Listen to what the interviewer is saying. They’ll probably try to help you when you’ll be stuck or your solution won’t be going in the right direction.
- Think about edge cases.
- Test your code.
After the interview:
After the interview, I highly recommend you take some time to write down questions and task(s) you have received. You can then go one more time through them while you’re at home and think about other possible solutions/answers. This can help you a lot in the future!
Pro Tip: someone from the recruitment team should always get back to you with feedback, but don’t be afraid to reach out yourself and ask for the outcome of the recruitment process.
P.S as always I’ll be happy to read your comments.
Like what I do & would like to support my work? Please visit: