Application / DevOps Engineer

Tell us how you build.

Short, specific answers beat long ones. Your draft is kept in this browser until you submit.

01 About you

Full name

Location and timezone

Hours per week you can give

GitHub or portfolio

LinkedIn optional

This is a paid role, but the budget is still being negotiated, so we cannot give you a number yet. Does that work for you?

Yes, I can start before the budget is set I need the number before I start Contact me once the budget is set

02 Your experience

What is your stack?

CI/CD systems, AWS, Terraform or OpenTofu, containers, observability, scripting languages. Mark what you have used in production.

How well do you know Terraform or OpenTofu on AWS?

Describe one pipeline or platform you built and ran.

What did it deploy, how did you know it was healthy, and what broke first?

03 How you would work here

We record plan fixtures by running terraform plan against real AWS test accounts. The same code should give the same plan JSON, but two runs a day apart differ. What causes this, and how do you make recording reproducible?

Name each source of drift and how you pin or remove it.

Customers pin our Action as wayne-citadel/review@v1. How do you release a new version safely, and what do you do if v1.4.0 breaks plans for some customers an hour after release?

The workflow only needs to read the repository and post a pull-request comment. Which permissions block should it use?

permissions: write-all contents: read and pull-requests: write contents: write and pull-requests: write No permissions block, the defaults are fine

04 Design problem

Wayne Citadel ships as a GitHub Action that customers pin by version. Behind it are a fixture library of plans recorded in real AWS accounts, golden-file tests, and a model evaluation set that costs money on every run.

Assume a small budget, and no long-lived cloud credentials anywhere.

How would you build the CI and release system?

Cover these points. If you think the brief is wrong in part, say so and explain why.

Pipeline stages, and what blocks a merge
Test AWS accounts: isolation, OIDC credentials, cleanup and cost limits
Recording fixtures reproducibly
When the paid model evaluation runs, and its budget
Releases: versioning, signing, provenance, rollback
Secrets and supply-chain security for the Action itself
What you would build in the first two weeks

0 words. Most good answers run 300 to 800.

Your answers are used only to review this application.

Tell us how you build.

Thank you.