Product Security Engineer
Summary
Hands-on product security IC at ZySec AI in Abu Dhabi, embedded in engineering to keep blockchain products secure by design: owning the secure SDLC, threat modelling, code review, smart contract audit coordination, and CI/CD security tooling. Requires 6+ years in appsec (2+ on blockchain/fintech) and speaking Ukrainian or Russian.
Role type: Individual contributor
Reports to: Head of Security and dotted line to Head of Engineering
Location: Abu Dhabi
Language to speak: Ukraine/ Russian
Role Summary: The Product Security Engineer works hand in hand with the engineering team to make sure the blockchain products the organization builds are secure by design. You sit inside the product development cycle rather than reviewing from outside: you join planning, design discussions, and code reviews, pair with engineers on fixes, and own security gates from architecture through release. You work as a hands-on individual contributor with full ownership of product security.
Key Responsibilities
• Work day to day with engineering: join sprint planning, design reviews and release readiness, and give security guidance while features are being built, not after.
• Own the secure SDLC: security requirements, design reviews, code review standards and release security gates.
• Lead threat modelling with engineers for new products and major changes, covering protocol, smart contract, wallet, bridge, API and cloud layers.
• Review code and pull requests for security issues, and pair with developers to fix findings and share the reasoning.
• Coordinate smart contract and protocol security audits: scoping, auditor selection, finding triage, fix verification and public report readiness.
• Integrate security tooling into CI/CD, including SAST, SCA, secrets scanning, container and infrastructure-as-code scanning, tuned so developers trust the results.
• Review cloud and key-management architecture with IT Operations and the Blockchain Security Engineer, including signing and custody flows.
• Run a security champions program with a named champion in each engineering team.
• Own product vulnerability intake: bug bounty triage, disclosure handling and remediation tracking against agreed timelines.
• Maintain secure coding guidance and reusable patterns for common risks in blockchain development.
• Define with the Cyber Defense what telemetry new products must emit so the MSSP can detect abuse.
• Report on product risk, open findings and audit status to the Head of security/ Engineering
Key Relationships
• Engineering leads and developers (daily, embedded)
• Blockchain Security Engineer and Head of Offensive Security (threat models, testing, audits)
• Cyber Defense (detection requirements for new products)
• GRC (secure development evidence for audits)
Required Qualifications
• 6+ years in application security, product security or security engineering, with 2+ years on blockchain or financial technology products.
• Proven record of working inside engineering teams, with developers who see you as a partner rather than a gatekeeper.
• Strong threat modelling experience (STRIDE or similar) and secure design review skills.
• Solid grasp of smart contract security (reentrancy, access control, oracle and upgradeability risks) and the audit process.
• Hands-on CI/CD security experience with modern pipelines and cloud platforms.
• Programming ability in at least one of Solidity, Rust, Go, TypeScript or Python, enough to read and review production code.
• Understanding of key management concepts: HSM, MPC, signing services and wallet architecture.
• One or more of CSSLP, OSCP, GWEB, GSSP, or a relevant audit and competition track record.
Preferred
• Experience with formal verification, fuzzing or invariant testing tools.
• Contributions to public audits, bug bounty findings or open-source security tooling.
• Experience running a bug bounty or responsible disclosure program.
• Prior experience as a software engineer.
Success Measures (first 12 months)
• Security present in sprint planning and design reviews for every product team.
• Threat models completed for every production product and major release.
• Security gates active in CI/CD for all in-scope repositories, with a low false-positive rate.
• Every high or critical audit finding fixed and verified before release.
• A security champion active in each engineering team.
Skills
Sign in to read and join the discussion.