Volver a la comunidad

AMD entrevistas conductuales

Preguntas de entrevista investigadas, descripción del proceso y señales de dificultad en AMD, compiladas por el equipo de investigación de Primly.

6 experiencias Dificultad 3.2/5 Semiconductors

IT Support Technician / Desktop Support

phone_screen · Dificultad 2/5

The process typically opens with a recruiter screen verifying shift requirements, onsite expectations, customer-service orientation, and baseline troubleshooting experience. Candidates then report a technical phone or video screen with an IT lead covering common enterprise issues such as Windows imaging, account access, endpoint security tooling, and ticket triage. A final round often includes a small panel with the local IT manager and a senior technician focused on how the candidate handles escalations, prioritization, and supporting engineers with time-sensitive issues. Some candidates are asked to walk through a live troubleshooting scenario verbally, clarifying questions, hypotheses, and next steps rather than performing hands-on work. Decisions are frequently made quickly after the final conversation, with timing dependent on headcount approvals and background checks.

  • A developer reports their laptop is slow after a security update. How do you triage the issue and decide what to check first?
  • How would you troubleshoot a user who cannot access VPN and also cannot authenticate to corporate Wi-Fi?
  • Tell about a time you dealt with an upset internal customer. What did you do to resolve the issue and preserve trust?
  • If multiple executives and engineers submit urgent tickets at the same time, how do you prioritize and communicate ETAs?
  • What does good IT support look like in an engineering-heavy environment where downtime can block critical work?

Manufacturing / Process Engineer (Semiconductor Packaging or Test)

onsite · Dificultad 3/5

The process commonly begins with a recruiter phone screen, then a technical screen with the hiring manager or a senior engineer to confirm experience with process control, yield, reliability, and working with external manufacturing partners. Candidates frequently report a multi-interviewer onsite or extended virtual panel, often including manufacturing engineering, quality or reliability, and a program or operations stakeholder. Interviews tend to be structured around problem solving, root-cause methods, and cross-functional communication, using examples from high-volume manufacturing or NPI ramps. Some candidates encounter a whiteboard-style exercise around interpreting yield paretos, defining experiments, or outlining an FA workflow from symptom to containment and corrective actions. Final steps often include a manager interview focused on prioritization and influencing without authority, followed by references, with total cycle time commonly taking a few weeks.

  • Describe a time you improved yield on a critical step. What data did you look at first, and how did you prove the root cause?
  • Given a yield drop concentrated in one bin after a packaging or test change, how would you structure the investigation from containment through corrective action?
  • How do you decide whether to run a DOE versus a focused single-factor experiment when cycle time and wafer availability are constrained?
  • A supplier is pushing back on a process window tightening request due to throughput impact. How do you negotiate a path that protects quality and schedule?
  • What operating principles guide how you communicate risk and bad news during a ramp or excursion?

Product Marketing Manager (EPYC / Data Center)

virtual · Dificultad 3/5

The process typically starts with a recruiter screen focused on domain fit, location and work authorization, and how the candidate has marketed technical products to enterprise buyers. A hiring manager call often follows within a week and goes deep on positioning, segmentation, and the ability to translate platform-level advantages into customer outcomes for cloud and enterprise. Candidates report a panel round next with cross-functional partners such as product management, sales, and sometimes engineering, testing collaboration, executive presence, and comfort with technical depth. Many candidates complete a case-style exercise or short presentation, such as a messaging framework or competitive teardown, and then present it live with Q&A. Final steps usually include a senior marketing leader interview and reference checks, with an end-to-end timeline often spanning a few weeks depending on scheduling and internal approvals.

  • How would you position AMD EPYC against Intel Xeon and Arm-based server CPUs for a cloud customer that cares most about TCO and performance per watt?
  • Walk through a product launch you led for a technical platform product. What was the narrative, which audiences did you target, and what did you measure?
  • If engineering gives you a set of benchmark wins, how do you decide which claims are credible, repeatable, and safe for external messaging?
  • A top OEM partner asks for differentiated messaging that conflicts with global positioning. How do you handle alignment and approvals?
  • What does 'customer-centric' look like in your work, and how have you incorporated field feedback into messaging or content plans?