DevOps Operator

Data Drone builds 0-1 SaaS products and the team that ships them. No bosses, no managers — the playbook manages, the copilot tracks. Every role owns a small, defined space with extreme accountability. The infrastructure has to be as reliable as the product promise.

You'll own the deployment pipeline, the infrastructure, and the monitoring. When code ships to production, you deployed it. When production stays up at 99.5%+, you're maintaining it. When something breaks, your monitoring caught it before anyone else noticed. Deployments are boring because your pipeline makes them boring.

• Daily: watch production health — uptime, error rates, alerts. Catch issues before users do.
• Per release: verify QA sign-off, then deploy through the pipeline. No SSH-to-prod shortcuts.
• Weekly: review cost, capacity, and patching status.
• Monthly: test a backup restore and confirm disaster-recovery readiness.
• Always: document infrastructure as you build it — the runbook is part of the work.

• Own and maintain the CI/CD pipeline (build → staging → production)
• Manage cloud infrastructure (compute, database, storage, CDN, DNS, networking)
• Manage SSL/DNS, secrets rotation, security patching
• Track and optimize infrastructure costs
• Maintain backup and disaster recovery readiness
• Own the Dev Ops Onboarding Playbook

• You've managed production infrastructure on a major cloud provider.
• You’ve built and maintained CI/CD pipelines that deploy to production without manual steps.
• You understand networking: VPCs, security groups, load balancers, DNS, SSL.
• You’ve responded to production incidents — diagnosed, fixed, documented, and prevented recurrence.
• You can write infrastructure as code (Terraform, Cloud Formation, or equivalent).
• You document your infrastructure. Not "I’ll write it up later" — you document as you build.

• Cloud certifications
• Experience with monitoring stacks
• Experience with container orchestration (Docker, ECS, EKS, or similar)
• Experience with cloud cost optimization
• Experience writing runbooks and infrastructure documentation for junior teams

• Boring is beautiful. The best deployment is the one nobody notices. Drama-free infrastructure is the goal.
• Pipeline over SSH. If you're SSH-ing into production to fix something, the pipeline failed. Fix the pipeline, not the symptom.
• Monitor everything. If it's not monitored, you don't know it's down. Unmonitored services are invisible failures.
• Backups are tested, not assumed. A backup that's never been restored is a hope, not a plan.
• Document as you build. Infrastructure knowledge in your head is a single point of failure — until the documentation exists.
• QA signs off. Then you deploy. No exceptions. Not for hotfixes. Not for "small changes." The gate exists for a reason.

• 30 Days — Full infrastructure mapped. Pipeline verified. Monitoring reviewed. Backup health confirmed. Dev Ops Onboarding Playbook friction points documented.
• 60 Days — Deployments are boring. Monitoring catches issues before users. Runbooks complete. Cost baseline established.
• 90 Days — Disaster recovery tested. Infrastructure optimized. Documentation is handoff-ready. Production is stable and trusted.

Cloud platform (compute, database, storage, CDN, DNS, IAM, secrets), CI/CD, monitoring and error tracking, infrastructure-as-code tooling, Slack, Google Drive, AI copilot.

You won't fight fires caused by cowboy deployments. You won't SSH into production at midnight because someone pushed untested code. You won't manage infrastructure that nobody documented.

You'll build and maintain a pipeline that makes deployments boring. QA approves, you deploy, monitoring…