Engineering Hiring Process
We have many different processes that apply for different positions or grade levels. Some are more focused on interviews, others on code challenges, some take some days and involve different areas, and others are one-day processes. This page explains some of the most common types of hiring processes we apply today.
Whiteboard Process
The whiteboard process consists of a 4 step interview, usually in a single day.
First Interview / Whiteboard: 45 minutes of a code challenge where the candidate shares his screen while solving the problem presented by the interviewer.
First Interview / Design discussion: Right after the code challenge, 15min discussing the decisions around the code produced. The candidate argues over his/her decisions about the solution delivered as well as general discussion about architecture.
Second Interview / Final: 45 minutes of a conversation between the candidate and some people from our team regarding the candidate's history, experiences, and questions related to his area of knowledge.
Decision / Proposal: Internal meeting among all of our interviewers and recruiters to share opinions about the candidates decide the offers, and the best squads for the candidates. This step may happen on another day depending on the number of candidates.
Composition Of The Interviews
First Interview / Whiteboard: 2 engineers take part in the code challenge interview. The lead engineer has the same grade level for the position the candidate is participating in and is responsible for making sure the candidate understands the process and guides him/her through the code challenge. The second engineer is usually someone who is a watcher to learn the process and be a leader in the future.
First Interview / Design Discussion: same audience from the whiteboard.
Second interview / Final: Usually composed of 3 people, being one representative from the tech area, one engineering manager and someone from the recruiting team.
Interviewer Preparation
The following items are general tips for you to get better prepared for the code challenge and the interviews.
First Interview / Whiteboard - Before The Technical Challenge
English is not mandatory for this interview if all participants are fluent in another language.
You will be asked to share your screen so make sure to close any application you don’t want us to see (like social networks or personal/work communication platforms).
prepare your editor of choice (VSCode, Sublime, Vim, etc.) and any plugin you may want to use (ESLint, Prettier, etc.) since you won’t have much time to do this during the code challenge. We may also request you to code using a code sandbox or playground.
Prepare a tool to test your APIs too (Postman, cURL, Insomnia, etc.).
We test your ability to design APIs, but not the ability to scaffold a project so that you can use a generator library (express-generator, fastify-generator, nestjs-generator, etc) and have that project prepared beforehand (no requirements on the name, you can be creative :) ).
You may or may not use a database, so have one ready to be used (MongoDB is the preferred choice). This way, you won’t lose time by setting up one database from scratch.
Ensure you have a good internet connection and you can secure a distraction-free space during the scheduled time.
We allow you to use any search engine of your choice and any npm package you may need, apart from those explicitly banned during the code challenge's description. Again, you can use search engines, but don’t look for tutorials.
We cannot see if you have a 2nd screen connected. This means we trust in you that you’ll follow the guidelines shared here.
First Interview / Whiteboard - During The Technical Challenge
First, we may ask you some introductory questions about you (no tech-related questions).
Then, we’ll share the test with you, you can take your time to read it, and ask as many questions as you want. Please, ensure you have the requirements clear before starting to code.
When you start to code, you can ask questions too, you can share with us your thought process or talk about what you want to do or how you’ll do it.
Ensure to manage your time. The test is short enough to fit in 45 minutes or less, so be vigilant of the time you’re using. We may give you some hints if we see you’re stuck, but we always prefer you to come up with the solution to the problems you’re facing.
We’ll let you know when you have 5 minutes remaining and when time’s over so you can wrap up/finish your code.
You can test your application as many times as you want, please, ensure it works correctly.
When there are around 1 or 2 minutes left, we’ll ask you to do a quick run of the application you’re developing to see if everything works fine.
Note: We won’t share feedback right after the code challenge. Talent Acquisition may give you feedback on things we think you can improve.
First Interview / Design Discussion (After the Technical Challenge)
After the code challenge, there will be around 15 minutes of conversation around the decisions you took to code the solution to the code challenge.
We may ask you for some feedback about the test, this is optional, but you can be as honest as you want here. This won’t have an effect on your selection process in any way but may improve the QoL of future applicants.
The discussion may vary from simple code structure to more complex items such as design patterns.
Second Interview / Final
The interview may include technical questions along with a discussion of past work experiences, career aspirations and motivations.
Be ready to discuss soft skills and growth opportunities.
We want also to understand your current position in regards to team structure, how demands reach you, how you provide status about your tasks and so on.
This is also a great opportunity to ask your questions and learn more about the opportunity, our values and our team.
Do you have any feedback? Please, feel free to send suggestions to the Talent Acquisition Team.
Last updated