Principal Software Engineer (Golang)

Procore Technologies•Austin, TX

1d•$198,240 - $272,580•Hybrid

About The Position

We're looking for a Principal Software Engineer to join Procore's Directory team, part of our Product & Technology organization. The Directory team owns the user and company management experience within a construction workspace — the systems that manage collaborators at the company level and per-project level, as well as the account entities that each company operates within. This is foundational, high-leverage infrastructure: nearly every workflow in Procore touches the accounts, companies and people this team owns. In this Principal Software Engineer role, you'll set the technical direction for the Directory domain across our Go-based backend, built on a CQRS/Event Sourcing architecture, and our React/TypeScript frontend and legacy Ruby/Typescript systems. You'll partner with Product, Design, and adjacent platform teams to translate business needs around identity, access, and organizational structure into resilient, scalable systems. Use your deep experience in distributed backend systems, event-driven architecture, and modern frontend engineering to keep the Directory domain a dependable foundation for the rest of Procore. This position reports into the Sr. Engineering Manager, Directory and 2 days per week hybrid role in our Austin office. We’re looking for someone to join us immediately. This position requires US citizenship to work on FedRAMP-compliant projects. Candidates must be eligible to work on federal government projects requiring FedRAMP authorization.

Requirements

Bachelor's or Master's degree in Computer Science or a related field, or equivalent experience.
10+ years of experience architecting, scaling, and maintaining complex, distributed backend systems, ideally including production experience with CQRS and/or Event Sourcing patterns.
Strong proficiency in Go; experience designing services around domain-driven boundaries (accounts, organizations, users, permissions, or similar entities) is a strong plus.
Hands-on experience with GraphQL, including schema design and working within a federated gateway architecture.
Experience with event streaming systems such as Kafka, and familiarity with Change Data Capture (CDC) patterns for syncing data across services or off a legacy system.
Comfort with relational databases (e.g., PostgreSQL) and modern ORM patterns, and with building systems that must maintain strong data consistency guarantees.
Solid frontend experience with TypeScript and React (18+), and familiarity with modern data-fetching and routing patterns in single-page applications.
Strong communication skills, with a track record of influencing technical direction across multiple teams and stakeholders.
US citizenship to work on FedRAMP-compliant projects.
Eligibility to work on federal government projects requiring FedRAMP authorization.

Nice To Haves

AI-literate, leveraging generative tools and agentic workflows to move faster and work smarter.
Building the agentic future of construction.

Responsibilities

Own the technical strategy for the Directory domain, helping to drive architectural direction across our backend and frontend services and ensuring the domain remains a first-class citizen within Procore's broader Service-Oriented Architecture.
Guide the Ruby-to-Go migration, overseeing the Change Data Capture (CDC) pipeline that keeps our backend in sync with the legacy Ruby monolith, and help chart the path to eventually retiring that dependency.
Lead GraphQL API design and evolution, ensuring our schema is well-modeled, performant, and cleanly federated through Procore's GraphQL gateway.
Champion event-driven architecture, using Kafka-based streaming to ensure the Directory domain's events are reliable, well-observed, and easy for other teams to consume.
Establish operational excellence across both services — strong observability practices, solid automated test coverage (unit, integration, and end-to-end), and reliable, containerized deployment pipelines.
Collaborate across boundaries with Infrastructure, Security, and Product leadership, and with other domain teams consuming Directory's data and events, to keep the Directory domain a dependable foundation for the rest of Procore.
Support maintenance of existing Ruby on Rails and NestJS servce