Tracking 100,000+ career sites

Senior Cybersecurity Jobs

Built from a 20M+ job database and updated hourly, this list surfaces senior cybersecurity roles across security engineering, architecture, operations, consulting, and cyber risk.

Titles can include senior security engineer, cybersecurity architect, cloud or application security engineer, detection engineer, incident responder, security operations lead, security consultant, governance or cyber-risk manager, and security engineering director. The underlying work spans preventive controls, threat detection, incident response, architecture reviews, vulnerability management, identity, compliance, and security strategy. Team placement can shape the job: some postings describe close work with engineering, while others center on operations, risk, assurance, or client advice. Advisory positions may add deliverables and recommendations for several stakeholder groups. Seniority is reflected in authority over risk decisions, ownership during incidents, scope of systems protected, influence on architecture, and responsibility for mentoring or managing teams. Separate technical specialist and principal roles from governance or people-leadership positions, even when their titles use similar security language.

Classify the function as engineering, operations, incident response, architecture, advisory work, assurance, or governance. That choice determines whether cloud and security tools, threat expertise, certifications, policy knowledge, or stakeholder influence should carry the most weight. Identify the assets and users being protected, the decisions the role can make, and who accepts residual risk. Next verify clearance requirements, on-call duties, travel, management scope, and reporting line in the original posting. If technical scenarios, architecture reviews, incident walkthroughs, or risk discussions are named, prepare evidence for those steps rather than assuming a universal security interview. Company, location, industry, compensation, and sponsorship filters can narrow the set. Consider pay with call burden, onsite constraints, team maturity, and authority to change systems; confirm authorization and residency language at the source.

The list is free to browse and filter. A free account is optional for saved cybersecurity roles, application tracking, and Copilot. A short note on security domain and operating responsibility makes later comparisons clearer.

5,001
roles in this list
1,438
added this week
Featuring roles at
Canva
Netflix
Notion
Visa
Capital One
& 100K+ more
Got questions?

Explore our FAQ section to learn more.

This list covers senior, staff, and principal cybersecurity roles in security engineering, application and cloud security, security operations, incident response, threat intelligence, penetration testing, vulnerability management, and security architecture.

Show ownership of security programs, controls, investigations, architecture, or remediation work. Quantify reduced exposure, faster detection and response, improved control coverage, or successful audits where possible.

Requirements vary. Certifications can support experience in security architecture, cloud security, offensive security, governance, or incident response, but employers usually prioritize evidence that you handled real systems and meaningful risk.

Expect technical scenarios, architecture or threat-model discussions, incident retrospectives, control design questions, and examples of influencing engineering or business partners. Some roles include hands-on exercises.

Security engineering focuses on building secure systems, tooling, controls, and automation. Security operations focuses on monitoring, detection, investigation, response, and continuous improvement of operational defenses.

Not necessarily. Staff and principal roles are often senior individual-contributor positions with broad technical influence, while management roles usually include team leadership, hiring, and performance responsibilities.

Ask which systems, threat models, compliance obligations, and business risks the role owns. Clarify decision authority, on-call expectations, incident frequency, executive exposure, and available engineering resources.

Compare security maturity, leadership support, tooling, staffing, on-call load, access to engineering teams, incident history, regulatory exposure, and whether the role has authority proportional to its accountability.