Menu

DevOps Engineer — The Architect of Flow

100% Remote | Full-Time

Why This Role Matters

There's a moment in every growing company when the distance between "it works on my machine" and "it works for every customer" becomes the defining challenge. The DevOps Engineer is the person who collapses that distance — who builds the invisible machinery that turns a developer's commit into a reliable, observable, production-ready experience.

This role isn't about owning a Jenkins server. It's about designing flow. You'll think in pipelines, feedback loops, and failure modes. You'll ask "what happens when this breaks at scale?" before anyone else does. And you'll build systems so reliable that the rest of the team forgets the complexity you've abstracted away. That forgetting? That's the highest compliment.

What Your Days Will Look Like

  • Build the delivery backbone — Design, implement, and maintain CI/CD pipelines that take code from pull request to production with speed and confidence. You'll make deploys boring — and that's the goal.
  • Shape infrastructure as code — Provision and manage cloud environments (AWS, GCP, Azure, or similar) using tools like Terraform, Pulumi, or CloudFormation. Nothing is configured by hand; everything is versioned, reviewable, and repeatable.
  • Make systems observable — Instrument applications and infrastructure with monitoring, logging, and alerting (Prometheus, Grafana, ELK, Datadog, or your preferred stack). The team should know something is wrong before a customer does.
  • Bake security in, don't bolt it on — Integrate container scanning, secret management, dependency auditing, and least-privilege access into the pipeline itself. Security is a design principle, not an afterthought.
  • Remove friction everywhere — Your job is to make every other engineer's job easier. Slow builds, flaky tests, painful rollbacks — these are your enemies. Hunt them relentlessly.

Who We're Looking For

You've operated in real production environments where downtime has consequences. You've been paged, you've debugged under pressure, and you've built systems specifically so that happens less often.

  • Practical experience building and maintaining CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins, CircleCI, or similar).
  • Comfort working with Infrastructure-as-Code tools to manage cloud resources programmatically.
  • Working knowledge of containers and orchestration — Docker and Kubernetes, or comparable platforms.
  • Scripting proficiency in at least one language (Bash, Python, Go) for gluing systems together and automating workflows.
  • A systems-thinking mindset — you naturally see bottlenecks, single points of failure, and cascading dependencies before they become incidents.

No degree is required. None. Not even preferred. We explicitly value self-taught talent and practical experience. If your education came from deploying side projects, contributing to open-source infrastructure tools, surviving production incidents, or reading every post-mortem you could find — that is a legitimate and respected path. We care about what you've built and what you've learned from what broke.

The Kind of Person Who Belongs Here

We hire character first. The best pipeline in the world means nothing if the person who built it can't be trusted.

  • Honesty as a reflex — When the deploy fails, say so immediately. When you're unsure about an approach, flag it. We build trust by being transparent, especially when it's uncomfortable. A culture of honesty means problems get solved faster and nobody wastes time managing appearances.
  • Loyalty and long-term thinking — We don't hire for projects; we hire for years. We'll invest in your growth — conference budgets, learning time, better tools — because we want you here long enough to see the impact of the systems you design. We're looking for someone who wants to build something lasting.
  • Outcomes over ego — The best infrastructure is invisible. If nobody mentions your pipeline because it just works, that's a win. We celebrate the quiet, compounding value of reliable systems just as much as any flashy feature launch.

Submit Your Information

To begin our hiring process, we collect some basic contact information to get in touch with you. This initial submission helps us understand your availability and communication preferences before we send you a personalized assessment.

After we review your submission, qualified candidates will receive an email with a personalized assessment link. We review every submission personally and carefully — we're genuinely interested in getting to know you through the assessment process.

How to Apply

1

Submit your information using the button above.

2

Our team personally reviews every submission.

3

Qualified candidates will receive an email with a personalized assessment link.

4

Selected candidates proceed to a conversation about the role, the team, and where you want to go.

We're looking for the next architect of our flow. If you build systems that let teams move fast without breaking things, we want to talk to you.

Ready to Apply?

Start by submitting your information — it's the first step in our process.