About This Role

As our new Integrations Engineer, you will be a vital part of our Client Experience organization, embedded directly within our Implementations team. You are stepping into this role to spearhead the delivery of custom, bespoke technical solutions that fall outside the scope of our core product development. Your critical goal is to ensure smooth client onboarding by creating sustainable, well-documented integrations that not only solve unique client challenges but also streamline downstream processes for our operations team post-go-live.

Opportunity & Impact

We are seeking a Staff Security Engineer to take ownership of cloud-native and application security across the Redox platform. This is a high-impact, hands-on IC role where you will move beyond identifying risks to actively hardening our environment, performing code reviews, and translating complex control gaps into engineering proposals that drive production impact.

You will function as a partner to our Engineering teams, embedding security into the SDLC by default. Whether it is container security, Kubernetes hardening, or architecture design, you will have the autonomy to define our standards and ensure the secure path is always the easy path for every engineer on the team.

As a core member of a small, senior team, your technical decisions will scale across our entire network, directly impacting how we protect data for every customer we serve.

We're a fully remote team within the U.S. that operates with radical transparency and a strong bias toward ownership.

Our Engineering Culture & How We Work

Transparency, Ownership & Autonomy
We make room for everyone to be heard, regardless of level. We work openly, normalize not knowing things, and treat "learning out loud" as a feature, not a liability. You'll be expected to bring your real perspective, push back when you see something wrong, and commit fully once a decision is made. As a Staff Engineer, you help cultivate our culture: you model the behavior, you embrace questions, you acknowledge mistakes.

We default to public Slack channels over DMs, post Zoom summaries back in writing, and work async whenever possible. We'd rather expose incomplete thinking in public to get better feedback than protect it in private. That applies to security work too - when you identify a risk or propose a control, you bring it to the table with a recommendation, not just a concern.

We own the systems we maintain, not just the new features on the roadmap. You'll have latitude to identify and drive platform work - defining scope, consulting on priority, and seeing it through from design to operationalization. We measure ourselves by the value we deliver, not the process we follow.