Security Lead

The Role

Sunset handles internal enterprise data from collaboration tools, documents, files, and business systems, then transforms it into de-identified datasets that remain useful. We also build software that can retrieve information, guide workflows, and take carefully bounded actions. Security is part of whether these products can exist, not a review added after they are built.

You will lead security across the company. The scope includes our products and cloud systems, the enterprise data we acquire and deliver, employee and contractor access, vendors, AI tool authority, incident readiness, and the human workflows through which consequential Dissolution work gets done. You will find the risks that could genuinely limit Sunset and turn them into technical, operational, and organizational controls that work in practice.

This is a hands-on individual-contributor role. You will write code, review architecture, test technical and human systems, lead exercises and incidents, and create secure defaults other teams can operate. You own the company-wide security program, but the people who run each product, system, and operation remain responsible for implementing and following its controls. You are not a one-person IT, legal, compliance, or operations department.
Problems You Might Own
Keep sensitive data inside explicit boundaries

Trace how customer data, credentials, derived artifacts, and delivery outputs move through SaaS applications, workers, data pipelines, review tools, logs, storage, and third parties. Build controls that make tenant isolation, access, retention, deletion, quarantine, and delivery decisions enforceable and auditable rather than dependent on convention.
Give people and AI systems only the authority they need

Design identity, authorization, and credential systems for employees, contractors, customers, services, and AI-assisted workflows. You might build just-in-time access, scoped tool contracts, approval boundaries, safe execution environments, or protections against prompt injection, confused-deputy behavior, and data exfiltration.
Secure how the company and its people operate

Design security into employee onboarding and offboarding, devices, accounts, contractors, vendors, support access, and sensitive human workflows. On the Dissolution side, that includes identity verification, approval boundaries, segregation of duties, document and credential handling, consequential actions, exception paths, and an audit trail that shows who did what and why.
Make the secure path the easiest path

Build paved roads that catch important problems early without creating a security queue. This could include high-signal code and architecture review, secrets and sensitive-data detection, reusable authorization patterns, dependency and cloud controls, release checks, incident tooling, or automated evidence that serves both engineers and customer trust.
What You'll Do

• Establish Sunset's company-wide security program, current attack surface, highest-consequence risks, and prioritized roadmap
• Threat-model product, data, AI, cloud, workforce, vendor, delivery, and human operational workflows, then stay involved through implementation and verification
• Build and improve controls for identity, authorization, tenancy, sensitive data, credentials, logging, secure execution, and customer delivery
• Define and verify workforce-security requirements for accounts, endpoints, onboarding, offboarding, contractors, vendors, training, and access reviews
• Work with Dissolution Operations to secure identity checks, approvals, segregation of duties, documents, money or asset-related actions, exceptions, and evidence of human decisions
• Find vulnerabilities through code review, architecture review, testing, production evidence, and attacker-minded investigation
• Lead the security side of incidents and exercises, including containment, recovery, learning, and durable remediation
• Create secure defaults, tooling, and review triggers that let product, machine learning, data, and platform teams move independently
• Maintain the security control framework and evidence for customer reviews and SOC 2, while keeping each control with an accountable operating owner
• Work with leadership on risk acceptance and with legal, compliance, and privacy partners on decisions outside the engineering function
• Use AI tools deeply for security analysis and engineering while treating generated findings, code, and conclusions as evidence to verify

What Success Looks Like

• Sunset's most consequential security risks are visible, owned, and being reduced in a deliberate order
• At least one high-risk technical or human-operational boundary is materially safer because of a control you designed, implemented with its owner, and verified
• Engineers adopt reusable security capabilities that reduce dependence on case-by-case review
• Employees, contractors, and operational teams have clear access, approval, escalation, and evidence requirements for consequential work
• Access, vulnerabilities, incidents, sensitive-data handling, vendor risk, and control evidence become easier to understand and act on
• Product and AI capabilities expand within explicit authority, isolation, monitoring, and recovery boundaries
• Customer trust evidence becomes faster to produce because it reflects real, current controls

You Might Thrive Here If

• You have at least three years of professional security or software engineering experience, including hands-on work securing production systems
• You are a strong software engineer with security as a core specialty, and you are comfortable building controls rather than only recommending them
• You have worked in a startup and can prioritize a few consequential risks across a much larger set of possible improvements
• You have owned security outcomes across several of product engineering, infrastructure, workforce, vendors, compliance, or business operations
• You can reason deeply about application security, identity and authorization, multi-tenant systems, cloud infrastructure, sensitive data, secrets, and incident response
• You think like both a builder and an attacker and can explain the actual abuse path, affected asset, likely impact, and useful mitigation
• You create low-friction defaults and clear decision boundaries instead of making Security the approval step for routine work
• You can secure human workflows with approvals, separation of duties, training, evidence, and monitoring without pretending every risk has a software-only solution
• You can communicate risk honestly to engineers, executives, customers, and auditors without using certainty you do not have
• You use modern AI engineering tools fluently and understand their authority, data, dependency, prompt-injection, and verification risks

This Role May Not Be for You If

• You want a compliance-only role centered on collecting evidence and administering frameworks
• You prefer producing findings or policies to implementing and verifying durable controls
• You treat every possible vulnerability as equally urgent or use Security as an unconditional veto without explaining the tradeoff
• You want a narrow specialty with established teams to own every adjacent system and decision
• You do not want AI tools to be part of your daily security and engineering workflow

Bonus

• Experience securing data-intensive, privacy-sensitive, or multi-tenant SaaS products
• Experience with information extraction, de-identification, data pipelines, secure delivery, or privacy-preserving systems
• Experience securing AI agents, tool-using systems, retrieval, model workflows, or MCP-style integrations
• Experience building least-privilege, just-in-time access, policy enforcement, secrets detection, data-loss prevention, or audit systems
• Experience with SOC 2, customer security reviews, vulnerability management, incident response, penetration testing, or security partners
• Experience as an early security hire who created leverage without centralizing all security work
• Experience securing operational, financial, legal, support, or other consequential human workflows