Four candidates describe ASU Software Engineer interviews as friendly and practical. They report panel conversations, project discussions, easy or open-ended technical problems, and a focus on clear communication.
$72K
Avg. Base Comp
$75K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe ASU Software Engineer interviews as conversational rather than adversarial, and the technical bar they report is modest. Across four accounts, explaining your work clearly comes up more than any hard algorithm drill.
One candidate faced a panel of three senior team members with about nine questions on testing experience, coding technologies, technical depth and team fit. That candidate was asked how specific languages had delivered impact in past roles. Another met a team lead, a product manager and a director, and got standard behavioral questions about strengths, weaknesses, juggling several projects and motivation. The coding portion was a couple of easy problems, including reversing a string in the language of their choice.
A third candidate began with a screen on programming fundamentals and a practical, role-related problem. The second round was with hiring managers who were not deeply technical and asked for core concepts explained in plain terms. A fourth described a relaxed session with a manager, a future colleague and other engineers. It centered on a deliberately vague mathematical problem, where asking clarifying questions and justifying the approach mattered, plus questions about coursework and projects.
To prepare, rehearse two or three project stories that show impact and testing habits. Practice basic coding with clean, working solutions. Get comfortable talking through ambiguous problems step by step before you write code. Three of the four candidates reported offers. One of them declined after finding the recruiter's exploding offer and unwritten, low salary unacceptable, so confirm timelines and get terms in writing.
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 Arizona State University 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 Arizona State University
Describing a data project and its challenges
| Question | |
|---|---|
| Simple Explanations | |
| P-value to a Layman | |
| User Experience Percentage | |
| CNNs vs Intensity-Based Features | |
| Slow SQL Query | |
| Count Transactions | |
| Legacy System Heartbeat Monitor | |
| Swap Variables | |
| Digital Classroom System Design | |
| Last Element of a Singly Linked List | |
| Incorrect Packets | |
| Optimal Host | |
| Why Do You Want to Work With Us | |
| Testing Constraints | |
| Open Source Reporting Pipeline | |
| Your Strengths and Weaknesses | |
| Stakeholder Communication | |
| Justify a Neural Network | |
| Evaluate News | |
| Design Poker Schema | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial screen before the main conversations. One was walked through basic programming concepts by a contact tied to the hiring team, then given a practical, role-related problem. Another describes a standard initial screening. Expect fundamentals rather than hard algorithms.
Candidates describe conversations with several people. Reported panels include three senior team members, a team lead with a product manager and a director, and a manager with a future colleague and other engineers. Hiring managers may not be deeply technical, so be ready to explain ideas simply.
Candidates report questions about past projects, coursework, testing experience, strengths and weaknesses, managing multiple projects and why they want the role. One was asked how particular coding languages created impact in earlier jobs. Prepare concrete examples with outcomes.
Reported technical problems vary. One candidate solved a couple of easy coding questions, such as reversing a string. Another got a deliberately vague mathematical problem that rewarded clarifying questions and reasoning. A third solved a practical, role-related challenge. Prepare for fundamentals and talking through your approach.
Three candidates report receiving offers. One reports the recruiter pushed an exploding offer with a two-day deadline, nothing in writing and a low salary, and declined. Another says the process moved quickly after the second conversation. Timelines may vary, so ask about deadlines and request terms in writing.
