Platform/Infrastructure Engineer

Job title: Platform/Infrastructure Engineer

What you'll actually work on

This is real, current work - not a hypothetical roadmap:

• Multi-region, multi-cloud Kubernetes across US GCP, EU GCP, and AWS GovCloud - making "stand up another site" a self-serve configuration instead of a bespoke project.
• A genuinely self-serve internal PaaS. ~60+ engineers already deploy on it, the large majority with no infra person in the loop. You extend the paved road - golden paths, guardrails, and interfaces engineers actually enjoy using.
• Agent-native infrastructure. Secure sandboxes where AI agents build and ship, and encoding our operational knowledge into skills so the platform increasingly runs and heals itself.
• Zero-trust secrets with Vault. Short-lived, dynamic credentials replacing every long-lived secret in the system - closing the blast radius on leaked passwords, one database at a time.
• Reliability engineering that means it. SLOs and error budgets, real observability, and disaster recovery with validated cross-region restore and sub-hour RTO.
• Databases as a first-class platform concern. Postgres on Kubernetes, migrations, replication, and redundancy for services that can't blink.
• Compliance as code. SOC2 and FedRAMP posture built into the platform so security is the default, not a scramble before an audit.

What you'll own

You'll own an Area of Responsibility end to end - a slice of the platform that is genuinely yours. You'll define what "great" looks like for it and build the glide path to get there rather than waiting for one; obsess over the metrics that tell you whether it's actually working; and fix root causes so a class of problems disappears instead of working the ticket queue faster. You own the outcome, not just your layer of it.

Who you are

This is a builder's role, and the bar is high:

• You've taken infrastructure from zero to one - designed and shipped a platform capability that other engineers came to depend on, not just operated one that already existed.
• You write real software (Go, Python, or similar). You build tooling, automation, and services - you don't only wire up other people's tools.
• You're deep in GCP and/or AWS - compute, IAM, VPC, networking, storage, load balancing - and comfortable operating across clouds.
• You've run Kubernetes in production (GKE/EKS) and are up to date with the state of the art for IaC.
• You can debug low-level problems without hand-holding - a networking issue, a saturated node, a slow query, a failing deploy - and get to the actual cause.
• You're fluent across the modern platform toolchain: GitOps (Argo/Flux), containers, CI/CD, observability built on SLOs rather than dashboards no one reads.
• You have strong instincts for security and databases — zero-trust, secret management, systems hardening; provisioning and migrating production databases. SOC2/FedRAMP exposure is a plus.

If you've built platforms that other engineers rely on every day, we want to talk.

What makes people thrive here

High ownership and low ego. Mission-first. Comfortable where speed and rigor have to coexist - something that takes a quarter elsewhere is expected to move in weeks here, without cutting the corners that matter for security and reliability. You see infra, security, data, and product as one connected system, and you turn one-off fixes into reusable paved roads by instinct.

What should give you pause

The scope is real and the playbook isn't fully written - you'll be writing it. Reliability and compliance expectations are high, and mistakes here show up as real incidents for customers and internal teams. If you prefer an environment where everything is defined before you start, this will feel uncomfortable. If that kind of ownership is exactly what you're after, you'll love it.

How we work

Remote-first (US). Small, high-leverage team with a weekly on-call rotation you'll take part in. We're an AI-native team in practice, not in theory - we use agents in our daily workflow and ship the skills that let the platform operate itself.

The estimated base salary range for this role and level is $205,000 - $245,000

Life at TRM

We are building a safer world. That promise shows up in how we work every day.

TRM moves FAST. We are a high-velocity, high-ownership team that expects clarity, follow-through, and impact. People who thrive here are energized by hard problems, experimentation, and continuous feedback. If something takes months elsewhere, it will ship here in days.

Our work sits at the intersection of AI, national security, and fighting crime. The problems are complex, the stakes are real, and the environment evolves quickly. The pace and intensity of the work reflect the importance of the mission. As a result, the way we operate requires a high level of ownership, adaptability, collaboration, and creative problem-solving.

At TRM, you should expect:

• Priorities and targets to change quickly
• Operating with a high degree of ambiguity
• A high level of personal ownership and accountability
• Close collaboration across teams and functions
• Frequent, high-touch communication
• Creative problem-solving and out-of-the-box thinking
• A pace that rewards urgency, adaptability, and outcomes

This environment is energizing for people who enjoy building, solving hard problems, and making progress in situations that are not always fully defined. It also requires thriving in ambiguity, adjusting course as new information emerges, and maintaining focus and positivity