Four candidates describe an Earnin Software Engineer process built around a recruiter call and a hiring-manager or engineer conversation that mixes behavioral, light coding and architecture questions. All four were rejected.
$175K
Avg. Base Comp
$193K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The Earnin Software Engineer interview, as four candidates describe it, starts with a recruiter call of about 30 minutes and then moves to a conversation with a hiring manager or engineer. All four candidates were rejected, so the evidence says more about what to expect than about what gets an offer.
The coding was described as easy to medium. One candidate got a target sum problem and focused on explaining the approach and logic. Another got an easy LeetCode-style exercise. A third reports a technical round that began with behavioral questions and then moved to a LeetCode-like platform. That candidate found the problem statement unclear and says the interviewer seemed to want one specific solution path. If you are given an ambiguous prompt, state your assumptions out loud and confirm the approach before you code.
Behavioral material took up much of the time. Candidates mention being asked about a proud project, handling ambiguity, a biggest achievement and a difficult problem they solved. Prepare concrete stories for each.
One candidate's supposed culture-fit conversation turned into an architecture walkthrough of a past project, with the interviewer probing design trade-offs. Be ready to explain the decisions behind your best project even if the round is billed as non-technical.
Candidates report little or no feedback after rejection, and one was told up front that none would be given. Go in expecting to judge your own performance afterward.
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 Earnin process.
The process was short. I had a fairly standard phone call with a recruiter first, and then a one-hour video call with the hiring manager. The coding portion was an easy LeetCode-style exercise, so nothing that demanded a clever trick, but I still wanted to walk through my approach clearly. Most of the hour went to experience questions and behavioral questions. The overall tone was pleasant and the conversation felt comfortable.
The part I'd flag is what came after. The recruiter's prep message told me up front that I wouldn't get feedback, and that held true. The rejection arrived as a generic message with no specifics. I know it's common for companies to skip feedback, even for senior roles, but that doesn't make it any easier to learn from. If you go through this process, expect to walk away without a clear sense of where you fell short, and plan accordingly.
Prep tip from this candidate
Be ready to spend much of the hiring manager round on experience and behavioral questions, not just the easy coding exercise. Since you likely won't get feedback after a rejection, write down the questions you were asked right after the call while they're still fresh.
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.
| Question | |
|---|---|
| Biggest Tip | |
| Mouse Search | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Merge Sorted Lists | |
| Total Spent on Products | |
| Top 3 Users | |
| String Shift | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Last Transaction | |
| Like Tracker | |
| Google Maps Improvement | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Duplicate Rows | |
| P-value to a Layman | |
| Maximum Profit | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a routine recruiter call of about 30 minutes. One says it covered the role, the team and what to expect in the interviews. Another calls it a standard phone screen. Expect background and logistics questions rather than a technical test.
Two candidates describe a one-hour video call with the hiring manager that mixed experience and behavioral questions with a coding exercise. One was asked a target sum problem. Another found the coding easy. A third candidate's session began with behavioral questions before coding on a LeetCode-like platform.
One candidate expected a team and culture conversation, but it was rescheduled after the hiring manager fell ill. The replacement engineer asked for a walkthrough of a past project's architecture and pushed on the design choices. Other candidates did not report this, so treat it as a possibility rather than a standard round.
All four candidates were rejected, in several cases with little or no feedback. One heard back five days after the interview, another the next day, and a third about two weeks later. One candidate was told that later rounds include system design and a debugging session, but none of the four reached them.
