Itron software engineer interviews, as candidates describe them, start with an HR or recruiter conversation. They move to experience-focused discussion and technical questions on fundamentals, past challenges, and system design.
$124K
Avg. Base Comp
$140K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Itron's software engineering interviews as conversational and formal, with a focus on your own work. One software engineer who received an offer began with a brief HR phone screen against the job description's preferred requirements. Next came a hiring manager conversation and a technical round. That candidate said the technical questions were not algorithm-heavy. Interviewers asked for a specific problem they had solved at work and how they solved it. Prepare two or three concrete work stories with clear challenges and outcomes, and be ready to explain how past roles connect to the position.
Another software engineer, who did not receive an offer, started with a resume walkthrough. Questions covered frameworks and why they were chosen, SQL after MongoDB came up, authentication versus authorization, arrays versus linked lists, and real-world examples of stacks and queues. That candidate wished they had stated trade-offs more explicitly. Practice explaining why you chose a tool, not just what it does.
A principal-level candidate reported a first technical round tied to the job description. A second technical round covered basic system design, when to choose a technology, and how it works internally. That candidate found the second round unclear and was rejected. If a question is ambiguous, ask the interviewer to narrow it. The evidence is limited, so confirm your exact process with your recruiter.
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 Itron 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 Itron
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Data Pipelines and Aggregation | |
| Mapping Nicknames | |
| Green Dot | |
| Uber Eats Customer Experience | |
| Safe Deployments | |
| Decision Tree Evaluation | |
| Your Strengths and Weaknesses | |
| Payment Data Pipeline | |
| Electricity Supply | |
| Stakeholder Communication | |
| Underpricing Algorithm | |
| Why Do You Want to Work With Us | |
| Simple Explanations | |
| LRU Cache 1 | |
| Accessible Data | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening conversation with HR or a recruiter. One offer recipient described a brief, no-nonsense phone screen that checked the job description's preferred requirements. Another candidate was asked to walk through their resume, projects and internship work, so expect to explain what you built and why.
One candidate who received an offer described a hiring manager discussion focused on what they had actually done in previous roles and how it applied to the position. It may help to prepare specific examples with outcomes rather than general statements. Other candidates did not describe this stage, so it may not occur in every process.
Reported technical questions vary. One candidate was asked in a technical round to describe a real problem they solved at work. Another candidate, in a recruiter-led conversation, was asked about frameworks, SQL after MongoDB came up, authentication versus authorization, and core data structures. That candidate also recalled one coding question but not its details. Candidates did not describe heavy algorithm drilling, but depth and trade-off reasoning appear to matter.
A principal-level candidate reported a second technical round on basic system design, when to use particular technologies, and how they work internally. That candidate found the questions drifted from the job description and were unclear. Senior applicants may want to prepare design reasoning and be ready to ask for clarification.
