Own security across Opal's product and platform, embedding directly with engineering to build security into the product from the design phase.
Posted by employer 3 months ago
First seen on Joblaze 1 week ago
Last verified on the company career page 1 day ago
Skills & Technologies
Role intensity
70% hands-on coding
Requirements
Not disclosed in this posting: compensation, work arrangement, visa sponsorship.
Joblaze summary
The Application Security Engineer at Opal is responsible for integrating security throughout the product development lifecycle, from threat modeling to code reviews and incident response. This role requires proficiency in Go and TypeScript, along with a deep understanding of authentication protocols like OAuth 2.0 and SAML, as well as experience in cloud environments such as AWS. Ideal candidates have at least four years in application security and a track record of leading security initiatives, thriving in a collaborative and ownership-driven environment. Opal's focus on security means this position is central to the company's mission, making it a critical role within the team.
Joblaze insights
Quick facts
From the original posting
About Opal Security:
At Opal, we’re building modern identity governance for the AI era—intelligent access management that empowers enterprises to move fast while staying secure. Our mission is to bring clarity, control, and confidence to complex enterprise environments, helping teams govern access without slowing down innovation.
The Role:
Most security engineers spend their careers bolting locks onto doors that were already built. This is not that job.
We're hiring an Application Security Engineer to own security across Opal's product and platform — and yes, own means what it sounds like. You'd be our dedicated security engineer, embedded directly with engineering, writing production code in Go and TypeScript, and building security into the product while it's still being designed. You’ll work closely with a team of engineers that genuinely care about getting this right, and a product that happens to be one of the most security-critical tools in enterprise software.
Oh, and one more thing: Opal is a security company. We sell access control to organizations that take security seriously. That means your work isn't a cost center — it's core to what we do.
This role lives on the Platform team and partners closely with Infrastructure Engineering on cloud security. It is explicitly scoped to application and product security — enterprise IT, compliance, and vendor risk management are handled separately.
What You’ll Do:
Secure Development Lifecycle -
Own the secure SDLC end-to-end: threat modeling, design reviews, code reviews — you set the bar
Run and coordinate app pentests (internal and external) and drive findings to closure
Build and own SAST/DAST/SCA tooling wired into CI/CD so security ships with the code
Triage and remediate vulnerabilities from every angle — bug bounty, internal scans, the works
Software Security Engineering -
Build and maintain the security-critical stuff: encryption services, authz enforcement, authn flows
Own the Auth0 ↔ Opal integration — tokens, sessions, MFA, SSO (SAML, OIDC, OAuth 2.0)
Ship production Go and TypeScript to harden APIs, enforce least-privilege, and close vuln classes for good
Create shared libraries that make the secure path the easy path for every product engineer
Incident Response & Cloud Security -
Be first on the scene for security incidents: investigate, contain, find the root cause, fix it
Partner with Infra on cloud hardening — AWS IAM, EKS, KMS, network segmentation
Level up detection and response by writing detection rules and improving logging and alerting
Security Culture -
Mentor engineers on secure coding, common vuln patterns, and security architecture — you make the org smarter
Help set the security roadmap by grounding it in real product risk
Be the security teammate engineers want to work with — a collaborator, not a bottleneck
You Might Be a Fit If You:
Have 4+ years in application security or software security engineering
Actually write production code — findings reports are the floor, not the ceiling
Know auth cold: OAuth 2.0, OIDC, SAML, session management, token lifecycle
Are comfortable in AWS and containerized environments (Kubernetes, Docker)
Bonus points for familiarity with our stack: Go, TypeScript, React, PostgreSQL, Redis, GraphQL
Have led complex, cross-functional security initiatives from kickoff to completion
Have run or participated in external pentests and seen findings through remediation
Thrive on ownership and ambiguity — you'd rather write the playbook than wait for one