DRDarko Ronićdarko@ronic.co

Principal Engineer, SRE · Zapier

I build the infrastructure everything else depends on.

I set the direction for infrastructure and platform across an org, and design the primitives that decide how hundreds of services work together — then stay close enough to the work to make sure it actually lands.

8 yrs
at Zapier
16 yrs
in production engineering

Shai-Hulud Devours the Cygnus Clouds · 28h 50m · photographed by me

What I work on

Scope, not project list

  • Technical direction

    Setting the direction for infrastructure and platform across an org, and planning years ahead without blocking the work in front of us. Both halves matter; over-optimizing for tomorrow is its own failure.

  • Platform primitives

    Designing the defaults, interfaces, and guardrails that determine how an engineering org interacts with its platform — so the correct choice is also the easy one.

  • Architecture at scale

    Hundreds of services working together: ownership boundaries, isolation, and blast radius. Going deep on the hard problem, then writing the path forward clearly enough for everyone to follow.

  • Service communication

    Service mesh, discovery, and cross-service patterns that make the right call between two services the default rather than something each team re-derives.

  • Delivery and environments

    Helm, Argo CD, Kustomize, Terraform, and GitLab pipelines — plus local development, sandbox environments, and ephemeral deployments. Shortening the distance between an idea and something running that behaves like production.

  • Reliability and observability

    SLOs that describe what users feel, incident follow-up that changes the platform, and telemetry organized around the questions people ask at 3am.

Background

Career · Education · Capabilities

Darko Ronić, black and white portrait

Sixteen years of production engineering, the last eight at Zapier, where I went from on-call reliability work to setting the direction for infrastructure and platform across the engineering org.

2025 Present

Principal Engineer, SRE· Zapier

Technical direction for infrastructure and platform across the engineering organization: deciding what the platform should make easy, and what it should make hard.

  • Set multi-year direction for reliability and platform work, sequencing what has to be solved now against what can safely wait.
  • Design org-wide primitives — ownership, deployment, service communication, environments — adopted because they are the shortest path, not because they are mandated.
  • Go deep on the hardest problems, draft the path forward, then bring the owning teams along it. Mentor staff and senior engineers across the organization.

2021 2025

Staff Engineer, SRE· Zapier

Platform strategy and cross-team delivery for a system of hundreds of services, from edge routing to service ownership.

  • Defined the long-term roadmap for the infrastructure organization and aligned it with enterprise requirements.
  • Designed and delivered shared routing, service discovery, and ownership foundations adopted across engineering.
  • Shaped reliability and observability practice so teams could reason about their own services rather than escalate.

2020 2021

Senior Engineer, SRE· Zapier

Reliability engineering for a large Python monolith and the AWS infrastructure around it — the ground the later platform work was built on.

    2018 2020

    Engineer, SRE· Zapier

    Site reliability for a rapidly growing product: AWS, Kubernetes, Python, and infrastructure as code.

      2010 2018

      Server Development Lead· Nanobit

      Led backend development for a portfolio of mobile games, from the first server to a multi-title platform.

      • Built the backend platform for a portfolio of mobile games on AWS, from the first server through a multi-title architecture.
      • Automated deployments across a fleet of EC2 instances, replacing manual release work.
      • Spoke at EuroPython 2014 in Berlin on scaling a Python game backend to the cloud.

      Beyond the terminal

      Astrophotography · Film · Cycling

      The engineering work is what I get paid for. These are the things that keep the rest of it balanced — and they have more in common with the day job than they first appear: patience, calibration, and a tolerance for long feedback loops.

      Astrophotography

      Deep sky from a city balcony and wherever the sky is darker.

      Most of my imaging is narrowband: hydrogen and oxygen emission from nebulae, hours of exposure stacked until the noise falls away and structure appears. A single frame can take several nights, and most of the work happens after the telescope is packed away — calibration, stacking, and a lot of judgement about how far to push the data.

      I shoot from Zagreb when the sky allows it and take the rig further out when it does not. Galaxies and reflection nebulae need dark skies and broadband; emission nebulae are forgiving enough that the city is not fatal.

      Rig
      Askar 107PHQ · Askar FRA400 · 150mm Ritchey-Chrétien
      Camera
      ToupTek ATR533M · ATR3 CMOS 26000 KPA
      Typical integration
      4h to 28h per image

      Film photography

      Fewer frames, and a closet full of chemistry.

      I shoot film because it forces a different pace: fewer frames, more deliberation, and a result you cannot check on the back of the camera. I develop and scan at home, which turns the whole process into something I actually control end to end.

      Mostly black and white, but not only — three weeks in Japan during cherry blossom season became a colour series, and the difference in grain and latitude between stocks is half the reason to keep shooting it.

      Cameras
      Leica M7 · Leica CL · Nikon FE2 · Nikon 35Ti · Fuji GF670 · Mamiya 645 Pro · Hasselblad 500C/M
      Process
      Home development and scanning, black and white and C-41

      Road cycling

      Climbs, and the training it takes to enjoy them.

      Road cycling has been the constant since the running years. I ride year round, including the cold months, and I still prefer a long climb to a fast flat — the kind of effort where pacing matters more than power.

      It is also the most reliable way I have found to think through a hard problem: no screen, no notifications, several hours of nothing but the road.

      Contact

      If it concerns reliability, infrastructure, or a hard system problem — I'm interested.

      The fastest route is email. I read everything, and I reply to anything that is not a recruitment template.

      darko@ronic.co