Senior Software Engineer, Infrastructure

About the role

About VSCO

For years, we've helped photographers create their work. Now we're building what comes next.

VSCO exists for photographers. Not as a side feature, not as an afterthought, but as the whole point. We build the connected system photographers rely on, and we've spent over a decade earning the trust of a global creative community that takes the craft seriously.

Photography is at an inflection point. AI is reshaping what's possible for creative work, and that's where our mission shines. VSCO is building the full photographer's workflow: from creating and editing your work, to delivering it to clients, to running your business. All of it built thoughtfully, with photographers leading the way. We believe the future of photography tools creates more space for creativity, handling the busy work so photographers can focus on the craft.

If you care about craft, community, and what technology can unlock for creative people, this is the work. We're a mission-driven and focused company where your work ships quickly, is meaningful, and reaches tens of millions of people worldwide. You'll have a real say in what we build and how we build it. We hire people who don't wait to be asked, naturally connect the dots, care about the quality of what they ship, and believe the best outcomes come from building together.

About The Role

We’re looking for a Senior Software Engineer, Infrastructure to own the platform that VSCO product and data teams ship on. You’ll join a small infra team that treats AWS, EKS, and GitOps as the default path for new systems, and you’ll spend real time pairing with other teams so - search, Workspace, and data - land in the right Terraform, Helm, and Flux instead of one-off snowflakes.

This is a hands-on senior seat. You will design Terraform modules, cut production traffic to EKS, secure traffic with Cloudflare, look for optimizations in our AWS infrastructure, and leave on-call better than you found them. You like production ownership, you can sequence a cutover, and you can teach another team why their service belongs in shared-infra versus an app repo.

The day-to-day

- Design, build, and operate the AWS and EKS platform using Terraform, Helm/Kustomize, and Flux GitOps across infra, shared-infra, and app-owned repos (Workspace, search, data).

- Own production cutovers end to end: ingress, DNS, workers and crons, telemetry monitors and dashboards, and a rollback plan you would actually use.

- Partner with product and data teams on the right home for new infra, including namespaces, secrets (SOPS, IRSA), preview environments, and not reinventing namespace or secret wiring that already lives in shared-infra.

- Build and maintain CI/CD on GitHub Actions, including self-hosted runners, image builds, and deploy pipelines that other teams can copy. That means supporting the build and test pipelines, container images, and runners for our language ecosystems (Go, Python, PHP, Node, Java, Ruby, and similar) so those teams can compile, test, and ship, rather than writing their application code yourself.