MyOS processes documents, payments, and agent interactions through a distributed, event-driven pipeline where correctness isn’t optional. State must be deterministic, ordering must be exact, and failure must be recoverable without data loss or partial writes. A bad deployment here doesn’t just cause downtime — it can silently break processing guarantees across active sessions. Understanding why that matters, and building infrastructure that prevents it, is the job.
The Role
You will own features end-to-end — from the React component a merchant clicks to the Lambda function that settles their transaction to the AWS infrastructure that keeps it all standing. No handoffs between "front" and "back". No waiting for someone else to unblock you.
This is a high-trust, high-autonomy role. You'll work directly with the founding team, your decisions will ship to production fast, and yes — you'll be on the hook when something breaks.
We’re looking for someone who will take full ownership of the DevOps side of the project and operate independently — without needing constant support or hand-holding. This role includes on-call duties, so we’re looking for someone who is comfortable with that model of collaboration and sees it as a natural part of engineering work.
We’re not looking for someone to manage servers. We’re looking for an engineer who looks at a distributed, event-driven system and immediately sees the failure modes, the ordering edge cases, and the places where a misconfigured queue will silently corrupt state. Someone who automates everything, documents why, and gets angry when something requires a manual step.