Senior Platform Engineer

United States, Remote-first

$190k–$230k base + equity

Storm2’s client is a payments infrastructure Fin Tech processing billions of dollars in annual transaction volume. Their APIs power real-time transfers, bank debits and card disbursements for Fin Tech, banking and marketplace businesses, so reliability and compliance are built into the infrastructure rather than bolted on later.

They’re growing a lean infrastructure team and need another engineer who can take meaningful ownership without relying on a mature platform organisation around them.

Platform engineering gets interesting when a bad infrastructure decision can affect real money moving in real time.

You’ll own significant pieces of the platform underneath the engineering team, from Terraform and environment provisioning through to CI/CD, observability and internal developer tooling. There’s a defined backlog to attack, but not layers of process telling you how to execute it.

This isn’t a role for someone who’s only operated inside a platform that was already mature. They need someone who’s built or materially improved infrastructure themselves, can safely make production changes with a high degree of independence, and likes creating tooling that makes every other engineer faster.

• Owning infrastructure-as-code across networking, IAM, VPCs and environment provisioning, including an ongoing Terraform migration
• Hardening CI/CD, secrets management and self-service deployment tooling
• Building internal abstractions and tooling that let product engineers ship without becoming infrastructure experts
• Expanding observability across service instrumentation, metrics collection, monitoring and alerting
• Supporting production cloud infrastructure and reliability across messaging systems
• Building tooling around compliance, access controls and infrastructure remediation
• Improving developer onboarding, local development workflows, cloud cost visibility and infrastructure documentation

• 5+ years across platform, infrastructure or backend engineering, with substantial production infrastructure ownership
• Strong Terraform, Pulumi, Cloud Formation or comparable infrastructure-as-code experience
• Production experience with GCP, AWS or Azure, with GCP particularly relevant
• Experience building CI/CD and internal developer tooling, rather than simply using an established platform
• Kubernetes, ECS or similar container orchestration experience
• Backend engineering ability in a language such as Go, Python or Type Script
• Hands‑on knowledge of observability tooling such as Datadog, Grafana, Prometheus or Open Telemetry
• A strong understanding of IAM, secrets management and secure‑by‑default infrastructure
• Comfort making production infrastructure changes independently in a small engineering team

Experience in payments, Fin Tech or another regulated environment will translate particularly well. The same goes for engineers who’ve built compliance‑focused platform tooling, worked across GCP and AWS, or supported infrastructure through rapid transaction or engineering‑team growth.

The important distinction is ownership. If your experience is mostly maintaining infrastructure someone else designed, this probably isn’t the right one. If you’ve been the engineer improving the platform while product teams are actively depending on it, it probably is.