Job Description

Job Description

Security Engineer \n

\n

Department: Engineering

\n

Location: Remote (US)

\n

Type: Contract-to-hire

\n

Intro: Onramp is hiring a Security Engineer. Remote (US). You'd own and advance the security program for a bitcoin custody platform, lead incident response, build AI-driven continuous pen testing, and still ship product code. Two-thirds security, one-third engineering. If irreversible transactions and small-team ownership sound like your kind of problem: hiring@onrampbitcoin.com  

\n

About Onramp \n

\n

Onramp is building the money platform of the future for individuals, businesses, and financial institutions: Bitcoin, dollars, and stablecoins in one place, secured by multi-institution custody and delivered through products people love and APIs institutions build on. We are a FinCEN-registered Money Services Business, run an active SOC 2 Type II program, and work directly with banks, custodians, and financial institutions. Security is not a department here. It is the product.

\n

The Role \n

\n

You'll be the day-to-day owner of Onramp's security roadmap, reporting to our Engineering Lead and partnering with our CCO, who owns SOC 2 and compliance. We already run a layered program mapped to our SOC 2 controls; your job is to take it further and keep it ahead of the threat landscape. About two-thirds of your time is security, the rest is product engineering on the same team. On any given week, you might:

\n

\n

\n
• Advance our controls across identity, endpoint, network, email, and browser layers, and handle the change management that gets a small team to adopt them
\n
• Lead incident response: triage, run the response, coordinate with custody partners when needed, and turn every event into a stronger playbook
\n
• Build AI-driven offensive testing: continuous, agent-assisted pen testing and attack simulation that complements our manual program and feeds findings straight to engineering
\n
• Harden the developer pipeline and cloud posture across GitHub, GCP, and Vercel: supply chain scanning, secrets management, IAM least-privilege, required checks on auth, withdrawal, and KYC paths
\n
• Extend custody-specific monitoring and runbooks: fee wallet controls, signing and quorum alerting, address verification
\n
• Refine the verification SOPs sales and ops use against deepfakes, synthetic identity, impersonation, and coerced withdrawals, and train the team on them
\n
• Run access reviews, service account inventory, vendor risk reviews, and SOC 2 evidence as part of the work rather than after it
\n
• Govern our AI-native toolchain with a lightweight pre-adoption review for new connectors and agents
\n
• Ship product code in our TypeScript/Next.js and Elixir/Phoenix services
\n

\n

Who You Are \n

\n

\n
• 4+ years hands-on security engineering, ideally at an early- or growth-stage fintech, custody, or exchange, where you owned the controls, not just the findings
\n
• You've run incident response end to end and written the post-incident review
\n
• Offensive-minded, with pen testing experience and real interest in making it continuous with AI agents
\n
• A working software engineer on at least one side of a modern stack (React/Next.js and TypeScript, or Elixir/Phoenix, Node, or comparable)
\n
• Deep on identity, endpoint, and cloud security in a Google Workspace, GitHub, GCP, and Vercel environment, and opinionated about right-sizing tooling for a small team
\n
• Fluent in today's threats: AI-driven supply chain attacks, session theft, OAuth phishing, deepfake social engineering
\n
• SOC 2 in practice: you know what an auditor asks for and build evidence into the workflow
\n
• Insanely AI-native, with strong views on securing agents without adding friction
\n
• A clear writer of runbooks, threat models, and async updates people actually read
\n
• Calm in an incident, direct in a review, comfortable with early-stage ambiguity and pace
\n
• You don't need Bitcoin protocol experience to apply. You do need to be curious about it and willing to go deep on custody fast. 
\n

\n

Nice to Have \n

\n

Bitcoin custody experience (multisig, PSBT, key-agent architectures), Elixir/Phoenix, agentic security tooling, GCP Security Command Center or Wiz, Terraform, OSCP or equivalent, CTFs or public disclosures.

\n

Why This Role, Why Now \n

\n

\n
• Ownership: the program, standards, and tooling are yours to drive as we scale
\n
• Stakes: we custody bitcoin for HNW clients, RIAs, and institutions. Withdrawals are irreversible
\n
• The AI moment: budget and mandate to push AI-native security on both the defensive and offensive side
\n
• Range: security engineer and product engineer in one seat, on a small team where you see the whole system
\n

\n

How We Work \n

\n

Remote-first (US), high-trust, low-ceremony. Small pods, direct communication, written culture, biweekly all-hands with live AI demos. We care about output, not hours.

\n

\n

This role starts as a remote contract with a clear path to full-time and equity once fit is confirmed on both sides.

\n

The Process \n

\n

Intro call, technical conversation with the Engineering Lead and CCO, a working session (bring your AI toolkit), founder conversation, offer.

\n

What We Offer \n

\n

\n
• High agency and first-principles thinkers
\n
• Flat structure, builder-first execution culture
\n
• Mission-driven: Bitcoin only, no altcoins
\n
• Collaborative, transparent, and low-ego
\n
• Competitive compensation, with meaningful equity on conversion to full-time
\n

\n

How to Apply \n

\n

Send your resume and a short intro video to hiring@onrampbitcoin.com covering:

\n

\n

\n
• A security control or program you owned end to end and how you got a team to adopt it
\n
• An incident you helped run and what changed because of it
\n
• One AI-leveraged workflow you've built or wished you had
\n
• Why Onramp
\n

\n

\n

Email subject: Application — Security Engineer

Job Tags

Full time, Contract work, Remote work

Similar Jobs