Credit Karma Software Engineer interview typically runs 2 rounds: technical coding and behavioral with an engineering manager. It usually takes about 2 hours total and is fairly standard, with a lightweight screening step sometimes before the rounds.
$118K
Avg. Base Comp
$296K
Avg. Total Comp
2-3
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Credit Karma is less interested in flashy algorithm tricks than in whether you can model a problem cleanly and explain the tradeoffs as you go. That shows up in the robot prompts, which ranged from a robot class with methods to a grid-movement problem, and in the mix of easy, medium, and hard questions that still stayed grounded in familiar data structures. Even when the round felt standard, the pressure point was not novelty; it was whether you could stay organized under time pressure and make the solution feel deliberate rather than improvised.
A recurring theme is that the company also pays attention to the engineering context around the code. One candidate was asked about Go, which suggests they care about whether you can ramp into their stack without hand-holding. Another successful candidate spent a lot of time walking through personal projects, with emphasis on what you built, why you built it, and what you learned. That tells us the bar is not just correctness — it’s whether your experience sounds real, specific, and transferable. The strongest candidates here seem to be the ones who can connect their technical choices to product thinking and collaboration, not just produce an answer on a whiteboard.
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 Credit Karma process.
The part that stood out most was the technical interview, because it was much more about modeling than just coding quickly. Before that, I had to go through a form screening where I filled out a set of questions to be considered for the interview at all, so the process started pretty lightweight and felt like a basic qualification check. After that, I spoke with a Software Engineer for the technical round, and the main prompt was a robot-related coding question. In my case it was framed as creating a robot class object with methods, and the other version of the round was a robot grid problem on Leetcode, so the core theme was clearly around designing or reasoning through robot movement and behavior under constraints.
Prep tip from this candidate
Be ready for robot-style coding prompts that can show up either as a class design exercise or as a grid-navigation problem. I would practice explaining edge cases and the method structure clearly, since the interview seemed to care about how you model the problem as much as whether the code works.
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 Credit Karma
Write a function that tests whether a string of brackets is balanced.
| Question | |
|---|---|
| Type-ahead Search | |
| Walking Robot | |
| Offer Matching API Design | |
| Check Matching Parentheses | |
| A/B Testing a Checkout Button Change | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Like Tracker | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Prime to N | |
| Cumulative Distribution | |
| Find the First Non-Repeating Character in a String | |
| Hurdles In Data Projects | |
| Over-Budget Projects | |
| Top 3 Users | |
| Google Maps Improvement | |
| Total Spent on Products | |
| Find the Missing Number | |
| Over 100 Dollars | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
Candidates first complete a survey or form with questions about their background, projects, and fit for the role. Credit Karma appears to use this step as an early qualification check before inviting applicants to interview.
A software engineer or senior engineer conducts a coding round, often on HackerRank or in a virtual format. The problems can range from basic data structures and string manipulation to more challenging tree, dynamic programming, or robot-themed modeling questions, and candidates may also be asked about language experience such as Go.
An engineering manager interviews the candidate about their resume, personal projects, teamwork, and situational judgment. This round is relatively light technically and focuses on how the candidate thinks, collaborates, and explains past work.