Esri Software Engineer candidates report a recruiter or HR screen, a technical conversation with a manager or engineers, and sometimes an onsite in Redlands. Expect C++ and project depth, one focused coding problem, and "why Esri" questions.
$120K
Avg. Base Comp
$133K
Avg. Total Comp
Not reported
Typical Rounds
3-9 weeks
Process Length
Candidates who interviewed for Esri's Software Engineer role describe a process that leans on conversation more than puzzle volume. One candidate who accepted an offer reports a recruiter call, a roughly hour-long technical screen with a hiring manager covering C++ fundamentals and past projects plus a shared-editor coding exercise, then a full onsite day at the Redlands campus. That onsite reportedly mixed coding, API and system design, cross-platform development and behavioral discussion.
Coding appears to be narrow rather than broad. Another candidate, interviewing with two senior engineers from the Graphics team, was asked to implement the step count for Kaprekar's routine, and reports that this single problem dominated the technical round. A third candidate reports two onsite coding tasks: a Fibonacci bug-fix extended with caching and recursion, and a second problem discussed verbally. That candidate suggests asking to write code on screen.
Motivation and fit come up repeatedly. Reports mention questions about why Esri and why the role, how you learn new technologies, and how you would win leadership buy-in on a decision. One candidate also notes that explaining your own work and tradeoffs mattered more than a perfect fast answer.
Outcomes in the Software Engineer reports are mixed: one offer and three rejections. Timelines also vary, from about three weeks to two months, and one candidate was told to expect up to twelve interviews before the process stalled. Ask your recruiter early about the number of rounds and next steps.
Synthesized from 10 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 Esri 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 Esri
Describing a data project and its challenges
| Question | |
|---|---|
| International e-Commerce Warehouse | |
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| Accessible Data | |
| Blogging Platform Schema | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Prime to N | |
| Find the First Non-Repeating Character in a String | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Upsell Transactions | |
| Top 3 Users | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Rectangle Overlap | |
| Bagging vs Boosting | |
| Largest Salary by Department |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call of roughly 30 minutes or longer with a recruiter or HR contact. Topics include your background, why you are interested in Esri and mapping or geospatial software, and, in one account, location, work authorization and compensation expectations. It is typically conversational.
Candidates report a video interview of about an hour, with a hiring manager in one account and two senior Graphics-team engineers in another. Reported content includes C++ fundamentals, project deep-dives, and a coding exercise in a shared editor, such as counting steps in Kaprekar's routine. Expect one problem explored in depth rather than many.
One candidate reports back-to-back interviews with different managers who asked about domain knowledge, how they pick up new technologies, and how they would get leadership buy-in for a decision. That candidate was told to expect as many as twelve interviews and then did not hear back, so ask about the timeline and expected stages.
Two Software Engineer candidates describe an onsite. One reports five sessions covering coding, API and system design, cross-platform development and teamwork, plus lunch and a campus tour. The other reports mostly behavioral questions, two coding problems, and a final interview with the Desktop development CTO. Be ready to draw architecture and discuss past projects.
