
Silicon Engineer
Anthropic · San Francisco, CA · Hybrid
Job Description
Anthropic is recruiting a Silicon Engineer in San Francisco, CA. This hybrid role supports a custom silicon team and works across chip-level development.
What you'll do
- Contribute across strategy, specifications, execution, and technical standards.
- Create specifications and interface definitions as architecture develops.
- Make decisions on technology, IP, partner selection, and design authority.
- Develop AI-assisted methods for code-like work within the domain.
- Contribute domain input to architecture and micro-architecture tradeoffs.
- Work with inference, performance, kernels, infrastructure, and hardware systems teams.
- Support first-silicon bring-up and debug activities.
What you'll bring
- Hands-on expertise in at least one silicon domain.
- Direct ownership of silicon that taped out and shipped.
- Ability to assess chip-level tradeoffs beyond a specialty.
- Experience with ASIC houses, IP vendors, foundries, or test partners.
- Practical use of AI coding tools.
- Clear communication and experience aligning teams.
- A Bachelor’s degree or equivalent education, training, and/or experience.
What you'll be offered
- Annual Salary: $320,000 - $485,000 USD
- Visa sponsorship support, where possible.
About Anthropic
Anthropic aims to create reliable, interpretable, and steerable AI systems. Its team includes researchers, engineers, policy experts, and business leaders.
Key skills: front-end design, pre-silicon verification, physical design, Design for test, Analog and mixed-signal, Technology and foundry, CAD and design infrastructure, Packaging, signal integrity, and power integrity, machine learning accelerators, hardware-software co-design
Apply for this role prepared
Tailor your resume to this exact job, write the cover letter, check your ATS score and practise the interview — in one place. Free to start.
🧠 AI Insights for this role
Resume → Job Fit Analysis
Get a fit score, keyword gaps, and specific resume edits tailored to this role.
Check my fitLikely Interview Questions
Show prep pack ↓
LIKELY QUESTIONS - Which silicon domain do you own most deeply? - Describe a chip you took through tape-out and shipment. - How did you assess chip-level tradeoffs beyond your specialty? - How have you worked with ASIC houses or IP vendors? - What was your role during first-silicon bring-up? - How do you define clear specifications and interfaces? - How have you used AI coding tools in engineering work? - How would you partner with inference and kernel teams? BEHAVIOURAL QUESTIONS - Tell me about a time you aligned teams with competing hardware priorities. Model approach: Situation: Teams disagreed on a chip-level decision. Task: Create alignment around requirements and tradeoffs. Action: Defined shared metrics, documented options, and drove decisions. Result: Reached agreement and protected [schedule, performance, or risk]. - Describe a time a silicon issue emerged late in development. Model approach: Situation: A late-stage issue threatened tape-out or bring-up. Task: Assess impact and lead resolution. Action: Isolated root causes, coordinated owners, and tracked mitigations. Result: Resolved the issue or made a documented risk decision. - Tell me about a difficult interface specification you created. Model approach: Situation: Architecture was evolving across several teams. Task: Define an interface that enabled parallel work. Action: Clarified ownership, timing, error handling, and verification expectations. Result: Reduced ambiguity and enabled implementation progress. - Describe a time you influenced a decision outside your core specialty. Model approach: Situation: A broader chip tradeoff affected your domain. Task: Provide a balanced technical recommendation. Action: Gathered input, compared options, and explained system-level consequences. Result: Helped the team select an approach with clear rationale. SMART QUESTIONS TO ASK - What silicon domains need the most support initially? - How mature is the current architecture and specification process? - How are design authority decisions made across teams? - What would successful first-silicon bring-up look like here? - How do hardware teams work with inference and kernel teams? RED FLAGS TO WATCH FOR - Unclear ownership for architecture, specifications, and design decisions. - No defined plan for tape-out, bring-up, or external partners. - Conflicting expectations across hardware, inference, and infrastructure teams.
Want full STAR-format answers tailored to your background? Use the Interview Simulator.
Adjacent Career Paths
Roles you'd also qualify for based on this posting's requirements:
- ASIC Design Engineer — The role requires hands-on silicon design and chip tradeoffs.
- Silicon Verification Engineer — Pre-silicon verification and first-silicon debug are central needs.
- Hardware Systems Engineer — The work spans hardware systems, inference, and performance teams.
- Machine Learning Accelerator Engineer — The team develops custom silicon for AI-related workloads.