Principal Software Engineer - Agentic SOC at Huntress Labs | JobsWithPay

Wait…

Own the architecture of agentic investigation. You help define how signals move from detection into investigation, how investigation state is managed, how tools are designed and exposed to agents, and what a finished investigation contains: the verdict, the timeline, the scope, and the evidence behind every claim. When the team is stuck between options, you make the call, and the foundations you set are what others build on for years.
Build agents that investigate like a strong analyst. You work alongside our SOC and product researchers to learn how experienced analysts actually triage and investigate, then turn that into agent behavior: which questions to ask, which evidence to gather, when to dig deeper, and when to stop and hand off to a human.
Take toil off analysts’ plates. Beyond full investigations, you build LLM-powered pre-processing for the tools and data sources analysts rely on every day. It summarizes, correlates, and highlights what matters, so analysts spend their time on judgment instead of assembly.
Bring a security mindset to the agent itself. The agent reads attacker-influenced data, runs across thousands of customer tenants, and can take action in customer environments. You design as if someone is trying to manipulate it, because someone will. Trust boundaries, tenant isolation, and auditability are part of the architecture from the start.
Treat evaluation as a core part of the product. You define how we measure whether an investigation is correct, well-reasoned, and well-documented, and you make sure no prompt, model, or tool changes without evidence that it helps.
Decide with data what the system does on its own. Based on measured performance, you decide where it acts autonomously, where a person reviews its work, and how that changes over time. You also recognize when a problem doesn’t need an agent at all.
Build for production, not for demos. You design for reliability, latency, and cost at scale. The system keeps working when models are slow, wrong, unavailable, or quietly changed underneath you, and anyone can trace exactly why an investigation reached its conclusion or why an action was taken.
Augment analysts, don’t replace them. You design the handoff between agent and analyst so that when a case reaches a person, the agent’s work makes them faster and better informed. You consider how analysts’ work changes as agents take on more of it, and how we explain agent decisions to partners and customers in a way they can trust.
Prototype your way through hard problems. When the team hits something genuinely uncertain, you dig in first: derisk it, prove out the approach, then hand it off clearly.
Be the engineering face of the Agentic SOC. In conversations with SOC leadership, other engineering teams, product, and executives, you represent the team’s technical perspective clearly and credibly. You drive alignment on key decisions, carry context in both directions, and protect the team from unclear scope.
Balance technical rigor with pragmatism. You push back when a shortcut creates real risk, and you also push back on over-engineering when the goal is discovery. You have a bias for action and frequent feedback from analysts and customers, and you can explain your tradeoffs to engineers and non-engineers alike.
Raise the floor and the ceiling. Your technical leadership is measured by how the whole team performs, not just by what you personally ship. That shows up in thoughtful code review, pairing on problems others are stuck on, and creating leverage through better patterns, tooling, and shared understanding. You partner with the engineering manager on team health, give direct feedback, and model the judgment and accountability you want the team to have.