Candidatei-me de outra forma. Fui entrevistado pela Livefront (Raleigh, NC) em mar. de 2026
Entrevista
The initial phone call was pleasant. The followup video call was also polite. But the interview project they give you is unequivocally the worst step of any interview process I have been in. Not only is it vague, but the length of the project is obnoxious. Even if they pay you for your time, it's not worth the tens of hours they expect you to spend building up an entire production ready app (they forbid AI as well, so you can't even have a code-bot help you with all the grunt work).
Tell me you don't care about work life balance or people with children without telling me...
Candidatei-me online. Fui entrevistado pela Livefront em jan. de 2026
Entrevista
The interview process was well structured and progressive. It started with answering a few questions via email. If that went well, the next step was a phone screen with an HR representative. After that, there was a conversation with the Head of Engineering, and the final step was a take-home coding challenge.
The initial email questions focused on things like why you want to be part of Livefront, who inspires you, the testing tools you’ve used, and your involvement in the coding community.
The HR call was a relaxed conversation about my background and the technologies I’ve worked with. The following interview with the Head of Engineering went deeper into my experience, with a strong focus on products I’ve built and technical decision-making.
The take-home assignment was a mock API built with NestJS, based on a provided PDF. While not explicitly stated, it’s important to include unit, integration, and end-to-end tests, as they clearly expect this. Following NestJS best practices is also key, such as using class-validator decorators on DTOs and leveraging NestJS’s built-in API documentation instead of creating separate OpenAPI docs.
A few tips for future candidates:
Avoid simulating real API calls with promises, as this can be viewed negatively. Adding JSDoc comments to your classes is appreciated, even though it’s not explicitly required. If you implement more complex logic like filtered pagination, make sure to clearly explain your approach, as reviewers may not immediately understand your design without context.
Overall, the process was thorough and fair, with a strong emphasis on code quality, best practices, and clear communication.
Perguntas de entrevista [1]
Pergunta 1
Questions about your background and deep dive on some products
Candidatei-me online. Fui entrevistado pela Livefront (Minneapolis, MN) em nov. de 2025
Entrevista
Interview process started with a screening which went well. Recruiter was nice and informative about the company. Next round was a technical interview with one of the senior staff. We went over work history and a few situational questions. Then moved on to the technical code challenge. Code challenge was straight forward mock API and API schema. After that there was a review of the code challenge with one of the senior developers. This interviewer had no idea what he was reviewing. He kept asking questions of why I chose the frame work I did and some of the functionality I created which were part of the coding challenge that Livefront gave me. Asking why I went with Nestjs, or why I assumed the link was from a third party, and a few others. I don't think this person ever looked at the requirements of the challenge before reviewing my code. I pointed out requirements or assumptions at least 5 or 6 times to the interviewer. Outside of that the interviewer did not seem like he wanted to be there. Completely in impersonal. They also said for doing the coding challenge they give you a week to do, they would send you $200, which I never received.