HII software engineer interviews reported by candidates lean conversational: HR or recruiter screens, behavioral questions, light technical talk on testing and complexity, and sometimes slow follow-up.
$116K
Avg. Base Comp
$142K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe HII's software-related interviews as conversational rather than code-heavy. The technical content they mention is modest: a software test engineer candidate was asked to talk through test cases, including Big O for array operations, and was not asked to write code live. A software engineer candidate reported greedy versus brute-force questions in a single hour-long conversation, and an Engineer 1 candidate was asked about testing methodologies, testing a simple function and bug reports.
Behavioral and company questions show up repeatedly. Candidates report being asked what they know about HII, about conflict, and about solving a difficult problem. Two internship candidates were also asked about Newport News Shipbuilding, so it is worth knowing what the company does there. Those two interviews were prerecorded video formats, and they are internship reports rather than full-time software engineer ones.
Expect the role itself to need clarifying. One candidate who applied as a software engineer said the role turned out to be software testing, and asked about security clearance requirements without getting a clear answer. Ask about the day-to-day work, clearance and relocation early.
Timing and communication varied. One candidate heard nothing for about six weeks after a single interview, and another went through seven interviews over several months before a rejection after about three months. Both of these candidates received no offer, so follow up politely and keep other options open. Prepare short STAR stories, practice explaining your reasoning aloud, and review basic complexity and testing concepts. The number of reports is small, so treat these as examples rather than a fixed format.
Synthesized from 6 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 Huntington ingalls industries process.
The process moved pretty quickly, which was nice. I started with an HR screening call that was straightforward—mostly getting to know me and making sure my background aligned with the role. Then I had a semi-technical interview where the conversation was more exploratory than intense. They asked me about my troubleshooting approach when facing real-world problems, like helping a coworker whose monitor had gone blank. It was less about a canned answer and more about walking through my thought process step by step.
The final round was a fully technical zoom interview with the hiring manager and team. This is where things got more substantive. Instead of live coding, they presented technical test cases and had me talk through how I'd approach them—some questions leaned into software concepts like Big O notation for array operations, while others touched on hardware considerations. The vibe throughout was conversational rather than interrogative. They were genuinely interested in how I think and solve problems, not just whether I could regurgitate textbook answers. No one asked me to write code on the spot, which I appreciated, but I did need to articulate my reasoning clearly. The whole thing reinforced that they care about your fundamentals and your ability to communicate technical ideas, so going in with a solid grasp of algorithmic complexity and the core skills listed in the job description made a real difference.
Prep tip from this candidate
Focus on articulating your problem-solving process out loud rather than memorizing solutions. Be ready to discuss Big O complexity and how you'd approach troubleshooting real-world technical issues—they want to hear your reasoning, not just your answer.
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 Huntington ingalls industries
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| Game Feature Home | |
| Hurdles In Data Projects | |
| User Event Data Pipeline | |
| Loan Model | |
| Deciding Between Solutions | |
| Distributed Authentication Model | |
| Fixed-Length Arrays: Deletion | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records | |
| Prime to N | |
| Largest Salary by Department | |
| Upsell Transactions |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR call, or a quick callback after applying online. One candidate described it as straightforward, mostly about background and fit. Timing before this stage appears to vary, so it may be worth confirming the role's actual responsibilities and clearance needs here.
Reports describe conversational questions rather than intense technical drilling. Candidates were asked about troubleshooting a real-world problem, conflict, difficult problems they solved, and what they know about HII. Preparing concise STAR-format stories and company knowledge, including Newport News Shipbuilding, is a reasonable approach.
Candidates report technical talks rather than coding exercises: test cases, Big O for array operations, greedy versus brute force, SDLC, testing a simple function, and bug reports. One candidate had a Zoom interview with the hiring manager and team and said clearly explaining their reasoning is what mattered, so practice doing that.
Reported follow-up was inconsistent. One candidate waited roughly six weeks with no contact, another got a rejection after about three months, and one received a rejection email. Some internship candidates received offers. Ask for contact details before leaving and follow up after the promised window.
