DevOps Engineer

Remote, Latin America (minimum 4-hour overlap with US Eastern hours) | Engineering | Reports to: Technical Lead Time Doctor is hiring a DevOps Engineer to run and scale the cloud infrastructure behind our platform. Most of it runs on Google Cloud, defined in Terraform across 40+ environments, with legacy systems still running on AWS.

Your job is to keep it secure, available and quick to change, and to give our DevOps coverage a base in the Americas so that issues during US business hours have an owner in the room. Who we are Time Doctor is a workforce analytics platform that gives distributed teams the visibility they need to improve trust and performance.

We serve remote, hybrid and outsourced organisations worldwide, with particular strength in BPO, healthcare and tech services. We are bootstrapped, profitable and fully remote, with team members across 30+ countries. We built a durable business on customer revenue rather than venture capital, and we are now focused on growing it.

The role You will design, build and operate the infrastructure behind our production, staging, sandbox and customer-specific deployments. You own it hands-on, from Terraform modules and CI/CD pipelines to monitoring, security and your place on the on-call roster. Three things define this seat.

The platform. Google Cloud is home: GKE, Cloud Run, Cloud Functions, Cloud Build, VPC networking, Cloud Armor and Load Balancers, all managed as code. We need someone for whom GCP has been their main platform, not one job inside an AWS career.

The coverage. Our DevOps team works from time zones a long way from most of our customers. This seat exists to cover US Eastern hours, which is why we are hiring in Latin America.

The operating model. Infrastructure as code, GitOps and automation by default. If a task gets done twice, it gets scripted.

Who you are You treat production as yours. When something breaks, you own it until it is fixed and written up. You stay calm in an incident and you are clear in the follow-up afterwards.

You think in modules and environments, not one-off changes. You automate repetitive work in Bash, Python or Go. You care about security: least-privilege access, secrets in Secret Manager, nothing sensitive in code.

You communicate clearly in English, live and async. You are organised and self-directed. You thrive fully remote.

What you will own Infrastructure as code. Terraform across 40+ environments, reusable modules that follow DRY principles, and multi-environment management through GitOps workflows and Terraform Cloud. GCP services.

GKE, Cloud Run, Cloud Functions, Cloud Build, VPC networking, Cloud Armor and Cloud Load Balancers. CI/CD. Pipelines in GitHub Actions, Helm or Cloud Deploy that let our engineers ship safely and often.

Data infrastructure. Redis (Cloud Memorystore) for caching, session management and real-time features. Security.

IAM, Secret Manager and our security services, and acting on what security scans find. Observability and on-call. Proactive monitoring and alerting with GCP Monitoring, Grafana and similar tools, and a place on the on-call support roster.

Our AWS footprint. Keeping the legacy systems we still run on AWS stable. This role may not suit you if GCP has been a side project and most of your production experience is on AWS or Azure.

You prefer clicking through a console to defining infrastructure as code. You want to work purely async. This seat needs real overlap with US Eastern hours.

You are not willing to be part of an on-call roster. You need detailed direction before you can move. What a realistic week looks like A Terraform module refactor that lets a new customer-specific environment come up from a pull request.

A pipeline change that cuts deploy time. A secret moved out of code and into Secret Manager without breaking the services that read it. An alert tuned so it fires before customers notice anything. A handover with teammates in New Zealand, and live collaboration during US Eastern hours.