
Four candidates describe Jerry's Software Engineer interviews as a take-home, a recruiter or HR call, data-structures coding, and later conversations with the CTO, a founder, or a VP.
$130K
Avg. Base Comp
$150K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
All four candidates describe a take-home assignment at the start of Jerry's Software Engineer process. Three of them say the bar is production-quality code rather than a merely working answer. One described an interval-style problem where edge cases and code quality mattered, and another said the challenge could be written in TypeScript or JavaScript and was judged on style as well as correctness. The fourth mentions finishing a take-home before a recruiter call but doesn't say how it was assessed.
Three candidates then describe a recruiter or HR call, in one case with some behavioral questions. The coding questions reported are data-structure and algorithm problems. One candidate was asked to generate a sorted, duplicate-free sequence from the rules k to 2k+1 and k to 3k+1, then return the value at index N, in a live session with two engineers. Another reported a pattern-recognition series problem plus array manipulation, and a third reported one hard and one medium-hard problem in back-to-back 45-minute rounds.
Later rounds differ by candidate. One reports a system design interview. Two describe a CTO conversation, and one of those focused on higher-level problem-solving rather than another coding exercise. One candidate finished with a founder conversation about academic and professional background, and another with a VP conversation. Reported outcomes were three no-offers and one declined offer.
Logistics were uneven in at least two accounts. One candidate saw Google Meet chat with a local IDE in one interview and a Replit link in the next, and another could not get format, duration, or tooling details from HR. Ask your recruiter about setup early, and practice talking through your reasoning aloud.
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 | |
| Size of Joins | |
| k-Means from Scratch | |
| User Experience Percentage | |
| Google Maps Improvement | |
| Distance Traveled | |
| Random Weighted Driver | |
| Green Dot | |
| Delivery Estimate Model | |
| Sort Strings | |
| Three Zebras | |
| Maximum Profit | |
| 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.
All four candidates mention a take-home coding assignment. Three describe it as judged on code quality, style, and edge cases as well as correctness. One mentions an interval-style problem and another says TypeScript or JavaScript was allowed. One candidate waited about two months to hear back after submitting.
Three candidates describe a recruiter or HR conversation, with some behavioral questions in one account. Experiences with communication differ: one found the recruiter friendly and the timeline clear, while another asked repeatedly about format, duration, and tools without getting a clear answer.
Candidates report coding rounds of around 45 minutes on algorithmic problems. Examples include generating a sorted, deduplicated sequence from growth rules, series pattern-finding, array manipulation, and one hard plus one medium-hard problem. One candidate coded with two different platforms across back-to-back interviews.
Later technical stages differ by candidate. One reports a system design interview, while two describe a CTO round; one of those focused on critical thinking and problem-solving rather than coding. Be ready to explain past decisions and architecture choices in plain language.
Two candidates report a final conversation with leadership. One describes a founder chat about academic and professional background that felt conversational rather than technical, and another mentions a final conversation with a VP without further detail.