Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
Storm2’s client, a payments infrastructure FinTech, seeks a Platform Engineer to own significant pieces of the platform, from Terraform migrations to CI/CD and observability. This lean team requires engineers who can implement production changes with independence and build tooling to accelerate others.
You will work across cloud providers (GCP/AWS/Azure), Kubernetes/ECS, and Go/Python/TypeScript, shaping secure, observable infrastructure with strong ownership.
United States, Remote-first
$190k–$230k base + equity
Storm2’s client is a payments infrastructure FinTech processing billions of dollars in annual transaction volume. Their APIs power real-time transfers, bank debits and card disbursements for FinTech, 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.
Experience in payments, FinTech 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.