Loading your next page…
Loading your next page…
Set the platform standard across our engagements: golden paths, IaC modules, observability defaults, and the developer experience our delivery teams depend on.
Open role
Platform & DevOps
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
A practical conversation about the role, time-zone overlap, compensation, and the kind of client problems you want to own.
02 · Work sample discussion
Walk us through a shipped system, design case study, incident, repository, or architecture decision. We focus on trade-offs, not trivia.
03 · Peer review
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
We share the engagement shape, expectations, benefits, compensation, and what success looks like in your first quarter.
MayaLogic roles are senior because they include judgment, communication, and ownership of how software behaves after it leaves your laptop.
Platform work is judged by secure defaults, usable golden paths, incident learning, and developer experience adoption.
Every meaningful change is reviewed for behavior, security, maintainability, performance, and whether the client can own it.
We write runbooks, instrument critical paths, and treat supportability as part of the role rather than someone else’s clean-up.
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?
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.