Infrastructure Team Lead, Storage Migration

Cinderforge's aging storage backend is partway through a multi-quarter replacement with something more scalable, and this lead role runs the four-person storage infrastructure team carrying that migration out. The current backend is already showing capacity warnings on its largest customer shard, which gives the project a real, if not yet urgent, deadline.

Planning the migration in phases that avoid customer-visible risk is the first job here, given how badly a storage migration can go if rushed; the role also means staying personally hands-on with the hardest technical problems rather than delegating everything, and representing the storage team in the infrastructure organization's monthly planning review. The team is four engineers today and expected to grow by one or two over the coming year as the migration's scope becomes clearer.

Required: deep storage and Kubernetes experience — direct exposure to Ceph specifically — plus Go for the tooling work and some prior experience leading a small team's planning through a genuinely risky technical project. Cinderforge scopes this seat by what it owns — running a four-person team through a multi-quarter migration with real customer-facing risk — rather than by a specific year count. Formal people-management credentials are not required if the technical leadership track record backs it up.

Migration planning and the monthly cross-team review set the rhythm for in-person days at Cinderforge's Austin office, where this hybrid role is based. You would report to the director of infrastructure and manage the four engineers on the storage migration team directly, with real latitude over how the migration phases are sequenced.