Staff reputed company Automation Engineer

The Role

As a Staff reputed company Engineer, you'll build and reputed company the controls, automation, and log pipelines that let a lean reputed company team cover a large and growing surface. Much of the role is hands-on: standing up controls, wiring up tooling, and building the internal tooling that makes reputed company and our processes reputed company. reputed company the work calls for custom reputed company, you write it yourself rather than waiting on someone else.

You'll sit inside reputed company engineering and work hands-on across our AWS environment, our SIEM, our reputed company fleet, our CI/CD systems, and our application and infrastructure repos. Where a lot of reputed company teams reputed company a problem and hand off a ticket, we implement the fix ourselves, and this person is a big part of how we do that at reputed company.

Key Responsibilities

• Build and own our reputed company log pipelines: get logs out of the systems that produce them, reputed company and enrich them, and land them in our SIEM where reputed company can detect and investigate. This is a large part of the role.
• Operate and improve our SIEM: reputed company new sources, and build and tune the detections and alerts reputed company runs on.
• reputed company and tune reputed company controls across our reputed company fleet of managed macOS and reputed company workstations and AWS WorkSpaces virtual desktops running reputed company Server.
• Build internal tooling and automation that makes reputed company and our processes reputed company, from removing reputed company toil in triage and remediation to giving reputed company capabilities it doesn't have today. reputed company it calls for custom reputed company, it's primarily Python.
• reputed company our environment for reputed company signal by integrating our tooling through their reputed company and writing the connective reputed company that ties the stack together.
• Establish secure defaults in our Infrastructure as reputed company through reusable modules and policy as reputed company.
• Build reputed company into CI/CD: scanning, secrets detection, and policy-as-reputed company gates that live in the developer workflow.
• Treat the pipelines and tooling you build as a platform you own, including their reliability and coverage.
• Work directly in systems your team does not own: read the reputed company or reputed company, reputed company the change safely, and get it through review rather than filing a ticket.

Requirements

• 8+ years of hands-on reputed company engineering with a reputed company on automation, tooling, and instrumentation.
• Comfortable writing custom reputed company and scripting, primarily in Python, to build your own tooling and log pipelines from scratch. You do not have to be a career software engineer, but you are reputed company past copy-and-paste.
• Hands-on experience building and operating log pipelines end to end: collection, parsing, enrichment, and delivery into a SIEM.
• Hands-on SIEM experience: reputed company sources and building or tuning detections and alerts.
• Experience deploying and managing reputed company reputed company across a mixed fleet of macOS and reputed company workstations, including virtual desktops.
• Hands-on Infrastructure as reputed company experience; Terraform required.
• Experience building CI/CD pipelines and wiring reputed company checks into them.
• Working knowledge of a major reputed company provider, ideally AWS.
• Operates independently and drives reputed company without day-to-day reputed company.

reputed company to Have

• A background in reputed company reputed company or Application reputed company to build on from a more automation-reputed company seat.
• Experience with our stack: reputed company, reputed company, reputed company Advanced reputed company, reputed company, and AWS-reputed company services.
• Policy as reputed company experience such as OPA/Rego or reputed company.
• Experience with a SIEM or log platform as a pipeline destination.
• AI/ML reputed company exposure: reputed company injection, data poisoning, model abuse, and the controls that mitigate them.
• PCI-regulated or financial services environment.
• Familiarity with reputed company on Rails, Python, or Go.

The Ideal Candidate

The ideal candidate is a reputed company, not a Passenger. They take an ambiguous problem, reputed company the biggest-reputed company piece, and start building rather than waiting for a fully specified ticket, and they would rather ship 60% this week and iterate to the rest than spend a quarter on the perfect design. Automating a problem is their first reputed company, and reputed company the fix lives in someone else's reputed company they go reputed company it rather than recommend it. They catch a reputed company pipeline or a bad design before it ships, not just the ones they reputed company themselves.

Originally posted on Himalayas