Staff Platform Engineer
Indexed description
Why this role exists
The platform stack needs an owner. One person who designs, builds, maintains, and takes responsibility for how it runs in production across multi-cloud environments. Not a committee. Not a manager. One engineer with deep enough expertise and ownership instinct to make hard calls fast and live with the consequences.
What You Will Own
- The entire shared backend layer: GraphQL gateways, graph databases, API infrastructure, internal SDKs
- Kubernetes clusters across AWS and GCP including networking, scaling, security, and orchestration
- Observability, alerting, and incident response systems that work at org scale
- Compliance posture across HIPAA, LGPD, SOC2, ISO 27001, not delegated but owned
- Pulumi modules, automation tooling, and the ongoing refactor of legacy systems
- AI-assisted workflows across incident response, code review, and capacity planning
- Migration and improvement of inherited systems, diagnosed accurately, fixed deliberately
- Write production code and infrastructure-as-code, not review it
- Debug slow queries, analyze traces, resolve production incidents personally
- Make architectural decisions on the shared platform with full accountability
- Evaluate and adopt AI tooling into your daily engineering workflow
- Operate in high ambiguity with limited process and high expectations for output
- Based in Brazil
- Senior hands-on platform or infrastructure engineer, not a manager who used to code
- Deep Kubernetes in production, multi-cloud: AWS and GCP both required
- Direct experience in regulated environments: HIPAA, SOC2, GDPR, or LGPD
- Backend engineering depth: you can debug a slow query, read a flame graph, trace a distributed system
- A track record of building 0-to-1 platform capabilities, not just maintaining what exists
- You use AI tools daily and can articulate exactly how they changed the way you work
- You can tell a specific, honest story about a production issue you personally caused and fixed
- Graph databases in production: Neo4j or Amazon Neptune
- Document stores at scale: Firestore or MongoDB
- Healthcare data infrastructure: EHR integrations, FHIR APIs, clinical data pipelines
- You have technically led other engineers without needing a management title to do it
- Your last two years are primarily management or director-level with no significant hands-on coding
- You describe your work as "managed" or "oversaw" rather than "built," "shipped," or "architected"
- No regulated environment experience on your CV
- Not based in Brazil
- CV review
- Intro call: role fit, background, expectations
- Technical screening with the founding team
- Deep-dive interview: production war stories, architectural decisions, live problem-solving
- Offer
Create a free Caio profile to unlock more results and save your role and location preferences.
Unlock free search