Addepar Software Engineer candidates describe recruiter screens, timed coding exercises, and technical, system design, and behavioral conversations. The five Software Engineer reports here all ended without an offer.
$167K
Avg. Base Comp
$211K
Avg. Total Comp
4-7 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Addepar Software Engineer process as practical coding, some system design, and behavioral conversation, though the loop differs from person to person. One candidate described a 30-minute recruiter screen, a one-hour coding test, then a full day of three one-hour rounds: coding, system design (Design Ticketmaster), and behavioral. Another described an online test, an HR round, a technical round, and a hiring manager round. A third said the process had seven stages and took roughly two months, ending in a rejection.
The coding problems candidates mention lean toward data handling. One was asked to rebuild a flat list of objects with parentId fields into a parent-child hierarchy, then explain time and space complexity and the trade-offs of the approach. Another got a portfolio-style reconciliation problem where lists and hash maps were used to find why an order book's holdings and cash didn't match. A third described a timed HackerRank-style exercise on string comparison, arrays, and hashmaps, where an ambiguous spec cost time. Clarify requirements early, then narrate your reasoning.
One candidate said system design was where they lost the offer. They felt frequent deep-dive questions kept them from finishing an MVP, so state a clear structure up front and defend your choices concisely. Behavioral prompts included walking through a complex problem you solved and explaining optimization decisions to management. One candidate was asked at the recruiter stage about a specific domain, so connect your background to Addepar's investment-management space. Some candidates also described slow or inconsistent follow-up, so ask about next steps at each stage.
Synthesized from 6 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 Addepar process.
The process started with a recruiter screening, where we dove into my background and experience with distributed systems and cloud infrastructure. That set up the technical round, which was conducted in a shared online editor. I was asked to solve an algorithmic problem—implementing a data structure for a transaction-related problem—and had to walk through my approach, explain time complexity, and discuss the tradeoffs I was making.
The process was well-organized with multiple rounds. My flow went HR interview first, followed by the technical round, then a conversation with the hiring manager. The coding question I got focused on practical concerns like transaction formatting rather than pure data structure and algorithm puzzles, which made it feel more pragmatic than typical algorithm-heavy interviews I'd done elsewhere.
The recruiters and interviewers were supportive throughout, and overall the experience felt straightforward. I was expected to explain my reasoning clearly and discuss real-world problem-solving rather than just chase an optimal algorithm.
Prep tip from this candidate
Focus on transaction-related data structure problems and be prepared to explain your implementation's tradeoffs. The coding questions lean toward practical, domain-specific problems rather than pure algorithmic puzzles, so practice problems that simulate real-world scenarios at a fintech platform.
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 Addepar
Design a data pipeline to compute hourly, daily, and weekly active user metrics from a data lake for an hourly-refreshing dashboard
| Question | |
|---|---|
| Slow OLAP Aggregations | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Random SQL Sample | |
| Top 3 Users | |
| Top 5 Turnover Risk | |
| String Shift | |
| Customer Orders | |
| Comments Histogram | |
| Minimum Change | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Scrambled Tickets | |
| Flight Records | |
| Prime to N | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Over 100 Dollars | |
| Upsell Transactions | |
| Maximum Profit | |
| Retailer Data Warehouse | |
| Download Facts | |
| First Touch Attribution |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe a recruiter or HR conversation first. One reported a 30-minute screen on their background. Another was asked to introduce themselves and explain why they wanted to join Addepar. A third was asked directly whether they had 1.5 years of experience in a specific domain, and scheduling their screen took 14 days.
Several candidates describe a timed online test early on. One reported a one-hour screen with LeetCode medium-level problems. Another had two coding problems (one DP, one graph) plus OOP and DSA questions and a short essay. A third described a HackerRank-style exercise on strings, arrays, and hashmaps with a hard-to-parse spec.
Reported live problems were practical. One candidate rebuilt a parent-child tree from flat records and discussed time and space complexity and trade-offs. Another reconciled stock and cash holdings against a series of transactions to find errors, using lists and hash maps. Be ready to justify your approach, not only produce working code.
One candidate had a Design Ticketmaster prompt and felt interruptions kept them from finishing their MVP. Another had a second round combining behavioral and system design questions, including team structure, work others reused, and how they communicated optimization decisions to management.
One candidate reported a hiring manager round that revisited their resume and added a JavaScript question and a system design question. They were told to expect an answer within a week, then asked for another week after following up, and never heard back. Other candidates reported rejections after earlier stages.
