Blue is building the trust layer the AI economy has been waiting for — a protocol for structured, verifiable, multi-party agreements that execute deterministically, leave an audit trail, and work across any system. Think smart contracts, minus the blockchain overhead.
Our products are already being built and tested with real integrations:
- PayNotes — Programmable payments with conditional capture, milestone releases, refunds, vouchers, and partner settlement.
- MyOS — SaaS orchestration layer for merchants and agents. Cross-platform trust, without writing a line of Blue Language yourself.
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.
- Deep AWS expertise across compute, messaging, storage, networking, and observability — not just familiarity, but operational instinct built from running things in production
- Strong IaC discipline — CDK, SAM, or CloudFormation; you version everything, you don’t click in consoles
- Understanding of distributed systems fundamentals: ordering guarantees, idempotency, at-least-once delivery, outbox patterns, partial failure recovery
- Experience operating event-driven architectures under load — you know what failure looks like before it becomes an incident
- Enough application-layer literacy to read TypeScript/Node.js code and understand what a service is doing, not just that it’s running
- Strong opinions about observability — structured logging, distributed tracing, dashboards built for on-call humans at 3am