> Markdown version of [/jobs/ext/4758118-member-of-technical-staff-software-engineer-cybersecurity-products](https://www.wearedevelopers.com/jobs/ext/4758118-member-of-technical-staff-software-engineer-cybersecurity-products). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Member of Technical Staff (Software Engineer, Cybersecurity Products) - **Company:** PERPLEXITY LLC - **Location:** San Francisco, CA, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Amazon Web Services, Software System Penetration Testing, Application Testing, Software as a Service, Cloud Computing, Cloud Computing Security, Code Review, Continuous Integration, Python (Programming Language), Software Engineering, Systems Integration, TypeScript, Large Language Models, Software Security, Data Management, Software Version Control, Data Pipelines, Golang, Programming Languages - **Published:** November 17, 2026 - **Apply:** https://startup.jobs/member-of-technical-staff-software-engineer-cybersecurity-products-perplexity-10777157 ## About the Role * 4+ years of experience as a software engineer building production systems, with meaningful time spent on security products, security data platforms, or security engineering with heavy software development. * Proficiency in at least one major programming language (such as Python, Go, TypeScript, or Rust) and experience owning production services end to end. * Hands-on depth in at least one security domain, such as application security, penetration testing or offensive security, cloud security, or detection and response, and curiosity to work across the others. * Experience integrating with security- or developer-relevant systems such as source control, CI/CD, cloud provider APIs, identity providers, scanners, or SIEMs. * Familiarity with cloud infrastructure (AWS preferred) and building secure, multi-tenant SaaS. * Comfortable working directly with customers and shipping pragmatic improvements quickly in an ambiguous, early-stage product area. * Bonus: experience building LLM-powered agents, evaluation frameworks, or tool-using automation for security or other high-stakes domains. * Bonus: experience at a security product company (AppSec, pentesting, cloud security, detection and response) or on an internal security platform at scale. ## Description Perplexity is building cybersecurity products where agents do the security work, not just assist with it. Our security team already runs agents on our own environment every day, across finding vulnerabilities, testing our defenses, securing our cloud, and responding to threats. Now we're turning that work into products for customers, and we expect those products to span application security, offensive testing, cloud security, detection and response, and areas we haven't picked yet., * Build security products from zero to one across domains such as application security, penetration testing and offensive security, cloud security, and detection and response. * Build agents that do real security work: review code and find vulnerabilities, test applications and infrastructure like an attacker, assess cloud configurations, and investigate threats, then validate findings and recommend or apply fixes. * Build the systems underneath: multi-tenant services, data pipelines, and secure execution environments that run against customer code, cloud accounts, and telemetry. * Build integrations with the tools customers already use: source control and CI/CD, cloud providers, identity providers, security tools, ticketing, and chat. * Ship the product surfaces customers use: APIs, dashboards, onboarding, and workflows that fit how security and engineering teams actually work. * Hold the product to the same standard we hold ourselves: strong tenant isolation, least privilege, safe handling of customer secrets and data, and tight controls on any agent that acts in a customer environment. * Define how we measure quality (finding accuracy, false positive rate, exploitability, time to fix, cost) and use it to drive improvements. * Work directly with design partners and customers, and help decide which security problems we should build products for next.