Juniper Square logo

Juniper Square Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 11 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
27.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Juniper Square.

Showing 3 of 11
Juniper Square logo
Juniper Square

Software Engineer

Engineering · a year ago

Entry Average Negative experience No offer 6 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Coding Technical Behavioral

I am very disappointed with the hiring process. After clearing 5 rounds of interview, I was waited for a whole week to schedule the last round of executive interview. After many followups, the HR was not responding to my mails and the calls. But giving me the excuses that she is on leave. They put me on hold, as I have already told that my last working day is near. But still, they were ignoring me. I am frustrated only becoz even after clearing the 5 rounds, I did not get the HR call. I have totally wasted my one month into that.

Confirmed questions3 questions
  • There was one DSA round
  • Then a technical round
  • And a HM round
Juniper Square logo
Juniper Square

Software Engineer

Engineering · more than a year ago

Staff Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Background check Offer
Interview formats
Technical Coding Behavioral

First, I had a call with the recruiter. The interview was scheduled about a week after that. Then, there was a technical interview where they asked questions about my experience. It included a 30-minute pair programming challenge that was pretty easy but had an edge case. After that, I had a manager interview, which was a friendly chat about my past leadership experience and goals. It went really well. The very next day, the recruiter called to say they decided to go with other candidates and explained why, which was helpful. I think I got stuck on the programming challenge because I got in my own head, even though it was easy.

Confirmed questions1 question
  • They asked me to do a coding challenge that was easy but required attention to edge cases. They mentioned that fully functional code wasn't strictly necessary, but for this task, it should have been straightforward to complete. The main goal wasn't optimizing for O(n) complexity, but rather understanding my thought process. I'm not giving specifics because someone who has practiced LeetCode a lot would find it easy, and I haven't practiced much lately.
Juniper Square logo
Juniper Square

Software Engineer

Engineering

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Technical Coding System Design Behavioral

I was contacted via triplebyte and had a really good phone call with a founder. Then I was invited for an onsite interview. The onsite involved some whiteboard coding and system design, pretty standard, maybe easy to medium leetcode level. One part was refactoring some javascript code. Everyone was really nice and I liked the company even more after talking to them. The only downside was after the interview, they said they'd get back to me the same week but I'm still waiting. At least the lunch was free.

Confirmed questions6 questions
  • Can you rotate an array in place?
  • Implement a Python class for user actions with undo/redo.
  • Solve this arrays coding exercise.

Juniper Square Software Engineer Interview Questions

Quoted word for word from Juniper Square interview reports.

How would you process document names to ensure uniqueness?

Read reports

How would you design an interactive book with branching paths?

Read report

Formats, difficulty and experience

Across all 11 Juniper Square interview reports.

Interview formats

Coding 32.3%
Behavioral 29%
Technical 25.8%
System Design 9.7%
Case 3.2%

Interview difficulty

Easy 18.2%
Average 72.7%
Difficult 9.1%

Candidate experience

Negative 36.4%
Neutral 36.4%
Positive 27.3%