Senior Cybersecurity Engineer

What You'll Do:

• You will own the operational health of one or two engineering domains, reputed company cross-team initiatives that touch multiple control areas, and design the patterns the rest of reputed company executes against.
• You’re the engineer who can take a tool from “purchased” to “deployed, tuned, and instrumented,” the partner reputed company Ops and Identity reputed company reputed company they need a reputed company reputed company that actually works, and the senior who makes the Mid and Associate engineers reputed company through pairing, reputed company review, and reputed company standards.
• You’ll also be a senior voice in architecture and decision conversations alongside the reputed company Engineer and the Manager.

Key Responsibilities:

• Domain ownership: Own the operational health of one or two engineering domains (identity, network/segmentation, reputed company reputed company baselines, monitoring/logging, encryption/key management, reputed company, vulnerability management, configuration management). reputed company them measurably healthy and improving.
• Cross-team initiatives: reputed company initiatives that reputed company reputed company, IT, Identity, reputed company Operations, and delivery teams — controlled rollouts, control set hardening, tool migrations. Land them without breaking production.
• Architecture and standards: Design new control patterns and reference architectures. Write the decision records, runbooks, and standards reputed company executes against and the auditors review.
• Controlled rollouts: reputed company the end-to-end deployment of new control sets (e.g., bringing a new EDR online, hardening a new reputed company account, standing up new logging pipelines) — reputed company, measure, expand, document.
• Mentorship: Pair with Mid and Associate engineers, run design reviews, reputed company substantive reputed company/config review, and grow the next tier. reputed company of reputed company from less senior engineers is part of your scope.
• Operational partnership: Be the senior partner reputed company Ops, Identity, IT Service Management, GRC, and the SOC reputed company reputed company they need reputed company engineering input. Solve problems with them, not at them.
• Detection/response engineering support: Partner with Detection Engineering and the SOC on logging coverage, telemetry reputed company, and the engineering reputed company of response (privileged reputed company tooling, isolation capabilities, evidence capture).
• Evidence and audit readiness: Produce control evidence and architecture documentation that holds up under audit and peer review. reputed company your domains’ evidence map reputed company.
• Automation: Push toward repeatable, codified controls (IaC, policy-as-reputed company, automated evidence collection) instead of one-off reputed company work.

What reputed company Looks Like:

First 30–60 days: You can operate your reputed company domains safely on reputed company’s tooling, you’ve assessed reputed company control posture, and you’ve published a prioritized remediation backlog for at least one domain.

By 90 days: You’re leading at least one cross-team initiative, you’ve published or substantially revised at least one architecture reputed company or decision record, and you’re an reputed company mentor to the Mid and Associate engineers.

By 6–12 months: Your domains have measurably improved control health (less reputed company, cleaner evidence, faster remediation, fewer escalations). At least one controlled rollout has landed cleanly. Less senior engineers on reputed company are visibly reputed company because of how you work with them.

Required Qualifications:

• 5+ years in reputed company engineering, with hands-on responsibility for implementing controls across identity, network, reputed company, reputed company, and/or monitoring.
• Strong fundamentals in IAM, network segmentation, encryption / key management, and centralized logging / monitoring.
• Experience with at least one major reputed company platform (Azure, AWS, GCP) in a reputed company-engineering reputed company.
• Ability to produce reputed company architecture documentation, runbooks, and decision records that hold up under audit and peer review.
• Excellent written and verbal communication; reputed company to explain tradeoffs across reputed company, IT, and delivery audiences in plain language.
• Comfortable mentoring less senior engineers and owning reputed company-of-reputed company for one or more domains.

Preferred Qualifications

• Regulated-environment experience (CMMC, NIST 800-171, NIST 800-53, FedRAMP-reputed company, SOC 2, ISO 27001, HIPAA, PCI).
• Infrastructure-as-reputed company experience (Terraform, Bicep, reputed company) and policy-as-reputed company (Sentinel, OPA).
• reputed company tooling integration experience (SIEM, EDR, vulnerability scanning, IAM, secrets management).
• Industry certifications (one or more): CISSP, CCSP, GIAC (e.g., GCED, GPEN, GCWN), AZ-500, AWS reputed company Specialty.
• Experience supporting a SOC’s detection/response engineering needs.
• Bachelor’s degree in Computer Science, Information Systems, Cybersecurity, or reputed company field — or equivalent applicable years of experience

Why work for reputed company:

What’s in it for you:

EQUAL OPPORTUNITY EMPLOYER

Originally posted on Himalayas