Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4 stories

Likes earn the author +10 XP for the first 3 likes each day

GlobalFoundriesSoftware Engineer
Reported Aug 2026

GlobalFoundries Software Engineer interview with setup and hold questions

After the recruiter conversation, I had two engineering-focused technical rounds. The first was with someone on the design side. We went through my resume and academic projects before discussing C. The second was with someone on the verification side and was noticeably tougher. That verification interview focused on fundamentals: asynchronous design, flip-flop behavior, assertions, and setup-and-…

Technical Screen0
GlobalFoundriesSoftware Engineer
Reported Jul 2026

GlobalFoundries Software Engineer recruiter and interview experience

After a recruiter step, I had a short set of interviews with several people. The conversations balanced technical and behavioral questions, and everyone stayed respectful and professional. Things moved quickly with little back-and-forth, and I heard back soon after the interviews. It was a smooth process without much stress or delay. My impression was that they were assessing fit efficiently. Loc…

Technical Screen0
GlobalFoundriesSoftware Engineer
Reported Jul 2026

Software Engineer interview at GlobalFoundries: supervisor to HR

The process began with people closest to the role and finished with HR. I spoke separately with a supervisor and a manager. Their questions drew on my experience and knowledge, with behavioral material mixed in, and seemed aimed at understanding how I would think and operate from what I had done before. Later, an assessment-style Q&A tested critical thinking and problem solving rather than memori…

0
GlobalFoundriesSoftware Engineer
Reported Jul 2026

GlobalFoundries Software Engineer interview: conversational department panel

My interview began with a behavioral conversation with two people from the department. The focus was on day-to-day fit and how I would work, and it never became a technical grilling. What I liked was having time at the end for many questions. I planned ahead to ask about things that mattered to me, including employee resource groups. That exchange made the interview feel more like a conversation…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP