Hey Dan!
Congratulations on making it to our technical interview!
At T3 Tools, we want to to build our interview process around your suc cess. We expect different candidates to have different methods that best showcase their strengths.
With that in mind, we've created 3 different paths for our technical interviews. Please read these ahead of your interview and let us know what path you'd like to take!
tl;dr - the usual leetcode algorithm puzzles
Lots of developers have trained up their skills on platforms like Leetcode, HackerRank, and Advent of Code (Pro tip: most of our problems will be based on AoC). If you're one of the devs on that grind, this might be the path for you!
We don't want you to stress out about the environment for the code puzzle/challenge, so we let you do a simple screen share and pick what you prefer 🙂 If you have no preference, we're happy to set up a quick CodeSandbox!
Answers can be working solutions or pseudo-code, whichever you prefer!
Remember - our goal isn't to see how fast you write the right answer. We're trying to learn about how you work and communicate.
tl;dr - same as above but with a realistic code problem
We're big fans of making interviews feel more like the work you'll be doing on the job. This path is focused on that 🙂
These problems will vary in type and complexity based on the role and level you're interviewing for. If you're not sure what type of problem you'd get after reading through the examples below, please reach out to your recruiter and they'll be happy to give you more clarity ahead of your interview!
Junior-midlevel frontend: Pokedex Problem