Jobs · four roles · applications opening soon
One system. Build it. Shape it. Finish it. Carry it.
Applications opening soon
Platform Engineer
Build and operate SDLC.works itself — the transportation system. The metaphysician of the team: works on the roads, junctions and traffic rules every team drives on, not on any single product feature.
Responsibilities
- Design the platform's building blocks — the pieces an application is made of, the machines they run on, the wiring between them — all captured in one written-down blueprint.
- Keep one live source of truth: the current state of every repository, environment, deployment and pending change.
- Make whole environments behave like Git branches: a complete copy of code, infrastructure and settings, created, cloned or torn down in one click.
- Build the Pulumi-based framework that provisions infrastructure, wires it together (IAM, networking, env vars) and deploys code — and on top of it, rollback, release coordination and push-button multi-region (single-region → HA).
- Keep the rules of the road intact: teams freely choose cloud, stack and release timing, but nobody rewires the underlying system on a whim.
Requirements
- Reasons from first principles about how software should move from a developer's laptop to production — not by copying industry patterns.
- Deep IaC and cloud architecture experience.
- Comfortable being the one who decides what the road allows.
Platform Engineer
Applications opening soon
This role's form is not live yet.
Applications opening soon
Experience Engineer
Own every surface a human touches — dashboard, CLI, onboarding, docs, error messages. Two ideas govern the work: people don't behave rationally, so the interface must guide and forgive them; and attention is scarce, so every click, concept and second between intent and outcome must earn its place.
Responsibilities
- Build the screens that answer "what is running where, and who changed what" at a glance — in language a first-day user understands.
- Make the core promise feel like one obvious action: create an environment, replicate a region, roll back.
- Instrument the interfaces and watch where users stall; treat confusion as a defect in the system, never as user error.
- Own day one: sign-up to a running, deployed app in minutes, nothing configured by hand.
Requirements
- Strong frontend engineering with genuine product-design sensibility — ships polished UI, not mockups.
- Works from evidence: user observation and funnel data, not taste alone.
- Writes clearly — microcopy and error text are part of the interface.
Experience Engineer
Applications opening soon
This role's form is not live yet.
Applications opening soon
Product Engineer
Combine platform capability and experience into product. The Platform Engineer asks "does the system work?"; the Experience Engineer asks "can a human use it?"; the Product Engineer asks "will someone pay for this, and is it actually finished?"
Responsibilities
- Own features end to end: from requirement to shipped, billable capability — backend, integration, and the wiring into the experience layer.
- Define "complete" as acceptance criteria and refuse to call a feature done until every criterion holds — for example Git Metrics, a dashboard of developer activity, built as its own product on the platform itself.
- Connect capability to revenue: pricing surfaces, plan gating, usage limits, billing.
- Prioritise by customer impact — starter founders and enterprise CXOs, not engineering interest — then measure adoption and iterate until the feature earns its keep or is cut.
Requirements
- Full-stack engineer who owns a feature's business outcome, not only its code — and is allergic to 80%-done.
- Uses AI-assisted development to ship production-grade work in days, not quarters.
Product Engineer
Applications opening soon
This role's form is not live yet.
Applications opening soon
Forward Deployed Engineer (FDE)
Embed inside customer companies and move their entire development process onto the platform — the field arm of the enterprise transformation offering.
Responsibilities
- Map the customer's ad hoc, tribal-knowledge setup into a clean blueprint: what the system is made of, how the parts talk to each other, and the settings that hold it together.
- Execute the migration with minimal downtime and hand over a system that is fully written down and centrally managed — one the customer runs without you.
- Feed real-world friction back to the Platform and Product Engineers as concrete platform requirements.
Requirements
- Strong generalist engineer who can read unfamiliar infrastructure quickly and work credibly with CXOs and their teams.
- Treats dysfunction as a systems problem: transforms the system, never lectures the developers.
Forward Deployed Engineer (FDE)
Applications opening soon
This role's form is not live yet.
How applying works
Three steps, all inside the role's Google Form.
Apply opens that role's form in a new tab. There is no account to create with SDLC.works.
- 1
Sign in with Google.
The form asks for a Google account before it opens.
- 2
Answer the questions.
Each role's questions are in its own form. Read them there.
- 3
Submit a video link.
Record a video answering the questions and paste its link into the form.
A role marked Opening soon has no form yet.