By Jihyun Hwang

As a brief introduction, I transitioned into software engineering five years ago following a period of self-study and a programme at a non-profit organization in London. Since then, I’ve completed numerous interviews, and with each one, I’ve learnt more about how to approach the process.

Interviews can feel daunting whether you’ve been in the industry for years or you’re stepping into a new role. I’m sharing what’s worked well for me, and what definitely hasn’t. I’ll break down what to prepare for each step, how to practice, and other tips along the way.

Typical interview process for software engineers

1. Application stage
2. Recruiter/Talent Acquisition screen
3. Technical interview(s) — this could be live coding, a take home task, system design, or pair programming
4. Hiring Manager and culture/values interviews
5. Offer

In the sections below, we’ll take a close look at each step.

But before I apply, I take some time to reflect on what I’ve learnt from past roles, what I’m looking for in my next team and project, and the value I can bring. It’s important not to apply just for the sake of it. Think of it as running your own little retrospective. Know your strengths, understand what you’re after, and set yourself up properly before diving into the process!

1. Applying stage

• To update my CV, I try to scan the market first. I read a handful of job descriptions for similar roles, note the tech stacks that keep coming up, spot the trends in the job market, and map them to my own experience, then update my CV accordingly.
• While reading job descriptions, I take notes if I notice wording or sentences that could reflect my experience. Mirroring the language of the job description is important with today’s ATS filters.
• I always keep my CV to a single page.
• If it’s your first role in tech, it’s worth mentioning a side project or any activities you’ve participated in (hackathons, Codebar, etc). It doesn’t matter how small the project is, what matters is showing what areas you’re interested in and your passion for learning.
• Also, if your previous experience doesn’t seem directly connected in terms of hard skills, highlight the soft skills you’ve built and how they could translate into the new role. For example, my previous job was in the service industry. I emphasized strengths like communication, working under time pressure, and task management. You might be surprised how many soft skills are transferable.
• “at least X years’ experience” can be flexible. I once interviewed for a senior role with only two years’ experience. The conversation went well, they opened a mid level position for me, and I got the job. So don’t be afraid to apply for roles that feel like a slight stretch.
• There’s never really a time when you’ll feel completely “ready”. You’ll never tick every single box in a job description. But the more interviews you do, the more ready you’ll feel. If you’re hesitating, that’s often the best sign it’s time to start applying.

2. Recruiter/Talent Acquisition screen

• This stage is more of an introductory call to get to know each other. Recruiters check high level fit — your background, the role, basic logistics, and general values. They might also explain the interview process, the timeline, and other useful information.

You’ll usually be asked the “typical” interview questions, such as,

• “Can you introduce yourself briefly?” → Always prepare a 1–2 minute highlight of your career path
• “Why did you leave your last role?”
• “What are you looking for in a new team?”

3. Technical interview

• This is the stage most people including myself find intimidating, and the preparation can feel broad. The only way through is repetitive practice to build confidence. mock interviews, varied exercises, and plenty of coding practice. Since this stage can vary a lot, I’ll focus more on approach and mindset.
• I try to think of the technical interview as pair programming with colleagues, solving an issue together. With that mindset, it feels more like a real work situation. Instead of thinking they’re there to judge me, I remind myself that we’re here to tackle a problem together.
• If something is unclear, don’t just stop at “I don’t know” or wait for them to give you the answer. Instead, share your current understanding, outline possible options, and show how you’d reach out for help or explain your reasoning.
• There’s rarely one “perfect” solution (that’s what I love about coding). Discuss your approach openly. Even if you have a clear approach, talk it through with the interviewer, get their input, and talk through pros and cons. It’s a great opportunity to show how you present ideas and remain flexible if you need to adopt a different approach.
• Throughout the interview, think aloud. Explain what you’re doing, why you chose that approach, and how you’d test it. If you run out of time, that’s okay. I usually leave the last couple of minutes to explain what I’d do differently, and what I’d try if I had more time. Be prepared to discuss how you’d improve your solution in terms of testing, accessibility, performance, and developer experience.
• As a front end engineer, I’ve often been asked to build something “simple” in JavaScript or React. To prepare, I practice building small features in the style of the company’s product. Even if the actual question is different, this practice lets you touch many core areas.
• Keep up with recent trends and best practices. I recommend subscribing to a few tech newsletters. Not just to learn how to use a tool, but also to understand why. For example, many of us are familiar with how to use React, but it’s just as important to understand why it became popular. Don’t just know what Redux is, but why it was needed in the first place and what alternatives exist today.

4. Culture and values interviews

• These are usually situational questions, such as “Can you give me an example of…” They mostly focus on your approach in tricky situations, your communication style, your passion, and so on.
• I recommend preparing one or two examples for the most common scenarios, like resolving a conflict, ensuring product quality, or communicating with other teams.
• Focus on what you did, not just the situation itself.
• It’s completely fine to share a situation that didn’t go perfectly. What matters most is how you approached it, the steps you took, and what you learnt from the experience.
• Again, I don’t think there’s a right or wrong answer here. This stage is really about showing how you work as part of a team!

5. Another tip

• Run your own retrospective as soon as the interview finishes. This is my biggest tip “Treat every interview as a learning point.” Note what they asked, how you answered, what you could have said better, and any questions you didn’t fully understand. Reflect on whether any gaps were down to nerves or genuine knowledge. It’s perfectly normal not to nail every answer. The key is using this to sharpen your prep for next time.
• Be prepared for the final questions too. This isn’t just a chance to show interest — it’s your opportunity to dig into what matters to you! The team, the culture, and the way of working. I usually keep five or six questions ready and, depending on the time and how open the interviewers seem, I’ll ask one, two, or even all of them. You’re interviewing them just as much as they’re interviewing you.
• One question I often ask is “What do you like about the team?” Don’t just listen to the words, pay attention to nuance and behaviour. Once, I asked this and three interviewers kept passing the question between them. No one was keen to champion the team, and their answers weren’t convincing. That already told me a lot.
• Keep a daily log of what you do whether at work or on a side project. It makes your achievements much easier to recall, especially when it comes to updating your CV.
• Treat interview preparation as a check-in. How far you’ve come, what gaps you want to close, and which team or product will help you grow next.

Interviews are like muscle memory. The more you practice, the better you perform. And remember, a one hour interview can never capture your full capability or potential. If you don’t progress this time, that’s okay! There will always be another opportunity. Keep going, and turn the daunting moments into learning experiences. You’ve got this!