We do enterprise document ingestion — capture a document once into a
canonical field registry, then project it to any schema, no re-extraction.
Stack: AWS, Docker, Railway.
We've never had a dedicated reliability owner and it's starting to show.
You'd be the first: SLOs and an error-budget policy that actually gets
honoured, observability worth paging on, post-mortems that change the
architecture, deploys nobody dreads. Target is 99.9%. Compliance is real
here (GDPR, ISO 27001/42001, HIPAA), so reliability and audit work overlap.
Haven't used Railway? Fine, we'll onboard you. We ship with Claude Code
day to day — if that's interesting rather than irritating, good.
Process: founder chat (bring a Sev1 you've owned), a paid day building
with us on something real, team fit, references.
I’m interested in the founding Staff Site Reliability Engineer role.
The opportunity to be the first dedicated reliability owner and build the foundations around SLOs, error budgets, observability, incident response, and safer deployments is especially appealing to me. I also like that reliability is closely connected with your compliance requirements and architecture.
The AWS/Docker stack is familiar to me, and I’m happy to learn Railway. I’d also be interested in hearing more about how you’re currently handling incidents, deployments, and observability, and where you see the biggest reliability challenges today.
I’d be happy to discuss my experience, including a Sev1 incident I’ve owned, and learn more about the team and the role.
We do enterprise document ingestion — capture a document once into a canonical field registry, then project it to any schema, no re-extraction. Stack: AWS, Docker, Railway.
We've never had a dedicated reliability owner and it's starting to show. You'd be the first: SLOs and an error-budget policy that actually gets honoured, observability worth paging on, post-mortems that change the architecture, deploys nobody dreads. Target is 99.9%. Compliance is real here (GDPR, ISO 27001/42001, HIPAA), so reliability and audit work overlap.
Haven't used Railway? Fine, we'll onboard you. We ship with Claude Code day to day — if that's interesting rather than irritating, good.
Process: founder chat (bring a Sev1 you've owned), a paid day building with us on something real, team fit, references.