Justworks Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 46 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Justworks.
Justworks
Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Coding Behavioral Technical
I had an automated coding screener with practical questions that built on each other, which was great. However, the 'Conversational' stage was really bad. The interviewer seemed uninterested unless I messed up and had to give another example. They didn't ask follow-up questions or try to engage in a deeper conversation; it felt like they were just rushing through a list of questions. I didn't get the chance to talk about my career contributions as mentioned in the prep email. It was mostly behavioral questions with some technical trivia, not what was advertised.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Justworks
Software Engineer
Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check Offer
Interview formats
Coding Behavioral System Design Technical
So after the recruiter emailed to set up a phone call, which was 2 days after the onsite, it turned out to be a rejection phone call. They gave me specific feedback from each interview. I appreciated the feedback, but I was kind of expecting an offer when they wanted to chat on the phone rather than just sending a generic rejection email. So the personal touch was a bit misleading but also kinda nice? The interview process included a phone screen, a Codesignal take-home, a behavioral interview with an engineering manager, and a final round onsite in NYC or virtual. The onsite had 4 parts, each lasting 45 mins to 1 hour: Architecture, coding, a PM chat, and an EM chat.
Confirmed questions2 questions
- For the system design, I needed to figure out data modeling, API design, and the overall system design for a JIRA or Kanban type board, and I felt like I could have used more experience with APIs and endpoints, and also knowledge on how to store this kind of data (like what kind of tables to use for this ticket-column-board structure).
- The coding interview was about debugging a script that was purposely confusing for printing manager-employee relationships and identifying how it could be improved.
Justworks
Software Engineer
Entry Difficult Neutral experience No offer 8 rounds
Interview process
Recruiter call Technical screen Take home Phone screen Onsite Onsite Onsite Onsite
Interview formats
Technical Coding Behavioral System Design Technical Behavioral Behavioral
So I had 2 years of experience going into this. The first bit was like a 15 min chat with a senior engineer, just talking about a project I did. Then there was this online assessment thing, Code Signal, where you had to build a banking system and it got harder with each question, kinda like tough LeetCode mediums or easier hard ones. I passed even though I didn't nail it. After that, a behavioral interview with a staff engineer, super standard stuff. The next stage was the in-person onsite, which started with a system design problem: design a Jira board. They were more interested in how I'd model the data and design the APIs, not so much the heavy architecture or CAP theorem talk. Then came a debugging task. It was this messed up script for managing employee hierarchies, supposed to show who reports to whom, but it was written badly with confusing names and structure. You had to figure out why it failed and fix it. If you were quick, they might ask you to speed it up. Finally, two more behavioral interviews, one with a product manager and one with an engineering manager.
Confirmed questions8 questions
- Can you talk about one of your past projects?
- Could you design and implement a banking system with progressively harder features?
- Tell me about a time when... (behavioral with staff engineer)
Justworks Software Engineer Interview Questions
Quoted word for word from Justworks interview reports.
“Given a list of intervals such as [[1,3],[2,6],[8,10]], merge overlapping intervals, and return them [[1,6],[8,10]].”
Read reports →“Is it possible to determine if an input array has sufficient characters for a given input word?”
Read reports →“What is the output for the input [5,9 | 0,3] regarding saturation?”
Read reports →“Can you write a function that checks if a given array of characters has all the characters needed to construct a specific string?”
Read reports →“Given a list of integer ranges, determine if the overall range is 'saturated'. The definition of saturated is tricky: it can be fully saturated, over-saturated, or under-saturated. For example, with input [2,5 | 0,2 | 10,15 | 6,9], the output should be 'Saturated'. Even though '2' appears twice, which might seem over-saturated, the interviewers considered it 'perfectly' saturated because it covers all numbers from 0 to 15. They found repeated numbers acceptable.”
Read report →“Can you create a method called 'has_letters' that checks if a character array has the necessary letters to spell out a given word, making sure the letter counts match, like needing three 's's for 'disassemble'?”
Read report →“Can you find a word within a grid, considering some extra constraints?”
Read report →“Consider the input [3,10 | 0,5 | 50,100]. What is the output for saturation? The interviewers called this 'over saturated' because the overlap is more than one number. They didn't seem to care that this range is also both over-saturated and under-saturated.”
Read report →“How would you merge intervals so that none overlap?”
Read report →Formats, difficulty and experience
Across all 46 Justworks interview reports.