Etched
Infrastructure Intern
About this role
Etched is seeking infrastructure interns to help develop tooling and systems for AI inference hardware. You'll work on hybrid-cloud HPC clusters, CI/CD infrastructure, Infrastructure-as-Code, and observability platforms alongside world-class engineers in San Jose.
What you'll do
- Develop and optimize next-generation infrastructure tooling for ASIC and software engineers
- Work on hybrid-cloud HPC cluster development and high-performance compute systems
- Build massively parallel CI/CD execution pipelines
- Contribute to Infrastructure-as-Code implementations
- Support scale-out observability platform development with LLM integration
- Debug and optimize hardware/software integration issues
What they're looking for
- C/C++ or Rust programming
- Python (for systems software)
- Data structures and algorithms
- Low-level software engineering
- Hardware/software co-design
- Linux internals or kernel development (preferred)
- CI/CD pipeline experience (preferred)
- Server virtualization knowledge (preferred)
Benefits
- 12-week paid internship program
- Generous housing support for relocating interns
- Daily lunch and dinner provided at office
- Direct mentorship from industry leaders
- Work on frontier AI inference infrastructure
- Fully in-person team in San Jose with collaborative engineering culture
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Etched
Etched builds AI inference hardware, designing and manufacturing complex mechanical and electrical components for data center systems. The company is hiring mechanical engineers, PCB designers, hardware verification engineers, and software engineers to develop manufacturing processes, circuit boards, verification infrastructure, and internal tools across its hardware and operations.
- Website
- etched.com
Likely interview questions
- Walk us through your experience with C/C++ or Rust. Can you describe a project where you used low-level systems programming and what challenges you faced?
- Tell us about your understanding of hardware/software co-design. How have you seen hardware constraints influence software decisions in a project?