Hashtag Web3 Logo
Tempo logo

Security Engineer

Tempo
USA (Remote)Posted 226 days ago
Apply

Tempo is hiring a Security Engineer in Engineering — USA (Remote). The overview below is synthesized from the employer posting on jobs.ashbyhq.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.

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.

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

Day-to-day scope for the Security Engineer as described in the posting:

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.

Responsibilities

Day-to-day scope for the Security Engineer as described in the posting:

  • 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

Experience and skills the team lists as required:

  • 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

  • High motor
  • Razor-sharp thinker with precise command of language
  • Concise, evidence-based communicator
  • Excellent organizational and logistical skills
  • Intense curiosity and open-mindedness
  • Scrappiness; willingness to roll up sleeves
  • Growth mindset

Build a standout application

For the Security Engineer at Tempo, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.

Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.

In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.