Principal Software Engineer

RegScale is a continuous controls monitoring platform that helps organizations automate and scale their security, risk, and compliance programs. The Principal Software Engineer will own systems and capabilities, drive technical initiatives, and provide leadership across engineering teams to ensure high-quality software delivery.

Responsibilities:

• Be a key member of the engineering leadership team, providing technical thought leadership that informs architecture, delivery, and product decisions across the organization
• Own systems and capabilities end to end, not just features, with accountability for the technical direction, quality, and long-term health of what you lead
• Identify architectural problems, scalability risks, and engineering patterns that need to change, and drive resolution with concrete proposals and cross team alignment
• Design reusable, well-reasoned platform primitives and frameworks that reduce duplication and meaningfully accelerate the teams that consume them
• Deliver across the full stack including frontend (Angular), backend (.NET, C#, Python), and data layer (PostgreSQL, SQL Server), with the depth to make sound architectural decisions at every layer
• Lead technical initiatives across squad and functional boundaries, building alignment without direct authority through strong communication, credibility, and sound engineering judgment
• Set engineering standards and patterns that others adopt in API design, data modeling, testing approach, and code quality, in partnership with the Architecture function
• Proactively identify technical risk and delivery concerns weeks ahead of when they become problems, with proposed mitigations that protect business commitments
• Develop the technical capability of the engineers around you through design reviews, mentorship, and active knowledge transfer. Measure part of your success by how much more effectively others operate because of your involvement
• Communicate complex technical decisions and tradeoffs clearly to engineering leadership, product, and executive stakeholders

Requirements:

• 12 or more years of professional software engineering experience with a portfolio of complex, cross cutting technical contributions that demonstrate system level thinking
• Demonstrated ability to own systems or capabilities, not just features, with impact that extends across multiple teams or functional areas
• Recognized as a technical authority who sets patterns others follow, drives adoption of standards, and shapes engineering culture through example and credibility
• Track record of leading technical initiatives across organizational boundaries without direct authority, building consensus, navigating competing priorities, and delivering outcomes
• Strong engineering instincts for tradeoffs including speed vs. sustainability, pragmatism vs. standards, and incremental delivery vs. architectural integrity
• Experience proactively identifying systemic problems and proposing architectural solutions before they become crises, with concrete mitigation options that protect delivery commitments
• Exceptional written and verbal communication skills, able to articulate technical strategy and tradeoffs to engineering leadership, product, and executive audiences
• Experience in regulated industries or with compliance, security, or risk management platforms. GRC, FedRAMP, NIST, or OSCAL familiarity is a meaningful advantage
• Background in enterprise SaaS companies navigating the transition from startup to scale, with direct experience managing technical debt, architectural evolution, and team capability development during that transition
• Experience building or governing platform primitives including SDKs, CLIs, internal APIs, and shared services, with an understanding of what makes them reliable, adoptable, and maintainable across teams
• Familiarity with AI and ML integration in production engineering contexts, particularly building reliable, observable, enterprise grade AI capabilities rather than proof of concept work
• Cloud native experience in Azure or comparable platforms (AWS, GCP) with understanding of infrastructure constraints, deployment models, and cost implications at scale
• Hands on experience with observability, performance profiling, and diagnosing complex production issues at enterprise scale