Software Engineer III – AI

Responsibilities

• Design, build, and operate the shared AI/LLM platform
• Write the central backend services that power our AI projects
• Handle APIs, data access layers, integration points between LLMs and internal systems
• Set technical standards for embedded engineers shipping AI features
• Produce reliable AI systems with low latency and manageable costs
• Develop governance patterns for LLM usage
• Provide technical recommendations on tools and frameworks

Requirements

Must-haves

• Shipped and operated LLM-based features in production
• Strong hands‑on backend engineering — you'll write production services, not just design them
• Fluent in TypeScript (both, not either)
• Familiarity with functional programming — ideally in Scala
• Strong knowledge of software architecture design patterns
• Experience designing or operating event‑driven architectures (Kafka, event sourcing, async messaging patterns)
• Hands‑on with orchestration frameworks, RAG, evals, and guardrails
• Thinks clearly about identity, access, and data governance — especially when LLMs touch sensitive systems
• Pragmatic on cost/latency trade‑offs and model selection
• Comfortable being the technical voice in strategic conversations and pushing back when needed
• Fluent in the AI tooling landscape — can compare options quickly and credibly

Nice‑to‑haves

• Experience in regulated industries (financial services, healthcare, legal)
• Familiarity with Python
• Familiarity with European data/privacy frameworks (GDPR, FCA expectations)
• Working knowledge of Scala specifically (you'll integrate with our Scala services)
• Mobile or full‑stack range (the broader product is web + mobile)
• Previous role in a small, high‑trust team where the engineer shaped technical direction directly

Not a fit if

• Background is primarily ML research, model training, or data science
• Looking for an architect/lead role where someone else writes the code
• Wants a fully greenfield environment with no regulatory or legacy constraints
• Prefers strict role boundaries — this is a small team where engineering and strategy overlap by design