Job Description

WHAT YOU'LL DO

Braze is a modern, cloud-first SaaS company running on cloud-native infrastructure across AWS and GCP. We're looking for a Cloud Security Engineer to join our Security Engineering function - a hands-on role focused on keeping our security operations running well day to day. You'll respond to incidents, review changes and access for security risk, operate the security tooling that protects our environment (endpoint/EDR, SIEM, cloud posture, and vulnerability scanners), manage identity and access, and drive vulnerabilities to remediation.

This is an individual-contributor role that works within priorities set by senior members of the team. You don't need to have set security strategy or led a team - but you should operate tools with real judgment (knowing a genuine finding from noise, and why it matters), be reliable at driving issues to closure, and want to grow deeper in cloud security. It sits one level below our Senior Cloud Security Engineer.

Key job responsibilities:

1) Incident response & investigations:

• Respond to security alerts and events - triage, contain, and help investigate - with support from senior engineers on higher-severity incidents
• Follow and help improve our incident-response playbooks, and capture what you learn so the next response goes faster
• Pull the right data (cloud logs, endpoint telemetry) to reconstruct what happened and support the response

2) Security reviews & IAM:

• Review changes, designs, and cloud configurations for security issues, and give practical, specific feedback to the teams making them
• Operate and improve identity and access across AWS and GCP: handle access requests, run least-privilege reviews, and keep access hygiene high
• Reason about IAM policies and permissions - spotting risky or over-broad access and proposing tighter alternatives

3) Operate the security stack:

• Run and tune our security tooling day to day - CrowdStrike (EDR/CSPM), SIEM, cloud-native security services, and vulnerability scanners such as Tenable
• Triage the alerts these tools produce: separate real signal from noise, tune out false positives, and escalate what matters
• Keep tooling healthy - coverage, agent deployment, integrations, and configuration
• Write small scripts (Python) to automate repetitive work and reduce manual toil

4) Vulnerability management & remediation:

• Run vulnerability scanning across cloud assets, and triage and prioritize findings by real risk, not just severity score
• Drive remediation to closure: partner with Infrastructure, SRE, and Product Engineering to get fixes shipped, and track them until they're done
• Spot recurring issues and suggest the guardrail or config change that stops them coming back

WHO YOU ARE

You're a hands-on engineer who's curious about how attacks and cloud systems work - not someone who just clicks through consoles. You operate security tools with judgment: you can tell a real detection from a false positive, explain why a permission or misconfiguration is risky, and decide what deserves attention now. You're reliable at chasing an issue all the way to closure, and you communicate clearly and without friction with the teams you're asking to fix things. You want to grow into deeper cloud security work, and you learn quickly. Above all, you can walk someone through the messy middle - what you tried, what broke, and what you'd do differently.

1) WHAT WE'RE SCREENING FOR:

You should be able to reason about the areas below from real experience - not just recite tools you've touched. We go deep on the "why" and the "what would you do if," and we'd rather hear about something that went sideways than a tidy success:

• Incident response - how you triage an alert: what you check first, in what order, and when you pull in someone senior
• Endpoint / EDR - a real detection versus a false positive, and how you told them apart or tuned it out
• IAM - how you reason about least privilege, and how you'd handle an over-broad access request
• Vulnerability remediation - how you prioritize findings, and how you actually get another team to fix them
• Security reviews - what you look for when reviewing a change, config, or access request
• Automation - something small you scripted to cut out manual work

2) THE FEW HARD PREREQUISITES

The genuinely pass/fail requirements:

• ~3+ years in security operations, cloud, or infrastructure, with hands-on time operating security tooling (EDR, SIEM, and/or vulnerability scanners)
• Working knowledge of AWS, especially IAM; some GCP and container/cloud-workload exposure is a plus
• You can script in Python to automate small tasks — not just drive tools through their UI
• You can explain not just what a tool flagged, but why it matters

Backgrounds we welcome: this is a role you can grow in, so we're glad to hear from strong SRE, infrastructure, or DevOps engineers moving into security, and from SOC or security analysts going cloud-native - not only people with a linear cloud-security resume.

3) WHAT MAKES A CANDIDATE STAND OUT

We weight depth and curiosity relative to your experience over any credential:

• A time you chased a root cause further than you strictly had to - and what you found
• Something tedious you automated because it was worth doing, even if no one asked
• You can explain a cloud attack path, or an incident you were part of, clearly and honestly - including what you'd do differently
• A home lab, CTF, write-up, or side project that shows you dig into how things work
• Certs (e.g., AWS or security certifications) are fine signal, but we read them as a starting point

#LI-Hybrid