Staff DevOps Engineer, Infrastructure — ChainIT

Staff DevOps Engineer, Infrastructure ChainIT · Remote (United States) · Individual contributor (no direct reports) · Full\-time Be the first in\-house owner of the AWS infrastructure every ChainIT product runs on. One core platform — roughly 25 microservices on AWS EKS — powers our entire portfolio, and you'll set the technical direction for its infrastructure, delivery pipeline, and cloud\-security posture. About ChainIT ChainIT is a private, US\-based, blockchain\-anchored digital\-identity and biometrics platform headquartered in Scottsdale, Arizona. Our mission is to create a zero\-trust digital future, where every identity, action, and agreement is verified, not assumed. We prioritize Truth over Trust: every record we create is a Validated Data Token (VDT) — an immutable, tamper\-proof record of who, where, what, and when, anchored on\-chain and backed by 14\+ granted U.S. patents and a growing IP portfolio. One core platform powers our entire product family — ChainIT\-ID (biometric KYC), ChainIT Org / KYB (business verification), Pactvera (biometric smart agreements), Sportafi (college\-athlete NIL payments), Age App (privacy\-first age verification), ChainITX (physical\-asset tokenization), Touch Audit (tamper\-evident audit trails), ChainIT Pay (embedded payments), and a developer SDK launched at Consensus 2025\. About the role For five years, the AWS estate beneath every ChainIT product — the EKS clusters, the delivery pipeline, the cloud\-security posture — has been built and run largely by an external development partner. As the platform has become core to the business, we're bringing that ownership in\-house, and you are the first in\-house engineer to own it. This is real, live infrastructure at production scale: a revenue\-bearing platform already carrying \~25 services and ten shipped products. You'll take stewardship of it end to end and become the accountable owner of its reliability, delivery speed, cloud\-security posture, and cost — serving every product team, so one well\-designed change to the platform compounds across the whole portfolio. It is a Staff\-level individual\-contributor role with no direct reports. Your leverage is architecture, influence, and the paved\-road patterns everyone adopts — not headcount. You partner with our Staff Backend Engineer (who owns application architecture and code quality) and coordinate with our external development partner during the handoff; you don't supervise either. How this role divides from our Staff Backend Engineer: if a service won't build, won't pass review, or ships a bad API contract, that's the Backend Engineer. If the cluster won't scale, a deploy takes down production, a secret is exposed, or nobody can explain next month's AWS bill — that's you. What you'll own * The EKS platform, end to end — cluster lifecycle across develop/staging/production, namespace\-per\-service topology, ALB ingress, security groups, EFS CSI / IRSA, and capacity planning for \~25 mic