Baseten
Software Engineer - Training Product
About this role
Baseten seeks a software engineer to build and scale their training product, which enables AI companies to fine-tune and deploy models efficiently. You'll own features across the full stack—from APIs and UI to infrastructure—while partnering with research engineers and customers to solve real training workflow challenges.
What you'll do
- Design and ship features like multi-node training and serverless reinforcement learning from conception through production
- Architect solutions across API, backend, database, infrastructure, and frontend layers
- Fine-tune and deploy models to understand user workflows and pain points
- Partner with research engineers and model developers to inform product requirements
- Improve system reliability and development velocity through long-term technical improvements
- Respond to customer issues and bugs with urgency
What they're looking for
- Full-stack software development (5+ years)
- Web stack, databases, and distributed systems
- Infrastructure and developer tooling design
- Kubernetes and orchestration systems
- API design and abstractions
- ML/AI infrastructure knowledge
- Frontend development (plus)
- Strong communication and product sense
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.
Baseten
Baseten builds an AI inference platform that enables companies to deploy and manage machine learning models in production at scale. The company is hiring software engineers, infrastructure specialists, and product engineers to develop observability systems, frontend experiences, reliability infrastructure, developer tools, and enterprise deployment solutions.
- Website
- baseten.com
Likely interview questions
- Walk us through your experience building developer-facing tools or infrastructure products. How did you approach understanding what your users actually needed?
- Tell us about a time you worked across multiple layers of a system (API, backend, infrastructure). How did you approach designing clean abstractions for complex resources?