Outtake
Software Engineer, Infrastructure
About this role
Outtake seeks a staff-level infrastructure engineer to design and build foundational systems handling billions of pieces of content. You'll own the technical direction for databases, search, data processing, and cloud architecture while mentoring a growing infrastructure team.
What you'll do
- Set technical direction for databases, search and retrieval, data processing, asynchronous execution, and cloud architecture
- Redesign search and retrieval systems to support fast investigation across billions of content pieces
- Evolve relational database architecture through sharding, partitioning, indexing, and caching strategies
- Design and build scalable asynchronous systems for scheduling, queues, workflows, and failure recovery
- Develop shared infrastructure services, APIs, and primitives for product engineers
- Operate systems and use production evidence to improve architecture and automation
What they're looking for
- Distributed systems design and implementation
- Relational database architecture and optimization
- High-throughput asynchronous systems and messaging
- Large-scale search and retrieval systems
- Data ingestion and batch/stream processing
- Cloud infrastructure (compute, storage, networking)
- System migration and deployment strategy
- Technical leadership and architectural decision-making
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.
Outtake
Outtake builds an AI-driven platform focused on combating digital impersonation, fraud, and security threats through innovative cloud infrastructure solutions. The company is hiring Software Engineers across full-stack, platform, and security specializations, along with Sales Engineers who bridge technical expertise and customer relationships.
View all jobs at OuttakeLikely interview questions
- Describe a time you redesigned a critical system to handle a significant increase in data volume or traffic—what was your approach and what tradeoffs did you evaluate?
- How would you approach designing a search system that needs to handle billions of pieces of content with low latency?