Credit Karma software engineer candidates report coding and modeling exercises, resume-based technical discussion, and manager conversations about projects and collaboration.
$193K
Avg. Base Comp
$245K
Avg. Total Comp
2 rounds
Typical Rounds
2-4 weeks
Process Length
Credit Karma software engineer interviews in the available reports center on practical coding ability and how clearly you can explain your own work. One candidate described a two-round process: a basic coding and data-structures screen with a question about Go, followed by an engineering-manager conversation focused on the resume, personal projects, teamwork, and situational judgment. Another candidate first completed a form screen, then faced a robot-oriented technical prompt that could involve designing a robot class with methods or reasoning through movement on a grid.
The newer report adds a different technical emphasis: resume and work-history discussion followed by detailed questions on the project stack, task prioritization, deadlines, and Java concepts. These included abstract classes versus interfaces, overloading versus overriding, stack and heap, volatile, immutability, and applying or compromising on a SOLID principle under time pressure. Prepare concise, concrete explanations of every project, design choice, and trade-off on your resume, alongside clear narration of your coding approach.
Reports are limited and describe different technical prompts, so expect variation rather than one fixed script. Practice modeling constraints and edge cases for a coding problem, then rehearse project walkthroughs that connect your technical choices to collaboration and delivery.
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 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 | |
| A/B Testing a Checkout Button Change | |
| Check Matching Parentheses | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Total Spent on Products | |
| P-value to a Layman | |
| Prime to N | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported completing a form with questions before being considered for an interview. Candidates may be asked to summarize projects or their thinking in writing, so make those explanations consistent with the detail you can provide live.
Candidates report a basic coding and data-structures screen in one case, while another reported a robot prompt framed as either a class-design exercise or a grid-navigation problem. Explain your approach as you work and make constraints, methods, and edge cases explicit.
A candidate reported detailed questioning on resume projects, the listed tech stack, daily work, prioritization, and deadlines. That report also included Java OOP distinctions, stack versus heap, `volatile`, immutability, and a SOLID-principle trade-off.
One candidate described a behavioral interview with an engineering manager that focused on personal projects, teamwork, and situational judgment. Be ready to explain what you built, why you made key choices, what you learned, and how you work with others.
