Four candidates describe LeanIX software engineer interviews as an HR call, a hiring manager conversation, a technical stage, and sometimes a take-home or presentation. Reports range from 4 to 6 steps, and three of the four ended in offers.
$110K
Avg. Base Comp
$130K
Avg. Total Comp
4-6 rounds
Typical Rounds
1 month
Process Length
Candidates describe the LeanIX software engineer interview as a conversational process that starts with HR and a hiring manager and then moves to a technical stage. Three of the four reports ended in offers, and one senior candidate was rejected after a six-step process.
The hiring manager conversation comes up in every report. Candidates were asked about career motivation, why LeanIX appeals to them, and how their past experience maps to the role.
The technical stage varied by level. One Software Engineer II candidate reports a two-hour live task building a REST API with Spring Boot, JPA persistence, and scheduling logic. A working student reported a discussion of OOP, database design, and data structure trade-offs. The senior candidate described the live coding as straightforward, with interviewers more interested in thinking process than optimization.
Some candidates mention a take-home assignment or a prepared project presentation. The senior candidate spent considerable time on a take-home before a two-hour technical interview and a 90-minute final round with two senior engineers. A fullstack candidate gave a presentation on a pre-assigned project. Ask your recruiter early which of these formats applies to you.
Two candidates say they finished in about a month. The sample is small and the roles span several levels, so check the exact stages with your recruiter. One candidate also reports a canned rejection with no feedback, so plan to keep applying elsewhere while you wait.
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 LeanIX process.
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 LeanIX
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Find the Missing Number | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Raining in Seattle | |
| Minimum Change | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Size of Joins | |
| The Brackets Problem | |
| Scrambled Tickets | |
| Weighted Keys | |
| Flight Records | |
| Rectangle Overlap | |
| Daily Retention Summary | |
| Project Pairs | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call with HR or talent acquisition that covers background and expectations. Descriptions are friendly and fairly standard. One candidate notes that some details were discussed by phone, and would have preferred them in writing first.
Candidates report a conversation with a hiring manager about career goals, why LeanIX interests them, and how their experience connects to the role. One senior candidate describes it as about an hour. A working student describes a 30-minute session. Prepare specific examples of what you want to learn.
The technical stage differs across reports. One candidate describes a take-home followed by a two-hour technical interview. Another reports a two-hour live Spring Boot, JPA and scheduling task. A working student reports a discussion of OOP, database design and data structures. Format may depend on level, so confirm it with your recruiter.
Candidates describe a final stage with different interviewers. The senior candidate reports 90 minutes with two senior engineers. Others mention a behavioral discussion with a director or a call with another manager. A fullstack candidate also presented a prepared project before the final call. Outcomes reported include offers and one rejection with no feedback.
