
Four candidates describe Jerry's Software Engineer interviews as starting with a production-quality take-home, then a recruiter call and live data structures and algorithms coding. Two also met the CTO, a founder or a VP. Three report no offer.
$130K
Avg. Base Comp
$150K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe Jerry's Software Engineer process as opening with a take-home assignment judged on production-quality code, not just a correct answer. One candidate said the exercise looked simple but needed careful edge-case handling and clean style. Another said it could be written in TypeScript or JavaScript. A third said they waited about two months for a response after submitting it.
The live technical rounds focus on data structures and algorithms. Candidates mention array manipulation, series-pattern questions, and a sorted, duplicate-free sequence generated by the rules k to 2k+1 and k to 3k+1. The interval-style problem one candidate mentioned came in the take-home rather than a live round. One report involved a 45-minute coding session with two engineers. Another described back-to-back 45-minute sessions that used different tools: a Google Meet chat with a local IDE, and a Replit link. Test your screen sharing and have an editor ready.
The later rounds differ between reports. One candidate describes a CTO round on higher-level problem solving and a founder conversation about background. Another describes a CTO technical interview followed by a VP conversation. A third mentions a system design round. Prepare to explain your past decisions in plain language.
Of the four candidates, three report no offer and one declined an offer. One found communication about format and timing unclear, while two others described a responsive recruiter and a clear timeline. Ask early about format, duration and tools.
Synthesized from 4 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 Jerry process.
Jerry's interview process is genuinely well-structured and tests a pretty broad set of skills. It kicks off with a take-home assignment where you write code that's expected to be production-quality — this is where they get a real sense of your coding standards and ability to build something clean and thoughtful. The timeline here can be slow; I waited about two months to hear back after submitting mine, but once things moved forward the pace picked up significantly.
Then you move into two separate technical rounds, both LeetCode-style questions focused on data structures and algorithms. These are standard but fair — they're testing your fundamentals, not trying to trick you. What made the process feel genuinely different was the CTO round. This wasn't another coding problem. Instead it was about critical thinking and problem-solving from a higher level, which gave me a sense of how the company actually thinks about engineering challenges beyond just grinding out leetcode.
The final round is with one of the founders, and it's a behavioral conversation rather than technical. They ask about your academic and professional background, and the whole thing feels more like getting to know each other than being interrogated. The founder was genuinely warm and easy to talk with, which matters a lot in those closing conversations.
What stood out most was the recruiter's engagement. She asked for feedback after each round — not in a robotic way, but because she seemed to actually care about making the experience better for candidates. Responses were prompt and thoughtful. The whole process felt like they respect your time while being genuinely thorough about evaluation. It's a longer process than some tech interviews, but that's intentional, and it shows they take hiring seriously.
Prep tip from this candidate
Focus on writing clean, production-quality code for the take-home assignment — it's the first impression and the bar is higher than typical OA problems. For the technical rounds, drill data structures deeply rather than breadth across many algorithms, and prepare for the CTO round by thinking through how you'd explain your past problem-solving decisions and architectural choices in plain language.
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 Jerry
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Employee Salaries | |
| Payments Received | |
| Top 3 Users | |
| Sum to N | |
| P-value to a Layman | |
| Weighted Keys | |
| Find the First Non-Repeating Character in a String | |
| k-Means from Scratch | |
| User Experience Percentage | |
| Size of Joins | |
| Google Maps Improvement | |
| Distance Traveled | |
| Random Weighted Driver | |
| Green Dot | |
| Sort Strings | |
| Delivery Estimate Model | |
| Maximum Profit | |
| Three Zebras | |
| Four Person Elevator | |
| Bagging vs Boosting | |
| Type-ahead Search | |
| LRU Cache 1 | |
| KNN From Scratch | |
| Uniform Car Maker | |
| Download Facts | |
| Groups of Anagrams | |
| Basic Regex | |
| String Subsequence |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a take-home exercise at the start of the process. Several say it is judged on production-quality code, readability and edge cases, not only correctness. One mentions an interval-type problem and another says TypeScript or JavaScript was allowed. Treat style and structure as part of the grade.
Candidates describe a recruiter or HR call after the take-home, with some behavioral questions in one report. Experiences vary: one found the recruiter welcoming and clear, while another could not get clear answers about interview format, length or tools. It is typically worth asking for logistics directly.
Candidates report data structures and algorithms questions in sessions of about 45 minutes, including array manipulation, series patterns and a sorted sequence generation problem. One report includes a separate system design interview. Tools may differ between interviewers, so check your screen sharing, IDE and Replit access beforehand.
Candidates describe final conversations with senior leaders. One report has a CTO round on critical thinking and then a founder conversation about academic and professional background. Another describes a CTO technical interview followed by a VP conversation. Prepare to explain your problem-solving choices clearly and to discuss your background.