Mirage
Software Engineer, Backend
About this role
Mirage is seeking a Backend Engineer to design and operate scalable systems powering an AI-native video platform. You'll own end-to-end backend infrastructure, integrate generative AI models into production, and collaborate across product and ML teams to ship high-impact features.
What you'll do
- Design and own backend systems end-to-end including services, APIs, and data pipelines
- Solve complex distributed systems challenges around scaling, concurrency, and performance
- Deploy, serve, and scale large generative AI models in production environments
- Instrument and iterate on systems in production to improve quality and reliability
- Design core platform infrastructure with third-party integrations and security considerations
What they're looking for
- Backend systems design and architecture
- Distributed systems and scalability
- API design and development
- Data pipelines and infrastructure
- Production ML model deployment and serving
- Performance optimization and debugging
- Rapid iteration and shipping in fast-paced environments
- LLM and generative AI experience (preferred)
Benefits
- Comprehensive medical, dental, and vision coverage
- 401K with employer match
- Commuter benefits
- Catered lunch multiple days per week
- Dinner stipend for late-night work
- Team offsites and monthly events
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.
Mirage
Mirage builds an AI-native video platform that leverages generative media and large language models to enable sophisticated video production, editing, and creative workflows. The company is hiring backend engineers, full-stack software engineers, ML engineers, and iOS developers to advance their AI-driven platform and enhance user experiences in web-based and mobile media creation.
View all jobs at MirageLikely interview questions
- Walk us through a backend system you designed end-to-end in production—what were the key technical decisions and tradeoffs?
- How have you approached scaling a system to handle significant growth or unexpected load?