Newfront Software Engineer Interview Questions
& Process

I had to complete a 2-hour Byteboard Assessment. It had two parts: Technical Reasoning and Coding Implementation. The Technical Reasoning part involved reviewing a project workflow document and giving my feedback. The Coding Implementation part was related to the first part, where I had to implement some of the tasks assigned to me. It was a really unique and interesting assessment, and I felt I did a great job because I finished all the tasks. Unfortunately, I got a rejection email about a week later.

So, my first interview was with an engineer, which was nice. He asked some direct technical questions, nothing tricky. Then came a coding challenge, which included Figma and a template. The Declarative UI components in the example were a bit dated though. I was supposed to design the API JSON to be scalable, and the coding approach too. They use formik, but I used react hook form, which created all the step pages and fields dynamically with validation based on the backend response. They didn't pick me, and I didn't even get to explain my solution, which I thought was pretty disrespectful given that they said it could take up to 6 hours.

So the interview process was pretty straightforward at first. I had an initial call with the VP of Engineering where we chatted about Newfront and the role. Then there was a technical interview with a Software Engineer, which mainly involved a coding problem and a couple of behavioral questions. After that, I got to ask questions about the engineering side at Newfront. The last part was the on-site. What's different about Newfront is this project-based interview. You get a feature to implement on their website, working on a full-stack problem for about 6 hours with an hour for lunch. When I got there, two engineers gave me an overview of Newfront and their product, which was a nice way to ease in. After the coding part, I spent an hour with the CTO and some engineers discussing my project, covering scaling, optimization, and the pros/cons of my approach. They really seem to want to gauge your knowledge. It wrapped up with a 1:1 with the CTO to review the day and answer any final questions. I really liked this interview; it felt meaningful because I worked on a real project and discussed it with the team. Lunch was also great for getting to know potential colleagues. The whole process was long, from about 9:15 am to almost 6 pm, a full day of being 'on.' But honestly, I preferred it to the more traditional interviews because I got to experience the office environment and meet the people I might be working with, which you don't get elsewhere.