David Navarro

Senior DevOps, on a contract basis.

Short engagements for startups and small teams that need a senior platform engineer without making the hire yet. AWS, Kubernetes, Terraform, CI/CD, and the tooling that holds it together.

Start a conversationRésumé (PDF)

Available now / 2 to 12 weeks / hourly or fixed scope

David Navarro

What I can build for you.

  • AWS architecture and cost

    A greenfield account set up properly, or an audit of the one you have. Multi-account organisations, networking, IAM, and cost cuts that survive the next quarter.
  • Terraform and infrastructure as code

    Move click-ops into Terraform, with module and state structure a small team can operate safely. Plan on pull request, apply on merge.
  • CI/CD pipelines

    CircleCI or GitHub Actions tuned for deploys that are fast and boring. Blue/green, canary, and ephemeral environments per pull request. I can pick up a Jenkins estate too, though I would rather help you leave it.
  • Kubernetes and containers

    EKS and GKE clusters with the Helm and Argo plumbing around them. Workloads that scale and recover without paging anyone at 3am.
  • Reliability and security

    Observability in Datadog, an on-call rotation people can live with, an incident process, and a security baseline you can defend in an audit.
  • Internal tooling

    The small Next.js and Node services, dashboards and bots that unblock your team. The ops tools nobody has time to build.

What changed on the last two platforms I ran.

  • 30+ hours of manual ops work a month removed with Bash and Python automation.
  • AWS spend down 20% at Blue Apron by moving cross-account infrastructure to Terraform.
  • Mean time to detect cut in half with Datadog monitoring and alerting.
  • A custom CircleCI Orb replaced a paid third-party deploy product across the org.

40%

faster deploys after rebuilding the CI/CD pipelines for ECS services at Agero

85%

fewer critical vulnerabilities after hardening images and dependencies

99.997%

platform availability, with shift-left QA and test automation

How I work.

The parts people usually find out too late.

  • Async first

    A weekly written update and a shared channel. It works across time zones and leaves a paper trail you can read later.
  • Remote, English or Spanish

    US East hours by default, from Charlotte, NC. Bilingual, so a Spanish-speaking team is no friction.
  • You get me, not a bench

    I do the work myself. Nobody junior gets handed the keys to your production account halfway through.

How an engagement runs.

  • Intro call

    Thirty minutes. You describe the problem, I tell you honestly whether I am the right person for it. No charge.
  • Written scope

    One page: deliverables, timeline, and price, hourly or fixed. You know what you are buying before anything starts.
  • The work

    Async, in a shared channel, with a written update every week and a demo when a demo helps more than a paragraph.
  • Handoff

    Docs, runbooks, and a walkthrough, so your team owns it after I am gone. No lock-in to me.

Need a hand with platform work?

The button opens an email draft with the questions I would ask anyway: company, scope, timeline, stack. Five minutes to send.

Start a conversation