About the role
- As Senior Security Engineer, you’ll report to the VP of Engineering and work closely with the CTO and DevOps as part of Roofr’s security guild. You’ll contribute directly to improving Roofr’s security posture — sharpening what’s already in place and driving it forward as the company scales. You’ll own the tools and processes that detect and stop threats, partner with engineering on secure-by-design practices, and act as the front-line responder when something goes wrong
- Own design and hardening of security infrastructure across cloud environments — network segmentation, firewalls, IDS/IPS, VPNs, WAF, and endpoint detection and response (EDR)
- Lead vulnerability management end to end: run assessments and authenticated scans, triage and prioritize by exploitability and blast radius, and drive remediation SLAs with engineering
- Build and tune detection content (SIEM/SOAR rules, alerting logic) against real attack techniques — not just default vendor signatures
- Act as incident commander for security incidents: contain, eradicate, run forensics, and write the post-incident review
- Threat-model new features and infrastructure changes before they ship — catch design-level risk, not just implementation bugs
- Own IAM hygiene and cloud security posture (least privilege, key/secret management, network boundaries) across production AWS accounts
- Write, enforce, and maintain security policies and standards — own them as living controls, not documents that sit in a drive
- Own Roofr’s compliance program end to end: map controls to NIST CSF 2.0, SOC 2, and CCPA/CPRA, run the audits, close the gaps, and keep evidence current between them
- Run tabletop exercises and incident playbook drills
- Push secure-by-design practices into engineering workflows — threat modeling in design review, security requirements in the SDLC, not a gate bolted on at the end
Benefits
- Medical, dental and vision insurance premiums for employees and their dependents
- Flexible time off
- Generous Parental Leave policy
- 1st week of employment is mandatory PTO! Start your journey with Roofr by decompressing and recharging - we will see you in week 2!
- Company wide paid shutdown for the week between Christmas and New Years
- We host 2 retreats per year and great team building activities
- 1 Friday off per month (we call those our laundry days!)
- Weekly Friday paydays!
- Ample learning and development opportunities to continue growing your career
- Remote first culture
- Home office setup stipend
- Bachelor’s degree in computer science, IT, cybersecurity, or equivalent hands-on experience
- 5-8+ years in security engineering, incident response, or related infrastructure roles, including time as the primary or senior responder on real incidents
- Certifications are a strong plus — CISSP, OSCP, GCIH, or CEH
- Strong software engineer at heart — comfortable reading and writing real application code, not just scripts, so you can dig into the codebase directly instead of filing a ticket and waiting
- Real incident response experience — triage, containment, forensics, root cause, not just theory from a course
- Hands-on cloud security in AWS — IAM policy design, VPC architecture, KMS/secrets management, CloudTrail/GuardDuty or equivalent
- Working knowledge of SIEM/SOAR tooling, writing detection logic (Python/Bash), and building your own tooling when nothing off-the-shelf fits
- Fluent in compliance frameworks — NIST CSF 2.0, SOC 2, and CCPA/CPRA — and translating controls into policy people actually follow
- Deep network security fundamentals — firewalls, VPNs, routing/segmentation, network boundaries, TLS, DNS, and how attackers actually abuse them
- Experience using AI/LLM tooling for threat intelligence — alert triage, detection summarization, or hunting workflows — not required, but a plus for a team building modern security practice from scratch
- Familiarity with GDPR — a plus as Roofr’s customer base grows internationally
- Experience with PHP/Laravel — a plus for digging into Roofr’s own codebase directly, not required
- Comfortable around Postgres — helpful, not required