Job Opportunities API

ABOUT LABRYNTH Labrynth is the execution layer that turns regulatory complexity into competitive advantage with faster and defensible approvals. We build AI-powered platforms that navigate complex regulations, generate audit-level documentation, and provide certainty, not shortcuts. Our technology serves clients across heavily regulated industries including energy, compliance, and government regulations. We operate as a forward-deployed engineering organization: small, high-velocity teams embedded directly with clients to rapidly discover needs and ship production-quality solutions. ABOUT THE ROLE This role keeps our delivered work running. You will sit across active client projects and the platforms we already have in production, splitting your time between building the features that support delivery teams, keeping systems healthy, and being the person who responds when something breaks. Because our platforms sit inside regulated workflows, reliability is not a nice-to-have. When an audit deadline is on the line, the system has to work. Incident duty runs as a shared rotation during business hours, so you are never carrying it alone and you are not paged in the middle of the night. Outside those hours we run an escalation path rather than a standing roster, and genuine after-hours work is recognised and compensated. It suits an engineer who takes satisfaction in reliability and in finishing things properly: shipping the fix that unblocks a delivery team, tracing the bug nobody else wants to touch, and turning a repeat incident into a permanent solution. You will see a wide surface area of systems and clients, which is one of the fastest ways to become genuinely good at this work. WHAT YOU'LL DO - Support project delivery. Build and ship features, integrations and fixes that support active client projects, working end to end from data model to interface. - Maintain the platforms. Keep our production platforms healthy: dependency and version upgrades, performance and cost tuning, security patching, refactoring, and paying down technical debt before it becomes an outage. - Handle incidents. Take first-line ownership of incidents during your rotation. Triage, communicate status clearly to the team and the client, restore service, then write the blameless postmortem and drive the follow-up actions to completion. - Improve observability. Improve logging, metrics, traces and alerting so problems surface before clients notice them, and so the next person on call has what they need. - Automate the repetitive. Turn recurring manual work into scripts, jobs or tooling. Every repeated fix should end in automation or a runbook. - Document as you go. Keep runbooks, architecture notes and handover documentation current and useful, especially where audit trails and evidence matter. - Support the team. Review pull requests, contribute to engineering standards, and give delivery teams a dependable second pair of eyes. WHAT WE'RE LOOKING FOR We care about how you work far more than which frameworks you have used. If your experience is in a different stack to ours, we will help you cross over. - Two to five years building and running web applications in production, comfortable across both server-side and client-side work. - Professional experience with Python and TypeScript, or deep strength in one and genuine working exposure to the other. - Solid relational database skills: schema design, query performance, safe migrations. - Practical experience with a major cloud platform, containers, CI/CD pipelines and infrastructure managed as code. - Real debugging ability in live systems: reading logs and traces, forming a hypothesis, isolating the cause, and verifying the fix. - A testing habit that matches the risk of the change, and a bias toward small, reversible releases. - Clear written communication, especially under pressure. During an incident, a calm and accurate update is worth as much as the fix. - So