Three candidates describe Cointracker's software engineer interviews. Two report a take-home assignment followed by a team presentation, and one reports multiple coding rounds, a system design question and a question about interest in crypto.
$185K
Avg. Base Comp
$230K
Avg. Total Comp
Not reported
Typical Rounds
4-6 weeks
Process Length
Candidates describe Cointracker's software engineer interview differently depending on the person, so prepare for a few possible formats. Two senior-level candidates report a take-home assignment followed by a presentation or demo as the center of the process. One of them describes a CoderPad algorithm screen first. The other describes an HR interview and a technical interview first. Both say the assignment was budgeted at roughly two to four hours. One felt it needed more time to do properly, and the other spent significantly more. Both report that interviewers pressed on implementation choices. One mentions queue implementations and extreme edge cases, and the other was repeatedly asked why certain features were not built. If you get this assignment, ask which features are must-haves and how the presentation will be judged. Be ready to explain what you left out and why.
A third candidate, for a Software Engineer role, reports a different shape: three coding and technical interviews with an engineering manager meeting in between. Questions covered years of experience, a system design problem and a direct question about why you want to work in crypto. Have a specific, honest answer on why this space interests you and how Cointracker differs from similar products.
Two candidates report that later rounds with hiring managers or managers were planned or took place. Two report receiving no offer and no feedback, and the third declined an offer. Reported end-to-end timing was about one month and about six weeks, and the process may feel long.
Synthesized from 3 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 Cointracker process.
I ended up declining the offer from CoinTracker for a Software Engineer role in spring 2024, and the reason had more to do with the company's vision than with the interviews themselves. The process was fairly conventional. I went through three coding and technical interviews, with a meeting with the engineering manager in between them. The team's structure seemed organized, and the people I spoke with clearly understood how the work was divided.
The questions touched on a few areas I didn't expect to see grouped together. I was asked about my years of experience, which was a straightforward check of my background. There was a system design question as well. The part that stood out was the direct question about my interest in crypto. It wasn't a trick, but it was pointed, and it made me think harder about why I wanted to work in this space rather than just in tech generally.
That question ended up being the crux for me. CoinTracker operates in a market with a lot of similar products, and I struggled to see what made their vision distinct enough to commit to. The engineering side looked solid, but I couldn't feel confident in the direction of the company, so when the offer came, I passed on it.
Prep tip from this candidate
Be ready to explain your years of experience and why you're specifically interested in crypto, since both came up alongside the system design question. Also prepare a clear, honest view of how CoinTracker differentiates itself from competitors, because the candidate's doubts about the company's vision were what ultimately drove the decision.
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 Cointracker
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Total Spent on Products | |
| String Shift | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Prime to N | |
| Top 3 Users | |
| Google Maps Improvement | |
| Over-Budget Projects | |
| P-value to a Layman | |
| Over 100 Dollars | |
| Minimum Change | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Maximum Profit | |
| Size of Joins | |
| Last Transaction | |
| Hurdles In Data Projects | |
| Project Pairs | |
| Retailer Data Warehouse | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. One describes a LeetCode-style CoderPad screen on basic algorithms. Another describes an HR interview followed by a technical interview on coding fundamentals. Expect a coding-oriented screen, and confirm the format with your recruiter.
Two candidates report a take-home assignment, one involving a prototype of the company's product. Both felt the stated two to four hours was not enough to do it fully, and one notes conflicting time estimates in the instructions. Ask which parts are essential before you begin.
Both take-home candidates report presenting their work to the team. One describes being pressed on implementation details, queue implementations and edge cases. The other was asked why certain features were not built. Prepare to explain your tradeoffs and scope decisions clearly.
One candidate reports three coding and technical interviews and a system design question. They were also asked about years of experience and interest in crypto. Another was told another LeetCode round and systems design would follow the take-home. Rounds may vary by level.
Candidates report conversations with an engineering manager or hiring managers, either between technical rounds or at the end. Two report no offer and no feedback, while the third received an offer and declined it. Follow up with your recruiter to ask about next steps.
