Real, anonymous reports from people who interviewed for Software Engineer at J.B. Hunt Transport, newest first and distilled into what to expect across the loop.
I ended up meeting recruiters at a career fair and got pulled into an interview shortly after, with the virtual session coming about a week later. The call format was pretty simple: a recruiter and another interviewer joined, and the conversation leaned heavily behavioral. We spent most of the time on my background and how I’d worked in teams, with only a small amount of programming-style discussion. I didn’t have to complete a separate coding assessment, which made the whole round feel more like fit and communication than problem solving.
I interviewed in a more structured two-stage process. After the initial screening period, I got a first round interview with the hiring manager plus two other team members, and the technical questions were driven mostly by the developer on the panel. The questions felt basic, but the thing that threw me off was how tightly the answers were expected to match the way their IT shop runs.
The interview process typically begins with a recruiter call followed by a series of interviews that may include technical, behavioral, and leadership assessments, often spanning several weeks. Candidates reported varying experiences with the length and structure, with some facing long panel days and others experiencing shorter, more casual conversations.
Many interviews emphasized behavioral questions and cultural fit, focusing on past experiences, teamwork, and communication skills rather than deep technical evaluations. Candidates noted that these discussions often felt more like conversations than formal assessments.
Technical rounds varied in depth, with some candidates facing hands-on coding tasks related to Java and Spring Boot, while others encountered basic technical questions that aligned closely with the company's internal practices. The technical assessment often felt low-pressure but could also lack rigor in evaluating broader technical competencies.
Candidates expressed frustration with the communication throughout the process, citing delays in feedback and a lack of clarity regarding their status. Some felt that the interviewers were not fully engaged, which negatively impacted their overall experience.
The composition of interview panels varied, with some candidates experiencing interviews with a mix of senior engineers and managers, while others felt evaluations were overly reliant on a single interviewer. This inconsistency affected candidates' confidence in the fairness of their assessments.
Candidates reported mixed feelings about their overall experience, with some appreciating the professional and friendly atmosphere, while others felt the process was poorly organized or mismatched with their expectations. The outcome often left candidates feeling uncertain about their fit for the role.