Descripción de la oferta
HappyRobot is the infrastructure for enterprises to build and orchestrate AI workforces. Our AI workers don't just communicate through voice and email - they make decisions, take action, and run operations autonomously across entire enterprise systems. Born in Y Combinator (S23) and backed by a16z, Base10, Prysm Capital and Eurazeo with over $150M raised, we power critical operations for global enterprises worldwide.Our platform is battle-tested in the most demanding environments, where AI has real consequences. We started in logistics, built our own voice stack, models, and orchestration layer from the ground up, and are now bringing that infrastructure to every enterprise that runs the real economy. Learn more about our vision in our manifesto.Role OverviewWe are looking for a SOC Analyst to join our team. You will be the consistent, accountable owner of alert triage during coverage hours — bringing the speed, rigor, and communication discipline that transforms alert handling from a best-effort scramble into a reliable, measurable function.This is not a detection engineering or research role. Your deepest strength is triage: prioritizing fast, distinguishing signal from noise, and escalating with the context that lets engineers act immediately rather than re-investigate from scratch. That said, you operate with a continuous improvement mindset — feeding a structured tuning loop with the SOC Engineer and proposing runbook fixes when the playbook doesn't match reality.What You'll DoAlert Triage Own the queue during coverage hours. Prioritize and disposition alerts accurately and fast — high-severity alerts acknowledged within 15 minutes, all alerts dispositioned within SLA. Know the difference between a true positive and noise, and act accordingly without waiting to be told.Log & Threat Analysis Pivot across cloud, identity, and endpoint log sources to build a clear timeline when an alert warrants deeper investigation. Use MITRE ATT&CK as a reference frame to understand what you're looking at and what it means in context.Incident Escalation & Communication Escalate incidents with complete, actionable context — severity reasoning, timeline, affected systems, and recommended next steps. Write clearly in English. Engineers receiving your escalations should be able to act without asking follow-up questions.Runbook Discipline & Improvement Follow runbooks rigorously. When a runbook falls short — wrong steps, missing cases, outdated assumptions — flag it and propose a fix. Runbooks improve because analysts use them critically, not just obediently.Tuning Feedback Loop Run a weekly feedback cycle with the SOC Engineer. Report false positives, patterns in noise, and cases where detection logic needs adjustment. Improve signal quality over time rather than just processing the same noise on repeat.Audit Readiness Keep monitoring and response evidence current and organized for SOC 2, ISO 27001, and customer incident response commitments. Triage work that isn't documented doesn't exist for audit purposes — make sure yours does.Must Have2–3 years as a SOC analyst or in a blue team / detection and response role.Hands‑on alert triage experience with a SIEM and an EDR — investigation, disposition, and escalation.Log analysis across cloud, identity, and endpoint sources.Working knowledge of MITRE ATT&CK and common attack patterns.Clear written incident notes and escalations in English (B2+).Comfortable operating on a coverage-hours rotation.Nice to HaveCloud console familiarity with AWS, Azure, or GCP.
