Security Engineer

Tempo tempo.xyz Open · verified Oct 24, 2026

Remote United States Full-time Mid-level Security Engineering

At a glance

Mid-level Security Engineering role at Tempo. Remote, United States · full-time · no salary stated · we estimate $120,988–$189,241 across the United States.

Estimated pay

Tempo has not published a salary for this role. The figure below is our estimate, not theirs.

$120,988 – $189,241

What the middle half of mid-level security engineering roles in the United States paid, among postings that did state a salary.

Worked out from 431 postings that stated pay, median $150,500. Last updated Oct 23, 2026.

RoleSecurity Engineering

SeniorityMid-level

LocationUnited States

WorkplaceRemote

EmploymentFull-time

PostedJan 12, 2026 · 9mo ago

Role brief

remoteroles summary, based on the employer's posting.

What you'll do

Probe Tempo’s protocol, consensus system and bridge for weaknesses, including through ongoing mainnet testing
Build security tools and automated checks with the Foundry team to expose logic flaws and unusual execution cases
Review important architectural decisions with engineering teams across the codebase
Assess protocol incentives, including MEV and staking, to uncover ways attackers could profit

What you bring

You can read and write production-quality systems code, with Rust especially valued
You know EVM internals in depth, including opcodes, storage slots, gas accounting and precompiles
You have offensive security evidence such as strong CTF results, serious bug bounty findings or published research
You have built custom security automation, rather than depending only on existing scanners

Who this fits

This role suits a hands-on security engineer who enjoys continuous offensive testing, protocol analysis and building bespoke tools. It is a full-time remote role for someone based in the United States.

From the employer

Tempo is a layer-1 blockchain purpose-built for stablecoins and real-world payments, born from Stripe’s experience in global payments and Paradigm’s expertise in crypto tech.

Tempo’s payment-first design provides a scalable, low-cost predictable backbone that meets the needs of high-volume payment use cases. Our goal is to move money reliably, cheaply, and at scale. Our north star is simplicity for users: fintechs, traditional banks, merchants, platforms, and anyone else looking to move their payments into the 21st century.

We're building Tempo with design partners who are global leaders in AI, e-commerce, and financial services: Anthropic, Coupang, Deutsche Bank, DoorDash, Mercury, Nubank, OpenAI, Revolut, Shopify, Standard Chartered, Visa, and more.

We’re a team of crypto-optimists, building the infrastructure needed to bring real, substantial economic flows onchain. We like to move fast and swing for the fences — join us!

The Role

We are building a full-time internal Red Team to continuously stress-test our own infrastructure. As a security engineer, you won't just be ticking compliance boxes; you will be writing Rust fuzzers, simulating economic attacks on our testnet, and dissecting the EVM to find edge cases in our execution client. We are looking for a builder who understands that the best way to secure a protocol is to try to break it continuously. If you have a history of topping CTF leaderboards, submitting high-severity bug bounties, or building your own security tooling because the standard ones weren't good enough—this role is for you.

Responsibilities

Proactively hunt for vulnerabilities in the Tempo protocol, consensus engine, and bridge architecture, treating our mainnet like a continuous CTF challenge.
Design and implement security tooling and automation in liaison with the Foundry team to catch logic errors and edge cases.
Partner with engineering teams to review critical architecture across our codebase.
Analyze incentives and game-theoretic risks within the protocol, such as MEV and staking dynamics, to prevent economic exploits.

Qualifications

Fluency in reading and writing production-level code in systems languages, with a strong preference for Rust.
Deep expertise in EVM internals, including intimate knowledge of opcodes, storage slots, gas metering, and precompiles.
Proven track record of offensive security, such as high rankings in CTFs (e.g., Paradigm CTF), high-severity bug bounty submissions, or published research.
Experience building custom security automation or tooling rather than relying solely on off-the-shelf scanners.
Bleeding-edge knowledge of the latest blockchain security research, including recent hacks and how these could have been mitigated.

Attributes