Principal Software Engineer

The Role

Reg Scale is a continuous controls monitoring (CCM) platform that helps organizations automate and scale their security, risk, and compliance programs. We are at an inflection point, transitioning from startup execution to a disciplined, enterprise‑ready engineering organization, and we are building the team that will take us there. This is a meaningful problem domain: the work you build directly helps organizations manage risk, meet regulatory requirements, and operate more securely at scale.

Principal Software Engineers at Reg Scale operate at the intersection of deep technical craft and organizational impact. A Principal Engineer at Reg Scale owns a system, a capability, an architectural boundary, or a set of patterns that other engineers build on top of. Your work has reach beyond your squad. The decisions you make and the standards you set shape how the broader engineering organization builds software.

You will work across customer‑facing GRC capabilities and the platform primitives that underpin them including APIs, data services, SDK, scalability, and performance. You are expected to identify problems before they become crises, propose solutions that others can execute, and drive technical initiatives across team boundaries without relying on direct authority. You build consensus through credibility, clarity, and demonstrated judgment.

This role is for an engineer who is energized by technical complexity, has the communication skills to navigate organizational complexity, and measures their success not just by what they build but by the capability and confidence they leave behind in the teams around them.

• 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 (Postgre
  
  SQL, 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 trade‑offs clearly to engineering leadership, product, and executive stakeholders.

• 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 trade‑offs including speed vs. sustainability, pragmatism vs. standards, and…