AMD Analog and Mixed-Signal Design Careers in Santa Clara

The old AMD Analog Design Engineer vacancy and its headline compensation should be treated as expired. Current AMD requisitions control salary, hybrid status, visa sponsorship and location. A current Santa Clara RTL/Logic Design Engineer example is hybrid, lists $166,400–$249,600 and says visa sponsorship is unavailable, but it is digital HBM/GDDR work—not evidence that the old analog role is open. Analog and mixed-signal candidates should show transistor-level design, simulation, PVT and Monte Carlo analysis, layout collaboration, parasitic closure and lab correlation relevant to the live requisition.

Evidence that demonstrates fit

Prepare two design cases: one block-level analog or mixed-signal example and one silicon or lab-debug example. State specifications, architecture trade-offs, process or voltage constraints, simulations, layout interaction, parasitic effects, verification and measured result. Evidence may include SPICE, schematic capture, PVT corners, mismatch analysis, noise, jitter, linearity, stability, power, area or yield depending on the role. Sanitize foundry, customer and unreleased chip information. A digital HBM/GDDR opening calls for RTL, Verilog, timing, power and area evidence instead; do not present it as analog experience.

Build a requirement-to-evidence matrix with requirement, proof, result and gap columns. Copy a current official requirement into the first column. Add one specific, truthful example and its result. Label missing proof as a gap rather than masking it with keywords. Location, legal status, safety, schedule or privacy mismatches require a decision, not résumé polish.

Write two short cases containing context, constraint, personal action, quality or safety check and result. Reduce each to one résumé bullet. Keep confidential customers, systems, health data, facility information and proprietary metrics out. A credible sanitized example is stronger than impressive detail that should not be public.

How to apply or use the guidance

Search AMD Careers for analog, mixed signal, SerDes, PHY, memory and Santa Clara. Record the job ID, posting status, exact discipline, location, compensation band, hybrid label and visa wording. Build a requirement-to-evidence table before tailoring. Apply through careers.amd.com only. AMD’s current fraud alert says recruiters do not use personal email, demand fees, make offers by text, charge for résumé review or request identity documents during the application process.

Verification checklist

1. Open the official employer or primary source.
2. Confirm active status, requisition ID and the date checked.
3. Record location, eligibility, deadline, work model and official next action.
4. Compare mandatory criteria with evidence you can substantiate.
5. Identify one decisive gap before investing more time or money.
6. Save the official URL and application confirmation.
7. Stop when someone demands payment, secrets or unofficial transfer of sensitive information.

Practical exercise and decision aid

Create a next-48-hours card with one verification, one evidence improvement and one communication action. Make each small enough to complete. At the end, mark completed, learned and changed. The loop supports a return visit and makes the page useful even when a legacy vacancy is closed.

Use a stop/continue table. Continue when the official source is current, core requirements fit and the next cost is reasonable. Pause when location, legal status, accessibility, security, safety or money is unclear. Stop when a recruiter guarantees an outcome, hides the accountable entity, requests payment or tries to bypass normal verification.

Safety and stale-content cleanup

Remove the old $312,000 claim and never transfer a range between requisitions, levels or locations. Label the current RTL role as a role-family comparator checked on 2026-08-09, not the vacancy being rebuilt. Do not publish proprietary schematics, tape-out details, foundry data, security-sensitive systems or employer-owned test results.

• Replace urgency and guaranteed outcomes with dated verification.
• Do not infer remote work from the site brand or a computer-based role.
• Keep employer, contractor, agency and research identities distinct.
• Put official sources ahead of copied job pages.
• Do not collect identity, bank, health, immigration or clearance data.
• Recheck canonical, robots, schema, outbound links and dates in QA.
• Keep unpublished if the intent cannot be served honestly.

Frequently asked questions

Is the old analog role open?

No current opening should be inferred; search the official portal for a live requisition.

Does the current RTL range apply to analog roles?

No. It belongs only to that requisition, level and location.

What portfolio evidence matters?

Specifications, trade-offs, simulations, layout closure, verification and measured correlation relevant to the live circuit.

Does AMD sponsor every Santa Clara engineer?

No. Sponsorship is requisition-specific; the current RTL example explicitly says it is unavailable.

Official and primary sources

• AMD Careers — official or primary evidence for scope, status, safeguards or application.
• Current AMD Santa Clara RTL Logic Design Example — official or primary evidence for scope, status, safeguards or application.
• Current AMD Hardware Validation Example — official or primary evidence for scope, status, safeguards or application.
• Current AMD Mixed-Signal Memory PHY Pattern — official or primary evidence for scope, status, safeguards or application.

Research checked 2026-08-09. Organization pages establish scope; only an active official requisition establishes a current vacancy. Guidance sources support practices within their limits and do not guarantee an individual outcome.