Staff Platform Engineer
Set the platform standard across our engagements: golden paths, IaC modules, observability defaults, and the developer experience our delivery teams depend on.
- Location
- Remote (EMEA / APAC overlap)
- Seniority
- Staff · 9+ years
- Type
- full-time
- Posted
- 2 April 2025
What you’ll do.
- Set the technical direction of MayaLogic’s internal platform and IaC catalogue.
- Design and operate golden paths for cloud, CI/CD, and observability.
- Lead cross-engagement architecture reviews on platform-shaped problems.
- Coach senior engineers and grow the platform practice.
Requirements.
- 9+ years of production engineering experience, with the last 4 on platform or SRE.
- Deep AWS or Azure fluency; Kubernetes operated in anger.
- Strong Terraform or Pulumi authoring; opinionated on module design.
- Familiarity with OpenTelemetry, SLO design, and modern observability stacks.
- Track record of paving roads engineers actually use.
Nice to have
- Backstage or comparable internal-developer-platform experience.
- Policy-as-code (OPA, Sentinel) in production.
What to expect.
The process is designed to show how you think and collaborate in work that resembles the role — no puzzle interviews, no unpaid production assignments.
01 · Intro
Role fit and working style
A practical conversation about the role, time-zone overlap, compensation, and the kind of client problems you want to own.
02 · Work sample discussion
Bring evidence of judgement
Walk us through a shipped system, design case study, incident, repository, or architecture decision. We focus on trade-offs, not trivia.
03 · Peer review
Collaborate with senior teammates
You meet the people who would review your work. Expect questions about failure modes, communication, quality bars, and maintainability.
04 · Offer and first ninety days
Clarity before commitment
We share the engagement shape, expectations, benefits, compensation, and what success looks like in your first quarter.
The standards you will help uphold.
MayaLogic roles are senior because they include judgement, communication, and ownership of how software behaves after it leaves your laptop.
Role-specific quality bar
Platform work is judged by secure defaults, usable golden paths, incident learning, and developer experience adoption.
Review culture
Every meaningful change is reviewed for behavior, security, maintainability, performance, and whether the client can own it.
Production responsibility
We write runbooks, instrument critical paths, and treat supportability as part of the role rather than someone else’s clean-up.
Send us a note via the contact form.
Mention the role title and link to whatever best represents how you work — a repository, a write-up, a system you are proud of. Until our applicant tracking system lands in Phase 3, the contact form is the fastest path to a real conversation.
Not quite the right role?
We still want to hear from you.
Send a note with the link to whatever best represents how you work. We keep an interest list for senior builders we would love to work with.