DevOps / Platform Engineer

Contrarian Thinking is building the infrastructure layer for modern entrepreneurs, and they are seeking a Platform Engineer who automates themselves out of every problem. The role involves owning the infrastructure, ensuring reliability, and managing CI/CD processes, while also focusing on security and automation.

Responsibilities:

• Own CI/CD end-to-end in GitHub Actions: automated deploys, plus test coverage gates, container and dependency vulnerability scanning, and versioned, traceable builds
• Manage all GCP infrastructure as code with Terraform: reusable modules, remote state with locking, and bringing existing infrastructure under code (no manual console changes)
• Build, ship, and run containerized services with Docker across Cloud Run, Kubernetes (GKE Autopilot), and VMs, choosing the right target per service
• Own the reliability of our data stores: provisioning, backups, performance, and safe migrations
• Own platform security: secrets management, least-privilege IAM and workload identity, API key and access controls, and keeping vulnerabilities out of the pipeline
• Configure and maintain Auth0 for identity and login
• Build observability: monitoring, logging, tracing, and alerting (GCP Monitoring, OpenTelemetry) so we catch issues before members do
• Own incident response and on-call through PagerDuty, and run blameless postmortems so the same thing never takes us down twice
• Keep the platform reliable and available: it's what our products and members depend on
• Right-size infrastructure for cost and performance as we scale

Requirements:

• 8+ years owning production infrastructure, not just touching it
• Fluent in Terraform or another infrastructure-as-code tool, including modules and remote state
• Comfortable with Docker, and you know when to reach for Cloud Run vs. Kubernetes vs. a VM
• Strong security instincts: secrets management, least-privilege IAM, and keeping vulnerabilities out of the pipeline
• You automate the second thing you'd otherwise do twice
• You can own on-call, run an incident calmly, and write the postmortem that prevents the repeat
• You work across infra without waiting on others
• You care about outcomes (uptime, deploy speed, systems that don't break)
• Hard requirement: You must be available during US business hours, 9am to 5pm Central Time (CST/CDT), on weekdays
• Built CI/CD pipelines from scratch (bonus if in GitHub Actions)
• Managed multi-service cloud infra entirely through code, modules and remote state included
• Ran containerized workloads across more than one deployment model (Cloud Run, GKE, VMs)
• Hardened a cloud environment: secrets management, workload identity, vulnerability scanning
• Stood up observability and tracing from zero
• Owned real incidents and wrote postmortems that actually stuck
• Auth0 or other identity-provider experience
• Startup, solo builder, or high-ownership environment