Security Engineer, Institutional Trading

Blockchain Lab analysis

London security engineer for institutional trading at Blockchain.com. Pay is not disclosed. Work-from-anywhere is twenty days a year, not a remote contract. The company is private.

Ninety days — illustrative

Not the employer’s onboarding plan.

1. Days 1–30: one map of a trading workflow, signed by the desk that runs it.
2. Days 31–60: one monitor in the SIEM for a signal they already care about.
3. Days 61–90: a risk treatment that names an owner and a date, not a framework.

A week you can rehearse

• Describe a trading-key incident without melodrama.
• Say what DORA would make you evidence, even briefly.
• Ask the London cash range.

Ask them

• What is the salary range in GBP or USD, in writing?
• What is the equity instrument, and when was it last priced?
• Is the twenty-day clause the whole remote policy?

Walk away if

• Pay stays 'competitive' past the second conversation.
• The seat is a contract audit after the posting said it was not.
• London is 'flexible for the right person' with no entity named.

Proof you can build before you apply

• The security-review lab. One trading-workflow threat, one mitigation. Do not test their production.

• Failure atlas
• Canon

Blockchain Lab analysis

Public reporting and the employer’s own releases. Not a relationship with Blockchain Lab. Not a credit opinion.

Founded

2011, as the posting says.

Base

London for this seat.

Status

Private. Do not treat it as a listed company. A wallet-user count is not a valuation.

People

Peter Smith is the long-time chief executive. Nicolas Cary is the co-founder associated with the company in public. This brief does not invent a current org chart above the security team.

1. Not restated

   Venture history, not a live mark

   Not disclosed here

   The company has raised before. This pass does not repeat a valuation from a database. The posting offers 'meaningful equity' and does not price it. A failed attempt to become a public company is part of the industry's memory of the brand. It is not a current listing. Ask what the last priced round was, and whether common still sits under a stack from a hotter market.

• No pay band. 'Based on experience' is not a negotiation if they will not anchor.
• Equity adjective without a cap table.
• Institutional trading at a consumer-wallet company can be a small desk with a large job description.
• DORA and similar regimes are real work. If you have not operated a control, do not bluff it.

Ask them

• What is the band for London, and what did the last person in the seat make?
• What percentage is 'meaningful', and what is the last round's price?
• How many people are on institutional trading, and who signs the risk treatment?
• Is the 20-day perk the only remote, and which entity employs the UK?

• The posting, including the company figures and the 20-day perk
• Blockchain.com

If a figure is not in those sources, it is not in this brief on purpose.

Employer stated. Security engineer for Blockchain.com’s institutional trading stack in London: trading workflows, custody touchpoints, key hygiene, and the monitoring of order and settlement signals.

• Partner with Trading, Middle Office and Quant (Institutional FinOps) teams to map out inventory trading systems, data flows, third-party integrations and custody/settlement touchpoints.
• Conduct deep-dive assessments mapping critical assets and workflows to identify structural vulnerabilities. You will be responsible for defining the Target State and drafting the strategic Risk Treatment Plans (RTP) required to meet institutional-grade standards (e.g., CCSS, NIST, DORA).
• Act as the primary security liaison for Senior Management and third-party vendors. You will translate complex technical gaps into actionable business risk summaries, drive vendor evaluations for core security infrastructure, and manage the project lifecycle for high-impact posture uplifts.
• Implement and maintain monitoring for FinOps-specific security signals such as abnormal order patterns, signature misuse, unusual settlements. You will integrate these signals into our SIEM/SOAR for real-time response.
• Support secrets and key-management hygiene. You will ensure app/service keys are stored in KMS/Vault, scoped to least privilege and rotated automatically to prevent credential leakage.

Source: the employer’s public Greenhouse record, job 7904343. Open the original. First seen by this desk 2026-10-06. Nothing above the fold is a substitute for that page.

Blockchain Lab analysis. These lines are a reading of the advertisement. They are not extra hiring requirements.

• Map the path from an order to a custody movement before you talk about AI.
• The posting asks for CCSS, NIST, and DORA language. That is a control-design seat.
• Wallet-user counts on the company blurb are not the risk of this desk.

• Anything the compensation line does not already quote. A printed band is the employer’s sentence for the place they named — not a Blockchain Lab estimate, and not a promise for every location on the posting.
• Closing date, and the day the role was first published. The board timestamp is an update.
• Which countries may apply. “Remote” alone is not worldwide eligibility. If the employer wrote a country or a region, that sentence is theirs — still ask which entity can hire you.
• Visa sponsorship, the real on-call rota, and the employing subsidiary, unless the posting already named them.