Systems AI Engineer

Why this role exists 

Most systems work at a low scale. 

Very few survive real production load, complex workflows, and enterprise edge cases. 

We are building a platform that must: 

1. Scale from 500K → 20M+ interactions/month 
2. Handle complex insurance workflows reliably 
3. Become easier to deploy as it grows, not harder 
4.  
5. This role exists to build the backend foundation that makes this possible. 

What you’ll do 

You will not just write services. 

You will design and own core platform systems. 

1. Scale the platform without breaking architecture 

1. Scale from 50K → 4M+ interactions/month 
2. Ensure: 
3. High availability 
4. Low latency 
5. Fault tolerance 
6. Avoid large rewrites — build systems that evolve cleanly 

2. Build the workflow automation (WA) engine 

1. Design a flexible system with: 
2. States 
3. Stages 
4. Cohorts 
5. Dynamic workflows 
6. Ensure workflows: 
7. Handle edge cases reliably 
8. Can be configured easily 
9. Move from: 
10. Hardcoded flows → configurable execution engine 

3. Build the insurance-specific data layer 

1. Design data models for: 
2. Policy states 
3. Claim workflows 
4. Consent tracking 
5. Ensure the system works across: 
6. Multiple insurers 
7. Multiple use cases 
8. Build a platform-first data layer, not use-case-specific hacks 

4. Make deployment and setup simple 

1. Ensure workflows and data models are: 
2. Easy to configure 
3. Easy to launch 
4. Reduce friction for: 
5. Product teams 
6. Deployment teams 

5. Create a compounding data advantage 

1. Build a data layer that: 
2. Improves with every deployment 
3. Captures structured signals 
4. Ensure data becomes a long-term edge, not just storage 

6. Own production reliability 

1. Participate in on-call rotation across 3 engineers 
2. Ensure: 
3. Incidents are handled quickly 
4. Root causes are fixed permanently 
5. Build systems where reliability is shared, not individual 

What success looks like 

1. Platform scales to 2M+ interactions/month smoothly 
2. Workflow engine supports complex, dynamic use cases 
3. Data layer enables fast deployment across accounts 
4. Edge cases are handled without constant firefighting 
5. System becomes easier to use as it grows 
6. Production issues are rare and predictable 

Who you are 

1. You have built: 
2. Scalable systems 
3. Distributed services 
4. You think in: 
5. Systems 
6. Data models 
7. Trade-offs 
8. You are comfortable owning: 
9. Architecture 
10. Production systems 

What will make you stand out 

1. Experience building: 
2. Workflow engines 
3. State machines 
4. Data-heavy platforms 
5. Strong understanding of: 
6. System design 
7. Distributed systems 
8. Failure handling 
9. Experience working in: 
10. High-scale production environments 

Why join 

1. You will build the core backend of an AI platform 
2. Your work directly impacts: 
3. Scale 
4. Reliability 
5. Product capability 
6. You will design systems that move from: 
7. Use-case specific → platform-level infrastructure 

What this role is not 

1. Not just API development 
2. Not limited to feature-level work 
3. Not disconnected from production realities 

What this role is 

1. A system architect 
2. A builder of scalable platforms 
3. A driver of long-term technical advantage 

One question to self-evaluate 

Can you design backend systems that scale, handle edge cases, and become easier to use as they grow? 

Skills

Databases, Failover, Infrastructure management, Python, Artificial Intelligence (AI), Generative AI (GenAI)