Senior Site Reliability Engineer, SecOps

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs before responsibilities. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "Complete any additional tasks as they arise" maybe considered boilerplate? It's part of responsibilities but maybe keep? It's generic; but it's part of responsibilities list. Might keep but it's not specific. Might drop as filler? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." "Complete any additional tasks as they arise" is generic but not necessarily boilerplate; but could be considered filler. I'd keep it as part of responsibilities? Might be okay. We need sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list), Skills? The posting includes qualifications and also some skill-like items; but we can combine Qualifications and Skills? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have: About the role: first paragraph(s) describing CMT and mission. That's substantive. Responsibilities: bullet list after "Responsibilities:" - many items. Qualifications: after "Qualifications:" list. Skills: The qualifications list includes many skill items; but we could treat them as Skills section. However we already have Qualifications heading; maybe we split: Qualifications (education/experience) and Skills (technical). But the posting lumps them together. To follow instruction, we could create Qualifications for degree/experience, and Skills for technical proficiencies. But we need to avoid thin sections. Might be better to have one Qualifications section containing both education/experience and skills. The instruction says we can use Skills heading if there is real specific content. There is specific content about skills (AWS, coding, etc). So we could have both Qualifications and Skills sections. Pay: There's "Compensation and Benefits:" includes base salary range, equity, benefits, etc. So we need Pay section (salary range) and Benefits section (medical, etc). Also Schedule? There's "Flexible scheduling and work from home policy depending on role and responsibilities" and "Unlimited Paid Time Off", "Summer Fridays". That's schedule info. So we can include Schedule section. We must not include headings with filler like "commensurate with experience". We have specific salary range, benefits details. We need to output only HTML fragment, no /, no markdown fences. Structure:

About the role

... (intro paragraphs)

Responsibilities

• ...
...

Qualifications

• Bachelor's degree or equivalent years of experience and/or certification in a related field
• 4+ years of experience working in Site Reliability Engineering or Information Technology

Skills

• Write and review code to automate away problems within your team's domain
• Intermediate to expert experience deploying and maintaining AWS services such as EC2, ECS, EKS, SQS, Lambda, Dynamo, RDS/Aurora, S3, and IAM
• Intermediate to expert experience monitoring services and applications using tools such as CloudWatch Metrics, CloudWatch Logs, and Datadog, including defining and configuring alerts and SLO reports
• Intermediate to expert experience implementing and maintaining security controls and tooling in AWS, such as IAM, KMS, Security Hub, GuardDuty, Inspector, and Config
• Intermediate to expert coding skills in at least one programming language; we work primarily in Python
• Intermediate to expert experience using AI coding agents (Claude Code) daily for Terraform and Python development, log and finding investigation, and remediation authoring - with the judgment to verify output and keep AI-assisted changes under standard PR and approval controls
• Intermediate to expert experience using Infrastructure as Code platforms and CI/CD pipelines, specifically Terraform, to manage AWS infrastructure and services
• In-depth knowledge & experience with Linux operating systems (Amazon Linux, Ubuntu) on EC2 and Docker on ECS / EKS
• Experience partnering with security or engineering teams to implement and operationalize security requirements

Pay

The base salary range for this position is: $118,300 to $147,900. This range is specifically for Cambridge, MA.

Benefits

• Fair and competitive salary based on skills and experience, and annual performance bonus
• Equity may be awarded in the form of Restricted Stock Units (RSUs)
• Medical, Dental, Vision and Life Insurance, matching 401k, short-term & long-term disability and parental leave
• Unlimited Paid Time Off including vacation, sick days & public holidays
• Flexible scheduling and work from home policy depending on role and responsibilities
• Summer Fridays provide team members with half days to recharge
• Additional perks: work on a mission with real impact, join industry leader, recognized innovator, Great Place to Work Certified, etc.

But we need to avoid duplication: The "Compensation and Benefits:" paragraph includes many items; we already captured salary in Pay, benefits in Benefits. Also we have "Additional Perks:" list; we could include those in Benefits as well. We must not include boilerplate like EEO statement, commitment to diversity, etc. Also remove "About Cambridge Mobile Telematics:" etc? That's about company description; maybe part of About the role? The intro already includes mission description; the later "About Cambridge Mobile Telematics:" is duplicate. We should drop duplicated lines. We need to preserve all substantive information; but we can drop duplicated content. The intro includes: "CMT has helped protect over 65 million drivers and prevent over 126,000 crashes worldwide. We build AI to solve some of the most difficult challenges in mobility — understanding and reducing risk, detecting crashes, and getting people life-saving help. The problems are hard. The impact is real. No matter your role, your work will matter at CMT." That's good. Later there is "About Cambridge Mobile Telematics: Cambridge Mobile Telematics (CMT) is the world's largest telematics and AI company for safer mobility..." That's more detail about company; could be considered substantive but maybe duplicate of earlier. However it's not duplicated exactly; it's additional info about offices, etc. Should we keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that info, but we need to place it somewhere. Could be part of About the role section as additional paragraphs. However we must avoid duplication; but it's not duplicate, it's extra. So we can include it. Thus About the role could have multiple paragraphs: first paragraph (mission), second paragraph (company details). We'll combine. We must not include "Commitment to Diversity and Inclusion:" etc. That's EEO boilerplate; remove. Also remove "To learn more, visit www.cmtelematics.com and follow us on Instagram @cmt.ai" maybe considered navigation? It's not boilerplate but could be considered contact info; but it's not required. Might be considered application instruction? It's not. But it's like a call to action; maybe we can drop as it's not substantive about job. Safer to remove. Also remove "CMT is headquartered in Cambridge, MA." Already covered. Now produce HTML. Check for any duplicated lines: Ensure we didn't repeat same bullet. Let's craft. About the role: two paragraphs. Paragraph1: "CMT is looking for a Senior Site Reliability Engineer, SecOps to help us change the world. CMT has helped protect over 65 million drivers and prevent over 126,000 crashes worldwide. We build AI to solve some of the most difficult challenges in mobility — understanding and reducing risk, detecting crashes, and getting people life-saving help. The problems are hard. The impact is real. No matter your role, your work will matter at CMT." Paragraph2: "Cambridge Mobile Telematics (CMT) is the world's largest telematics and AI company for safer mobility. Its mission is to make the world's roads and drivers safer. The company's AI-driven platform, DriveWell Fusion®, proactively identifies and reduces driving risk, leading to fewer crashes and injuries. To date, CMT's technology has helped prevent over 126,000 crashes worldwide. CMT enables partners to measure risk, detect crashes, provide life-saving assistance, and streamline claims. Headquartered in Cambridge, MA, CMT operates globally with offices in Budapest, Hungary; Chennai, India; Seattle, Washington; Tokyo, Japan; and Zagreb, Croatia." That seems good. Now Responsibilities: list each bullet from responsibilities section. Let's extract bullets: - Use independent judgment and discretion to implement security tooling and controls in AWS as defined by the Security Engineering team, including deployment, configuration, agent coverage, and ongoing tooling health - Implement IAM Roles and Policies, account-level guardrails, and secrets management in AWS in line with Security Engineering standards - Remediate vulnerability, cloud security posture, and compliance findings across the AWS estate, tracking work to the remediation SLAs defined by the Security Engineering team - Own the security telemetry pipeline — org-wide CloudTrail, GuardDuty, Security Hub, AWS Config, VPC Flow Logs, and application/audit logs — including coverage validation, retention and immutability requirements, routing into Lacework and Datadog, and managing ingest/retention cost - Implement and maintain preventive controls — SCPs/RCPs, permission boundaries, Config rules and conformance packs, IaC policy-as-code in CI, and secret scanning — including drift detection, auto-remediation, and a documented exception/waiver process with expiry - Implement network and data protection controls: security group and egress baselines, VPC segmentation, KMS key lifecycle and rotation, encryption-at-rest/in-transit standards, certificate lifecycle, and public-exposure prevention (S3 Block Public Access, IAM Access Analyzer external findings). - Codify everything as infrastructure-as-code using Terraform and CI/CD pipelines, enabling updates through Pull Requests with approval workflows, while also automating maintenance tasks to reduce toil - Provide secure-by-default Terraform modules and self-service paved paths so product teams inherit controls; consult on design reviews and threat models; act as the translation layer between Security Engineering standards and platform/application reality, feeding back where standards are impractical. - Participate in incident response for security events, contribute to blameless postmortems and systemic remediation, including participating in an on-call rotation - Complete any additional tasks as they arise We'll keep all. Qualifications: two bullets: - Bachelor's degree or equivalent years of experience and/or certification in a related field - 4+ years of experience working in Site Reliability Engineering or Information Technology Skills: list as earlier. Pay: one paragraph. Benefits: list items. We need to avoid including "Compensation and Benefits:" heading; we already have Pay and Benefits sections. Benefits list: from "Compensation and Benefits:" we have: - Fair and competitive salary based on skills and experience, and annual performance bonus (but salary already in Pay; maybe we can omit duplicate) - Equity may be awarded in the form of Restricted