Real, anonymous reports from people who interviewed for Software Engineer at GlobalFoundries, newest first and distilled into what to expect across the loop.
Get your personalized GlobalFoundries 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.
My process felt refreshingly simple and calm. It started with an HR conversation to get things moving, then I had a manager interview and finally a round with a senior engineer. The whole schedule was quick—about a week and a half—and what surprised me was how little it leaned on deep technical questioning.
Most of the conversation centered on behavioral fit and how I would show up in the role, and there was also time for me to ask questions at the end. I remember thinking the panel gave me a genuine window to understand what it was like internally, and I tried to steer my questions toward how teams operate—things like employee resource groups and how that culture shows up in practice.
3 months ago
Average Positive Brisbane
After a recruiter call to check my background and fit, I ended up with a fairly structured sequence of interviews. The next steps were with engineering leadership—two thirty-minute conversations with engineering managers—plus an additional assessment-style Q&A. The manager and supervisor discussions were grounded in my experience and knowledge, but they still leaned heavily into behavioral prompts, trying to understand how I think and how I operate day to day.
The assessment Q&A felt more like a test of how I handle unfamiliar problems. It focused on critical thinking and problem-solving rather than coding or LeetCode-style questions; one version of the process specifically noted no programming questions. Between rounds, the people I spoke with were professional and it didn’t drag out too long overall—though another experience from this set highlighted that when the process stretches to months, there was less clarity and some borderline unprofessional recruiting moments. Either way, the format was consistent enough that I always knew what kind of question was coming next.
5 months ago
Difficult Negative Vereinigte Staaten von Amerika
My process felt excessive for the level they advertised, and it started with a recruiter screen about my resume and basic fit. From there, I moved int…
7 months ago
Easy Negative Singapur
Right after my self-introduction, it seemed like HR realized there was a mismatch with my technical background and made a call to the interviewer base…
7 months ago
Difficult Positive Malta, NY
I went through a two-round technical-heavy interview where almost everything was about technical depth. Each round lasted about an hour and there were…
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 & Timeline
The interview process typically consists of an initial HR call followed by multiple rounds with engineering managers and team members, often taking about 1-2 weeks to complete. However, some candidates reported longer timelines, with follow-ups taking several weeks or even months.
HR callManager interviewsTimeline
Behavioral & Cultural Fit
Most interviews emphasize behavioral questions and cultural fit, focusing on how candidates align with the company's values and day-to-day operations rather than deep technical assessments. Candidates are encouraged to ask questions about team dynamics and company culture.
Behavioral questionsCultural fitTeam dynamics
Technical Depth & Focus
While some candidates experienced intense technical questioning, particularly around semiconductor concepts and fundamentals, others noted a lack of technical depth, with interviews leaning more towards general problem-solving and critical thinking rather than specific coding challenges.
The overall tone of interviews varies, with many candidates reporting a friendly and conversational atmosphere, while others experienced disengagement or unprofessionalism from interviewers, impacting their overall impression of the process.
Friendly atmosphereEngagementProfessionalism
Assessment Style
Candidates often encounter assessment-style Q&A sessions that test critical thinking and problem-solving skills rather than traditional coding tests. This format aims to gauge how candidates approach unfamiliar problems.
Assessment Q&ACritical thinkingProblem-solving
Feedback & Closure
Candidates appreciated receiving constructive feedback and clear communication throughout the process, even when not receiving an offer. This respectful closure contributed positively to their overall experience.