Sierra
Software Engineer Intern, Agent (Winter 2027)
About this role
Sierra is seeking a Software Engineer Intern to contribute to production AI agents for major enterprise customers. You'll work on designing, developing, and shipping features while gaining hands-on experience with real-world AI systems at scale.
What you'll do
- Design and develop production AI agents for Sierra's enterprise customers
- Ship features and contribute to agent system improvements
- Work with real-world use cases and production deployments
- Collaborate with product and engineering teams on AI agent tooling
- Participate in code reviews and engineering best practices
- Learn from production systems and real customer feedback
What they're looking for
- Python or Go programming
- AI/LLM systems and prompt engineering
- React and TypeScript (preferred)
- Evaluation frameworks and agent tooling
- RAG pipelines and retrieval systems
- Problem-solving in ambiguous environments
- Technical communication skills
- Product-oriented engineering mindset
Benefits
- Monthly stipend for health insurance
- Daily lunch provided
- Hands-on experience with cutting-edge AI technology
- Mentorship from experienced AI engineers
- Exposure to Fortune 500 customer use cases
- In-person collaboration in San Francisco office
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.
Sierra
Sierra builds production-grade AI agents for enterprise clients in insurance, financial services, and other industries, enabling companies to automate complex business processes and enhance customer experiences. The company is hiring Software Engineers to design and deploy mission-critical AI systems, develop platform infrastructure, and work directly with enterprise customers on agent development and optimization.
View all jobs at SierraLikely interview questions
- Describe your experience building or deploying AI/LLM systems. What were the biggest challenges?
- Tell us about a time you shipped a feature in a fast-changing, ambiguous environment. How did you navigate uncertainty?