DevOps and Infrastructure Engineer

We’re looking for a DevOps & Infrastructure Engineer who enjoys owning infrastructure end-to-end and building reliable systems in a fast-moving startup environment.

You’ll work across our infrastructure, deployments, cloud, observability and data systems. This is a role for someone who wants to do more than maintain servers or close deployment tickets. You’ll help shape how we build, deploy, operate, scale and secure production, with real ownership over the infrastructure that keeps our product running.

What you’ll do 🛠️

• Own infrastructure from design to production across development, staging, UAT and production environments.
• Build and improve CI/CD pipelines so engineers can ship changes safely, quickly and consistently.
• Establish reliable deployment strategies, including rolling, blue/green and canary releases, rollbacks and safe migrations.
• Manage and improve cloud infrastructure: networking, compute, storage, queues, caches and supporting services.
• Operate and scale production data stores (PostgreSQL, MongoDB, Redis, Kafka), including performance tuning, backups and recovery.
• Support data pipelines and help meet data residency, retention and security requirements for enterprise customers.
• Own observability across the platform: metrics, logs, traces, profiling and dashboards, with low-noise alerting tied to real user impact and clear runbooks.
• Investigate production incidents and drive them from detection through root cause to a permanent fix.
• Build infrastructure that behaves well under real-world failures: service outages, network issues, resource exhaustion and partial outages.
• Plan for scale, including horizontal scaling, capacity planning and traffic spikes, without over-engineering.
• Automate repetitive operational work and set sensible standards for configuration, secrets, environments and access control.
• Work closely with backend and frontend engineers on architecture and developer experience, bringing an infrastructure view into design discussions early.

What we’re looking for 🔎

• 3+ years of experience building and operating production infrastructure, not just writing deployment configs.
• Strong understanding of Linux, containers, cloud infrastructure and production operations.
• Solid networking fundamentals: DNS, HTTP, TLS, load balancing, reverse proxies, TCP/IP and firewalls.
• Hands-on experience with CI/CD, infrastructure-as-code, observability and reliability engineering.
• Experience operating production databases, including backups, recovery and performance.
• Good understanding of distributed systems and failure handling: retries, timeouts, health checks, graceful degradation and recovery.
• Strong debugging skills across applications, infrastructure, databases, networks and external dependencies.
• Ownership mindset: you take a problem from first investigation through to a permanent fix.
• Comfort with ambiguity and making good decisions with incomplete information.
• Clear communication and the ability to balance speed, reliability, simplicity and long-term maintainability.

Nice to have ✨

• Kubernetes, Docker and container orchestration
• Terraform or other infrastructure-as-code tooling
• AWS, GCP or Azure
• GitHub Actions, GitLab CI, ArgoCD or similar CI/CD platforms
• Grafana stack (Prometheus, Loki, Tempo, Alertmanager, Pyroscope) and OpenTelemetry
• SLOs/SLIs, error budgets, on-call tooling (PagerDuty, Opsgenie) and postmortems
• Kafka, Redis, PostgreSQL, MongoDB or other distributed infrastructure
• Data pipelines (ETL/ELT, batch or streaming) with tools like Airflow or dbt, and strong SQL
• Data governance, residency and retention requirements
• Secrets management, IAM, certificates and infrastructure security
• Go, Python, Shell or TypeScript for automation and tooling
• Experience at an early-stage or high-growth startup

What we value 🧭

• Ownership over handoffs: you help get the system healthy, even if the issue technically belongs to someone else.
• Automation over repetitive manual work: if we do it twice, we should probably automate it.
• Reliability over “the deployment succeeded”: a successful deploy isn’t the same as a healthy production system.
• Observability over guessing: we diagnose from metrics, logs and traces, not symptoms.
• Simple infrastructure over unnecessary complexity: technology should solve real problems, not follow trends.
• Engineering judgment over blindly following process: we care about why, not just following a runbook.
• Outcomes over infrastructure code: Terraform and pipelines are a means to an end. The goal is a reliable platform.

This is a high-ownership role where you’ll have meaningful influence over both the product and the infrastructure that runs it.

Probably skip 🚫

• You want a narrowly scoped role where ownership ends once a deployment succeeds.
• You see DevOps as mostly writing YAML and maintaining CI pipelines.
• You avoid production incidents or difficult debugging.
• You’d rather fix recurring problems manually than automate them.
• You rely on AI-generated infrastructure configs without understanding what they do.
• You treat security, backups, disaster recovery and capacity planning as someone else’s problem.
• You’re uncomfortable with ambiguity, changing priorities or early-stage startup constraints.

How to apply? 🧑🏻‍💻

Send your resume and a short note on why you’re a great fit to [email protected] with the subject line “DevOps & Infrastructure Engineer – [Your Name]".