Updated by
Hi, I'm Jack, the owner of Cybersecurity Jobs List and co-founder of Himalayas (himalayas.app) and Cavuno (cavuno.com). Across all my platforms, I work with application security daily: dependency vulnerability scanning, secure authentication, API security, and data protection across hundreds of thousands of users. My technical background is in computer science (UNSW). I studied security engineering and computer networks, and worked as a research assistant on VR experiments that were published in the Journal of Experimental Psychology. I also work with cybersecurity hiring data every day, tracking which companies are posting, what certifications actually appear in listings, how salaries differ by sub-discipline and clearance level, and where the talent gaps are widest. That combination of security practice, engineering at scale, and daily immersion in hiring data shapes the content on this site. I'm currently based in Sydney, Australia.

Three employer-listed product security openings checked on 22 November 2026. Each posting can change or close, so use the employer link to confirm it is still open and that your location is eligible.
Product security can mean very different work from one team to another. One role may focus on tenant boundaries in a SaaS platform; another may build systems that validate vulnerability reports; a third may embed security into an AI product suite. Here are three current postings, compared by what you would work on and what to check before investing time in an application.
| Employer and role | Main work | Stated location | First screen |
|---|---|---|---|
| Hightouch: Product Security Engineer | Application security for a multi-tenant data platform, including authorization, isolation and API abuse controls | Remote, North America | Can you read application code, reason about distributed systems and ship production fixes? |
| Vercel: Product Security Engineer | Build tooling that validates reported findings, traces root causes and helps drive reviewed fixes | Hybrid in San Francisco or New York City; three office days a week | Do you want to build security systems, with strong JavaScript or TypeScript and Node experience? |
| Superhuman: Product Security Engineer | Secure the product lifecycle, improve security tooling and bug-bounty work, and develop AI-based security tools | Remote in the United States; San Francisco and Seattle hubs | Do you have substantial application-security experience across secure design, code review and testing? |
Hightouch: secure the boundaries in a multi-tenant product
Hightouch describes this as its first dedicated security hire. The posting centers on application security in a distributed data product: multi-tenant isolation, sub-tenant permissions, compute isolation, high-throughput internet-facing APIs, rate limiting and abuse detection. It also calls out multi-region and multi-cloud architecture.
This is a strong direction to explore if your best evidence is production engineering close to the code. The company asks for experience reading application code, threat modeling distributed systems and shipping fixes. It says the role is remote in North America; that label does not establish that every North American country is eligible, so check the employer page for your location before applying.
Vercel: build the system that handles security findings
Vercel's posting is unusually explicit about the work: build systems that assess external vulnerability reports for validity, severity and reproducibility, then connect confirmed findings to root causes and proposed fixes. It also includes security tooling for customers and ownership of the bug-bounty program. The description emphasizes engineering and automation rather than processing a manual testing queue.
The role may suit a software engineer moving toward security or a security engineer who prefers building tools. Vercel names JavaScript or TypeScript, Node.js and modern web frameworks among the relevant skills. The live posting describes a hybrid role based in San Francisco or New York City, with three days a week in the office. Its application asks about country, preferred location, work authorization and visa support. Confirm your situation on the employer form before investing time; hybrid office days are not the same as fully remote work.
Superhuman: build security into an AI productivity suite
Superhuman's employer page lists a Product Security Engineer role for remote work in the United States, with San Francisco and Seattle hubs. It says remote teammates may travel for scheduled collaboration weeks. The work spans threat modeling, design and secure-code reviews, manual testing, product-security tools, the bug-bounty program and AI-based security tools.
The qualification bar is clearer than in many broad “product security” listings: the posting asks for at least five years securing applications at scale and experience across secure design, code review and web application testing. It also names SAST, DAST and SCA familiarity, programming experience, and vulnerability-disclosure or bug-bounty work. Treat these as the employer's stated criteria, not a universal definition of product security.
Which role should you investigate first?
- You like tracing risk to code and shipping fixes in a distributed SaaS product: start with Hightouch. Prepare an example that shows how you found a tenant or authorization boundary, tested the failure, and improved the implementation.
- You like automation, vulnerability research and developer tooling: start with Vercel. Be ready to explain how you would validate a reported issue, distinguish a real flaw from noise, and connect a root cause to a safe, reviewable fix.
- You have broad application-security experience and want security embedded through product development: start with Superhuman. Pick a project that shows how you influenced design, code, testing and the engineering team's follow-through.
Before applying, make a quick four-column check: work, location, must-have experience, and unknowns to confirm. Copy the employer's actual wording for location and eligibility. If the page is unclear, ask the recruiter rather than relying on an aggregator or assuming that “remote” includes your country.
A focused portfolio exercise
If you need a work sample, use a small application or local lab that you are authorized to test. Draw one trust boundary, explain a realistic abuse path, make a targeted change, and show a test that demonstrates the fix. For a multi-tenant app, that could be an authorization check between two test accounts. For a report-triage tool, use a synthetic finding and document how you reproduce and classify it. Keep the sample small enough that another engineer can follow the reasoning.
Do not test an employer's production systems or submit a speculative finding as a portfolio piece. A clear, reproducible explanation is more useful than a large collection of unverified screenshots.
For adjacent paths, see our guide to moving from software engineering into application security, Cloud Security vs Application Security, and guide to reading security-clearance requirements. Then return to the employer pages above to confirm each vacancy and its terms.


