Principal Software Engineer, SOC Experience (Ruby/Rails)

Cybercrime is growing, and more businesses are getting hit by threats that used to target only the biggest organizations. That pushes defenders like us to operate at the highest level, and it deepens our need for good people who want to make a meaningful impact.

Founded in 2015 by former NSA cyber operators, Huntress is a remote-first team working to make enterprise-grade cybersecurity accessible to businesses of all sizes. We work closely with security teams and service providers protecting complex environments, often without the time or headcount to handle it all. That’s why we build our technology in-house and back it with a 24/7 human-led Security Operations Center (SOC). As a result, our platform is never disconnected from the experts who manage it, ensuring our customers' protection.

Huntress now secures more than 5M endpoints and 11M identities worldwide. Those numbers keep growing because more businesses rely on us to help carry the load and operate with more confidence. Every day, you can see that commitment in how we stand with our customers and how we show up for each other.

The Huntress team seeks a Principal Software Engineer to join our Security Operations Center (SOC) Experience team. This team builds the systems that enable Huntress’ human-led SOC to operate at scale across investigative workflows, protecting our customers and our partners’ customers. The team’s work is about building the operational backbone for modern SOC execution: live triage and investigation experiences, workflow-driven automation, agentic investigation capabilities, remediation actions, and customer-facing reporting. The team also owns the steady stream of operational work as new detections, products, and capabilities come online across the Huntress platform.  Your contributions will help Huntress improve analyst efficiency, reduce toil, and drive customer outcomes as we scale protection for the 99%.

As a Principal Software Engineer at Huntress, you will provide technical leadership across this space by shaping architecture, decomposing ambiguous problems, and driving execution on the highest-leverage work. You will partner closely with engineering, product, UX, and SOC stakeholders to turn operational pain points into reliable, auditable, and scalable systems. This includes empowering and enabling analyst investigation workflow, establishing behavior and safety rails for assisted and automated actions, improving observability and operational metrics, and raising the bar for reliability, maintainability, and delivery quality across the team. You’ll be expected to go deep in the code when needed, mentor senior engineers, and help the organization make pragmatic technical decisions that improve analyst effectiveness, partner outcomes, and Huntress’s long-term ability to innovate in the industry with confidence.

We make full use of AI coding tools to enable you to accelerate your development. We don’t cap token usage. We expect you to use AI and all tools responsibly.

• →Be the engineering face of the team and a trusted technical leader across the department. In cross-functional conversations with other engineering teams, product, or leadership, you represent the team's technical perspective clearly and credibly. You drive alignment on key decisions. You bring context back in both directions and protect the team from unclear scope.
• →Balance technical rigor with pragmatism. You push back when taking a shortcut creates real risk, but you also push back against over-engineering when the goal is discovery or prototyping. You have a bias for action and for getting frequent customer feedback. You make sound tradeoff decisions across requirements, reliability, performance, and cost. You can articulate the trade-offs either way to engineers and non-engineers alike. 
• →Keep the team moving. You know the difference between decisions worth deliberating and decisions worth making quickly. You break down ambiguous requirements into work that can actually be executed, surface and clear blockers before they become delays, and hold the line between planning and shipping.
• →Shape the team as well as the code. You notice interpersonal friction and work with the engineering manager to address it. You give direct feedback, help engineers grow into solving harder problems, and model the kind of judgment and accountability you want the team to have. The team functions better because you're a part of it.
• →Raise the floor and the ceiling. The measure of your technical leadership is how the whole team performs, not just what you personally ship. That means code review with genuine intent, pairing on problems others are stuck on, and creating leverage through better patterns, tooling, and shared understanding.
• →Shape how we build AI into the product. Design and ship agentic investigation capabilities that help analysts triage and report faster, with the accuracy, safety, and auditability that is required in a security environment.
• →Prototype your way through hard problems. When the team hits something genuinely uncertain, you dig in first. Derisk, prove out the approach, then hand it off clearly.
• →Own the team's technical architecture and influence architectural direction across the system. Define long-term technical strategy, how the system evolves (e.g., data models, interfaces, contracts), and make the calls when the team is stuck between options. Your decisions create the foundation others build on for the foreseeable future.

• 15+ years of experience developing complex software products
• 8+ years of programming in Ruby on Rails
• BS or MS in Computer Science or Engineering, or equivalent experience
• Experience with AWS, Azure, or other public cloud environments
• Experience with relational databases such as Postgres and with in-memory datastores such as Redis
• Experience building production systems with LLMs, using agents, tools, evaluation, guardrails, and common, proven patterns
• Experience with AI coding tools, such as Claude Code
• Deep backend expertise and a track record of scaling production systems
• Solid frontend fundamentals (today’s stack is Hotwire, Turbo, and Stimulus), but able to reason outside that box
• Proven ability to build and maintain large, highly parallel systems and design for concurrency, throughput, and correctness under load