01
Make complexity legible
Turn AWS resources, event paths, permissions, logs, and architecture trade-offs into interfaces and explanations a team can use.
Build tools that make complex AWS systems easier to reason about.
Work at Zerverless sits between developer experience, distributed systems, cloud security, product design, and technical communication.
There are no open roles today. This page explains how future roles will be designed and communicated.
Work on problems where judgment matters.
The product is not another layer of infrastructure. The work is helping engineers see, decide, and act with more confidence.
02
Protect customer control
Design around least privilege, separate trust decisions, inspectable outputs, and workloads that remain in the customer account.
03
Work from the user backward
Start with the engineering decision or operating problem, then choose the smallest product surface that makes it easier.
04
Write as part of engineering
Use design notes, decision records, product copy, runbooks, and examples to make technical intent reviewable.
How the work should feel.
Context before ceremony
Share the decision, constraints, owner, and expected outcome before adding meetings or process.
Small scopes, complete outcomes
Prefer a narrow problem carried through design, implementation, validation, and explanation over a large ambiguous backlog.
Direct, respectful review
Challenge assumptions and implementations clearly while keeping feedback about the work, not the person.
Production reality
Treat permissions, failure modes, cost, support, and documentation as part of the feature rather than work left for later.
Future role descriptions will be explicit.
Outcome and ownership
The problem, decision authority, expected collaboration, and definition of success will be written down.
Location and working hours
Every posting will state location constraints, overlap expectations, employment basis, and travel requirements.
Compensation and process
Postings will explain the compensation structure and interview stages before asking candidates to invest significant time.
Skills, not proxies
Requirements will focus on the work and evidence of ability rather than inflated credential lists or hidden seniority expectations.
No open positions right now.
When a role opens, it will appear here with the scope, location, working model, compensation approach, interview stages, and a direct application path. Zerverless does not accept paid placement or recruiting submissions through this page.
Interested in work that may open later?
Send a short note with the kind of problems you solve, the work you want to do next, and one artifact that shows how you think. This is not an application to a current role, and no interview process begins until a relevant position exists.