Interview Experiences

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

Share yours, earn XP

3 stories

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

AMD Construction GroupSoftware Engineer
Reported Aug 2026

AMD Construction Group Software Engineer Interview Experience: Linux, embedded work, and networking

After a recruiter call, I entered a structured technical loop that lasted a few weeks. The recruiter covered my background and the rough process, and about a week later I was in the first technical screen. The later conversations with engineers and the hiring manager focused mostly on my past projects, especially Linux systems and embedded-style software work. I also completed a coding session on…

Technical Screen0
AMD Construction GroupSoftware Engineer
Reported Jul 2026

AMD Construction Group Software Engineer interview

I first spoke with the hiring manager about the team and my day-to-day work in earlier roles. The rest of the process was several technical panels, with scenario-based questions that tested both problem solving and technical range. The panels covered computer architecture, UART, SPI, I2C, AXI, APB, AHB, coverage, assertions, UVM fundamentals, debugging, and verification strategy. One round also t…

Technical Screen0
AMD Construction GroupSoftware Engineer
Reported Jul 2026

AMD Construction Group Software Engineer Interview Experience: Medium LeetCode, RTL, and CUDA optimization questions

My process started with an HR-style phone pre-screen about my background and basic logistics. Then it became very technical. In a manager-style round, I walked through my resume and projects, which led into coding on a couple of medium LeetCode problems, mostly strings and arrays where edge cases mattered. The next technical discussion stayed in that problem-solving lane, with emphasis on RTL kno…

HR 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