Member of Technical Staff Intern

Breadth

This is a broad technical internship, not a front-end-only internship and not a passive shadowing program. You will be assigned one primary technical lane and one bounded project:

• agent and AI systems
• product and backend software
• inference infrastructure
• profiling and kernel tooling
• FPGA or driver test infrastructure
• hardware or materials research tooling
• manufacturing-data analysis
• interactive technical education

Technical Territory

Projects may include:

• agent tool loops, context and evaluation
• web and backend systems
• APIs and data
• observability
• model serving
• routing and caching
• workload replay
• profiling
• compilers and GPU kernels
• FPGA and driver test infrastructure
• simulation and verification
• architecture models
• experiment automation
• DOE or yield-data analysis
• metrology and reliability data
• documentation
• interactive technical education

Representative Outputs

• A written project brief naming the user, problem, technical lane, interfaces, constraints, acceptance test, evidence state, reviewer, and delivery date.
• A working artifact such as code, tests, a benchmark, simulator, data pipeline, experiment tool, verification harness, visualization, or interactive lesson.
• A review packet with source links, commands or methods, results, failures, limitations, and the evidence that supports each claim.
• A final demonstration and handoff that another engineer, researcher, or educator can reproduce and extend.

What Success Looks Like

• You ship one useful artifact that passes its defined acceptance test.
• You can explain the full path from user problem to code, system behavior, evidence, and limitation.
• Your tests and documentation let another person reproduce and extend the work.
• You leave with deeper technical judgment, not only familiarity with one tool or model.

What You Bring

• Current bachelor’s, master’s, or PhD student, or recent graduate, with strong fundamentals and evidence of building, experimenting, or researching.
• Ability to learn unfamiliar tools, ask precise questions, and finish a bounded project.
• Code, research, experiments, technical writing, or projects that demonstrate curiosity and ownership.
• Comfort reading existing code and documentation before proposing a rewrite.
• Basic testing and debugging discipline appropriate to your area.
• Clear written communication and willingness to receive direct technical review.

Helpful Experience

• Agent systems, evaluation, or developer tools
• Full-stack, backend, data, or infrastructure engineering
• ML serving, routing, caching, profiling, or inference infrastructure
• Compilers, GPU kernels, FPGA, drivers, architecture, or verification
• Materials science, semiconductor processing, packaging, metrology, reliability, DOE, or manufacturing data
• Research communication or technical education