Real, anonymous reports from people who interviewed for Software Engineer at Jabil Circuit, newest first and distilled into what to expect across the loop.
Get your personalized Jabil Circuit Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I interviewed in a relatively average-difficulty process that started relaxed and then tested situational judgment and role understanding, with some quality-and-turnover signals.
Step 1 (friendly chat) — an initial conversation designed to get to know me before any deeper questioning.
2 months ago
Average Neutral Bayan Lepas
I went through a short interview cycle that centered on explaining my prior work, with one process being especially condensed.
Phone screen — high-level qualifications and background.
3 months ago
Average Positive Solothurn
I went through an HR/manager-style screening flow that felt mostly straightforward, though one attempt stalled due to poor scheduling. HR screen — a s…
7 months ago
Average Positive Minsk
I interviewed for a Software Engineer role with an early recruiter touch, then a mix of technical conversation and coding, and in one case heavier man…
9 months ago
Average Neutral Saint Petersburg, FL
I went through interviews that were personable and low-drama, but the outcomes still varied from rejection to no offer. Recruiter phone screen — I sta…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process typically involves an initial recruiter screen followed by multiple rounds, including technical and managerial discussions, often culminating in a panel interview. Candidates noted that the flow could vary significantly in terms of organization and communication.
Recruiter screenPanel interviewMulti-round
Technical Assessments
Candidates experienced varying levels of technical questioning, including coding tests, electronics assessments, and architecture-style questions. The depth of technical inquiry often depended on the specific interview track and could range from basic to highly specialized topics.
Behavioral interviews were common, with many candidates being asked to respond to STAR-format questions about their experiences and fit for the role. The emphasis on behavioral questions varied, with some interviews being more technical and others focusing heavily on personal fit.
STARBehavioral questionsFit assessment
Communication & Scheduling Issues
Several candidates reported challenges with scheduling and communication throughout the interview process, including delays, rescheduling, and lack of follow-up. These issues often impacted the overall experience and left candidates feeling frustrated.
Scheduling issuesCommunicationFollow-up
Onsite Experience
Onsite interviews often included facility tours and informal discussions with team members, providing insight into the company culture and daily operations. Candidates found these visits informative but noted that they could also be less structured and overwhelming.
Onsite interviewFacility tourTeam interaction
Overall Difficulty & Candidate Sentiment
The overall difficulty of the interview process was reported as average, with candidates expressing mixed feelings about their experiences. While some found the atmosphere friendly and supportive, others described it as disorganized or overly formal, affecting their confidence.