Two candidates describe a Juniper Square Software Engineer process built around a recruiter screen, a hiring manager conversation and a multi-interview final loop with coding and behavioral questions. Neither received an offer.
$178K
Avg. Base Comp
$190K
Avg. Total Comp
6-8 rounds
Typical Rounds
Not reported
Process Length
Two candidates describe the Juniper Square Software Engineer interview, and both start the same way: a recruiter phone screen, then a conversation with a hiring manager that centers on past experience. After that, the reports diverge, so treat the later stages as variable.
One candidate describes a final round of four separate Zoom conversations plus an informal chat at the end. The coding task was an array transformation that handled duplicates with indexed notation, turning [dog, dog, cat, dog] into [dog, dog(1), cat, dog(1)(1)]. That candidate passed all test cases and still did not get an offer, and says engagement varied between interviewers. Behavioral questions covered a time they failed and what they learned, why they wanted Juniper Square, and a walkthrough of previous projects.
The other candidate, interviewing for a Staff-level role, reports a virtual onsite with four technical rounds. Extra team-matching interviews followed, one with an engineering manager and one with a VP of Engineering. That candidate was also asked to design a barcode system and to describe what their projects would look like without their contributions, and counted eight rounds in total.
For preparation, practice explaining your reasoning aloud while you code. One candidate passed every test case and still did not receive an offer, so a correct solution may not be the whole picture. Prepare specific failure and motivation stories. Ask the recruiter early how many rounds remain and who they are with. If you are interviewing at Staff level, prepare for system design and questions about your individual impact.
Synthesized from 2 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Juniper Square process.
I expected a straightforward interview process, but what I got was eight rounds of interviews with poor communication from start to finish. The first three rounds went smoothly: an HR phone screen, a hiring manager conversation focused on my past experience, and then a virtual onsite with four technical rounds. After that, things got messy.
The recruiter called with positive feedback, but the next day called again to say the original position had been filled. They wanted to keep moving forward with me for a different team and mentioned two team-matching interviews—one with an engineering manager and one with a VP of Engineering. Since this was a Staff SWE role, they also wanted another system architecture round. I asked the recruiter point-blank if they actually intended to hire me, because I didn't want to waste time on a real opportunity that wasn't real. They explicitly said yes, they wanted to hire me.
Based on that assurance, I scheduled the three additional interviews, expecting them to be lighter team-matching conversations. Instead, they turned out to be serious technical and leadership interviews. One question asked me to design a barcode system from scratch. Another was behavioral, asking what my projects would look like without my contributions. That brought the total to eight rounds.
After all of that, I got a generic rejection email: "We have decided not to move forward at this time." No explanation. I tried calling the recruiter multiple times to understand what happened, especially after being told they wanted to hire me. They never answered or called back. The actual interviews were fine, but the process itself was incredibly frustrating. The lack of transparency was the real problem. If the role was uncertain or the hiring decision was still up in the air, I should have been told that upfront instead of being reassured and then put through three more substantial interviews. Eight rounds is a huge time investment for any candidate, and I at least deserved a real explanation for the rejection, not silence.
Prep tip from this candidate
Be cautious if you're told a position has been filled but the company wants to continue the process for another team—that's a sign to ask hard questions about the actual hiring intent and timeline before investing in additional rounds. Also, for Staff SWE interviews, expect system design questions like barcode system design and behavioral questions about your individual impact on past projects.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Juniper Square
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Random SQL Sample | |
| Subscription Overlap | |
| Top 3 Users | |
| Top 5 Turnover Risk | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Duplicate Rows | |
| Scrambled Tickets | |
| Find Bigrams | |
| Last Transaction | |
| Upsell Transactions | |
| Longest Streak Users | |
| Payments Received | |
| Size of Joins | |
| String Shift | |
| Customer Orders | |
| Find the Missing Number | |
| Minimum Change | |
| Comments Histogram | |
| Raining in Seattle | |
| Get Top N Frequent Words | |
| Google Maps Improvement | |
| Bagging vs Boosting | |
| Employee Salaries (ETL Error) | |
| Flight Records |
Synthesized from candidate reports. Individual experiences may vary.
Both candidates report starting with a recruiter or HR phone screen. One describes the recruiter as helpful and keeping them informed. Expect a short conversation about background and logistics, though the exact content is not detailed.
Both candidates report a conversation with the hiring manager next. One says it focused on their past experience. Prepare concise project stories that show your individual contribution and the outcome.
One candidate reports four separate Zoom conversations plus an informal chat. The other reports a virtual onsite with four technical rounds. Content reported across the process includes an array-duplicate coding problem, failure and motivation questions, and project walkthroughs. Interviewer engagement may vary between sessions.
The Staff-level candidate reports that the original position was filled and that they were offered further interviews for another team. These were with an engineering manager and a VP of Engineering, plus a system architecture round. One question in these later rounds asked for a barcode system design. This may not apply to every level, so ask the recruiter what to expect.
