The Huntington Software Engineer interview typically runs 1 round: recruiter/hiring manager conversation plus technical interview and live coding. Timeline was about one scheduled session, and the process was poorly communicated.
$54K
Avg. Base Comp
$104K
Avg. Total Comp
2-3
Typical Rounds
1-2 weeks
Process Length
Our candidates report that The Huntington tends to care less about abstract theory and more about whether you can build and explain a front-end feature in real time. In the one experience we saw, the technical discussion centered heavily on React fundamentals — hooks, the virtual DOM, and React Redux — which suggests the team is looking for practical fluency rather than surface-level familiarity. The live exercise also wasn’t a puzzle; it was a realistic task involving ingesting an API and rendering the result, which points to a preference for engineers who can translate requirements into working UI quickly and cleanly.
A recurring theme is the process itself: the biggest friction came from the mismatch between what the candidate was told and what actually happened. That matters because it signals a company where clarity and adaptability may be evaluated implicitly, even if not stated outright. We’ve seen that candidates who assume a purely conversational screen can get caught off guard when the interview shifts into hands-on coding. For this company, the non-obvious make-or-break factor is being ready for a practical React session even when the setup sounds informal; the interview seems to reward people who can stay composed, ask good clarifying questions, and work through a real product-style task without needing a lot of scaffolding.
Synthetized from 1 candidates 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 The Huntington process.
Applied and got the interview scheduled before I ever really got a clear recruiter call, which already made the process feel a little off. I couldn’t get ahold of the recruiter for details until about an hour before the interview, and even then I was told it would just be a conversation about my resume and projects, with nothing technical or coding-related. That turned out not to be true at all. When I joined, the format was a mix of technical questions and a live coding challenge on a Coderpad-style site, so I felt pretty blindsided going in unprepared.
The technical part was centered on React, especially hooks, the virtual DOM, and React Redux. After that, I had to work through a coding exercise that involved ingesting an API and displaying the information. It wasn’t the hardest algorithm problem, but it did require being comfortable with building something practical under time pressure. I ended up asking to push the interview to another time because I wasn’t set up for that format, and the hiring manager said they might circle back after speaking with other candidates. Overall, the biggest issue wasn’t the difficulty of the questions so much as the lack of transparency about what the interview actually was. I didn’t get an offer, and my main takeaway is to confirm the exact format ahead of time, especially if the role might include React concepts and a live coding task.
Prep tip from this candidate
Be ready for React-specific questions on hooks, the virtual DOM, and Redux, plus a live Coderpad task where you ingest an API and render the results. I’d also confirm the interview format in writing before the call so you’re not surprised by a coding round.
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 The Huntington
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Prime to N | |
| Largest Salary by Department | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Find the Missing Number | |
| Address Schema | |
| Hurdles In Data Projects | |
| Liked Pages | |
| Permutation Palindrome | |
| Integer to Roman | |
| Google Maps Improvement | |
| Delivery Estimate Model | |
| One Element Removed | |
| Session Difference | |
| Size of Joins | |
| The Brackets Problem | |
| Basic Regex | |
| Flatten N-Dimensional Array to 1D Array | |
| Centralized Event Ingestion | |
| Paired Products | |
| Nearest Common Ancestor | |
| Type-ahead Search | |
| Popular Actions | |
| Identifying User Sessions | |
| Valid Anagram |
Synthesized from candidate reports. Individual experiences may vary.
The candidate had difficulty reaching the recruiter for details until shortly before the interview. At that point, the recruiter gave a limited overview of the role and said the conversation would focus on the resume and projects, without mentioning that technical questions and live coding would be included.
The main interview combined React-focused technical questions with a live coding exercise on a CoderPad-style platform. Topics included React hooks, the virtual DOM, and React Redux, followed by a practical task to ingest an API and display the data.
After the candidate asked to reschedule because they were not prepared for the format, the hiring manager indicated they might reconnect after reviewing other candidates. No further rounds were described in the experience.