Principal Software Engineer, SOC Experience (Ruby/Rails)

Responsibilities:

• 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.