
Justworks Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Justworks.
Front End Engineer
The interview process was pretty good overall, most of the people I talked to were nice and some were even funny. One thing that would have made it better is if they shared the agenda beforehand, like who I was meeting and when. I didn't know how much time I had with each person, but they seemed to know. The technical challenges were similar to coding challenges you'd find on platforms like Codewars or Hackerrank. It's a decent way to see if someone can do the job, and it's pretty standard for most interviews. While I like coding challenges, I think there might be a more efficient way to assess skills. I wasn't upset by their decision not to move forward with my application. Justworks seems like a cool company with smart people, though the industry itself might be a bit dull.
- Can you tell us a bit about yourself and what you're currently doing?
- What are your thoughts on how you approach projects?
- Can you describe your experience with agile development processes?
Frontend Engineer
The interview process kicked off with a recruiter call to chat about the gig and my interest. Next up was a quick 30-min tech phone screen where I had to code a basic JS function in Coderpad and make some tweaks, then answer some questions. After that, I was supposed to head to an on-site, but since I was out of state, we did the interviews over Skype. It was three 45-min rounds with two interviewers each. The first round involved coding a basic JS class in Coderpad and enhancing it based on specific inputs and outputs. Even though I didn't finish all the methods, I felt it went okay. For both this and the prior tech interview, it's good to talk through your approach before coding and during the coding phase. The next interview was about architecture – how I'd set up the database for a made-up app, using Google Draw to map out a schema and tables. The final interview was all about culture/fit, discussing JustWorks and the engineering team. After getting the okay, I flew out for more interviews with the CEO and VP of Engineering. I had a good chat with the CEO, and then a relaxed lunch with the engineering team. A few days later, I had a call with the VP of Engineering that also went well. I got an offer but took another role. JustWorks did everything right, but the other offer was significantly higher for a more senior position. I'll definitely recommend JustWorks.
- Can you write a JavaScript class to simulate Redis functions?
- How would you go about designing the architecture for an e-commerce application?
Front End Developer
First, I chatted with HR who asked about my background and then scheduled the next interview. A few days later, I interviewed with someone from the tech team. They also asked about my background, my projects, and the tech I use. Then, they gave me an algorithm problem to solve and code live online. Even though I solved it, the HR later told me they weren't moving forward with my application, and I'm not sure why.
- Can you tell me about your background?
- Can you tell me about your background and the technologies you are using?
Justworks Frontend Engineer Interview Questions
Quoted word for word from Justworks interview reports.
“Can a given string be formed using the letters provided in an array, accounting for duplicate letters?”
Read reports →“Can you write a JavaScript class to simulate Redis functions?”
Read reports →“Could you whiteboard or pseudo-code a program to check if a date range is saturated by an array of date ranges?”
Read reports →“Could you whiteboard or pseudo-code a game?”
Read reports →“How would you go about designing the architecture for an e-commerce application?”
Read report →“Could you build a small web application using the instructions and wireframe provided, aiming to spend only a couple of hours on it? The directions were intentionally ambiguous and open-ended.”
Read report →“Can you describe your experience with agile development processes?”
Read report →“Can you tell me about your background?”
Read report →Formats, difficulty and experience
Across all 6 Justworks interview reports.