Coding Interview

The goal of the Coding Interview is to build an understanding of how you tackle writing code within new problem spaces, as well as your ability to communicate your strategy and progress. We will also want to learn how proficient you are in your chosen programming language.

It’s also an opportunity to collaborate on a problem, so that both you and us can learn how it might be working together at Isometric.

We know that this kind of interview may be a source of stress: we'll keep things very friendly and your interviewer is there to help you out when needed.

Here is what you need to know beforehand:

Aim

• This interview gives both you and us a chance to understand what it would be like to work together on a problem.
  • There are multiple ‘right answers’. We’re more interested in seeing how you consider the context of the specific problem within the time constraints of the interview, and how you communicate your approach and collaborate with the interview.
• Communication and collaboration is a key part of day-to-day work at Isometric: we’ll be assessing how you communicate with your interviewer (technical colleague) in a pair programming scenario.
  • Treating this interview as if it is pair programming is totally the right way to go about it.

Logistics

• We will run the interview through CoderPad - an online interactive platform that allows us to host the coding exercise and will send you a link ahead of the call. We will still run the call through Google Meet.
• You can use Google, Stack Overflow or other tools to support you during the interview, but no AI. Github Copilot.
  • Please tell us when you’re about to search the Internet for something. It’s meant to be used for syntax, library functions, etc. – not helping solve the problem itself.
• This is not going to be an algorithmic/Google-style/LeetCode-style problem - it will be something that's more approachable and more like a typical feature implementation task.

Backend

• You can use whatever programming language you feel most comfortable with. There are 40+ languages supported by CoderPad.
• We’ll ask you to write a small program that solves a defined problem. There is no ‘right answer’, but we will ask you to consider edge cases and performance, and communication throughout is important.
• We are interested in seeing how you test your code - you don’t have to use a specific framework or test style to do this, but at least running your code against examples will be helpful.

Frontend

• You will be working in a React application, so a working knowledge of both React and TypeScript/JavaScript is required.
• We are interested to see how you test your code. You don’t have to write tests using a specific framework, but this will depend on your solution so it’s important to explain your reasoning.
  • The CoderPad environment we will be using has vitest pre-installed.