Senior Security Engineer - xStocks
About the role
The team
The opportunity
- Own security deliverables end to end. Coordinate and review smart-contract audits, respond to security questionnaires and due-diligence requests, support CISO and compliance initiatives, and turn findings into tracked, closed-out fixes.
- Run offensive assessments against our own platforms. Pentest the web apps, APIs, backend services, and on-chain components, and build the tooling to do it repeatedly rather than once.
- Continuously assess posture. Threat-model new and existing systems, review architecture and key-management flows, and maintain a living view of the risks and their mitigations.
- Review code for security. Be a default reviewer on changes touching auth, cryptography, custody, signing, and fund movement across our chains.
- Harden the platform. Improve secrets handling, IAM and least-privilege, dependency and supply-chain hygiene, and detection and logging for security-relevant events.
- Secure custody and signing workflows. Review and harden transaction signing flows, MPC and HSM integrations, signer permissions, admin roles, approval policies, and break-glass procedures.
- Contribute to product engineering. Pick up regular backlog work in TypeScript so you stay close to the codebase you are defending.
- Support incidents. Help with detection, triage, response, and post-mortems, and feed the lessons back into the program.
What you bring
- An engineer first. You write and review production code comfortably, TypeScript and Node.js in our stack, and you understand systems deeply enough to break them.
- Strong application and infrastructure security fundamentals. The OWASP-class vulnerability landscape, authn and authz, injection, SSRF, supply-chain risk, and secure design. You have done real offensive work in pentesting, vuln research, or red-team.
- Applied cryptography and blockchain security. Symmetric and asymmetric primitives, hashing, signatures, and key management, plus the security model of EVM, Solana, and ideally TON or Tron. You can read a smart contract and reason about how it fails.
- Ownership. You can take an ambiguous security item, an audit, a questionnaire, or an incident, and drive it to closure without being managed through it.
- Clear communication. You can explain a risk to engineers, to a CISO, and to an auditor, and tailor the message to each.
- An automation instinct. You do not want to catch the same issue manually twice, so you turn findings into tests, alerts, controls, documentation, or platform improvements.
- Risk judgment. You can tell a theoretical issue from a material one, and communicate severity, likelihood, impact, and remediation tradeoffs clearly.
Nice to have
- Experience commissioning or remediating third-party smart-contract audits.
- Familiarity with custody and signing infrastructure such as HSMs, MPC, and ForDefi-style providers, and with on-chain transaction security.
- Cloud security depth in GCP or AWS, IAM, and container and runtime hardening.
- Detection engineering and security observability, including SIEM and log-based detections.
- Relevant certifications such as OSCP, OSWE, or GWAPT.
- Prior work in a regulated fintech or tokenization/DeFi environment.
Unless a specific application deadline is stated in the job posting, applications are accepted on an ongoing basis. Please note, applicants are permitted to redact or remove information on their resume that identifies age, date of birth, or dates of attendance at or graduation from an educational institution. We consider qualified applicants with criminal histories for employment on our team, assessing candidates in a manner consistent with the requirements of the San Francisco Fair Chance Ordinance.
Our commitment
Stay connected
Not included in the source posting: qualifications, benefits.
Skills
Who can apply
The employer didn't state any visa, work authorization, citizenship or clearance requirements in this posting. Confirm with the employer before applying.
Read automatically from the employer's posting text. Always confirm with the employer — requirements can change after a job is published.