ClickUp Senior Security Engineer, DFIR at ClickUp focuses on securing cloud infrastructure and building AI-powered security tooling. The role involves architecture reviews, detection and response, and enforcing least privilege access.
Responsibilities
Architecture, proposals and reviews. Act as an initial reviewer on infrastructure proposals and designs from engineering and non-engineering teams such as business systems and go-to-market. Write our own security proposals and review the changes that follow. Translate security requirements and agent findings into clear guidance for less-technical partners, and bring their needs back into our designs.
Agentic security tooling and agent infrastructure. Build, evaluate and maintain the agents behind our reviews, triage and investigations, and help run the sandboxed, observable infrastructure they operate on.
Detection, investigation and response. Lead cloud and infrastructure alerts and incidents through to resolution and root cause, working alongside AppSec and incident response on incidents that span both.
Identity, access and least privilege. Move people, CI and services toward least privilege and just-in-time access across our cloud organization and the tooling engineers use to reach production. Deliver fixes as secure building blocks that teams adopt by default.
Compute, network and pipeline security. Harden our container, serverless and virtual machine workloads, our network perimeter and our CI/CD pipelines, and add checks so each class of issue is caught automatically next time.
Continuous review and audit evidence. Move vulnerability, access and attack-surface reviews from point-in-time checks to continuous monitoring that also produces evidence for our infrastructure controls.
Qualification
5+ years in security engineeringDeep AWS IAM experienceAWS networking for securityExperience with CNAPPPythonClear written and verbal communication
Required
5+ years in security engineering, cloud infrastructure or SRE, with at least 2 years securing AWS at organization scale.
At least a year of agentic development experience: building agent skills and tools for real engineering work, and developing and maintaining the development harness they run in, from configuration and permissions to integrations, evaluations and cost controls. You can secure agents against prompt injection, over-privileged tools and unaudited actions, and explain how agents fall into the confused deputy problem and the lethal trifecta. You validate agent output against evidence and decide where human review is required.
Deep AWS IAM experience: IAM Identity Center or an equivalent SSO model, SCPs, permission boundaries, resource and key policies, cross-account trust, and the ability to prove a policy's effect with simulation rather than inference.
Production Kubernetes security on EKS or similar, covering RBAC, workload identity, network policy, admission control and container runtime hardening.
AWS networking for security: VPC design, endpoints and endpoint policies, network and DNS firewalls, egress control, and WAF.
Fluency with infrastructure as code such as Terraform, including reusable patterns, multi-environment rollouts and reading plans for security impact.
Experience with CNAPP, SIEM or runtime security tooling and the cloud detection sources around it, such as CloudTrail, GuardDuty and Access Analyzer.
Experience investigating cloud and infrastructure security events: correlating cloud audit, Kubernetes, identity and network logs to establish what happened, its blast radius and its root cause.
A track record of reviewing architecture and writing design proposals, guiding teams toward secure designs through conversation rather than mandate, mentoring others through reviews, and turning a review into a change another team is glad to make.
Python, Go or TypeScript for security automation.
Clear written and verbal communication, including explaining technical risk to non-technical partners. Most of our work with other teams is asynchronous, so much of the job is a well-evidenced finding, proposal or design note that another team can act on without a meeting.
Experience using AI agents in a SOC or other incident response workflows.
