Principal Software Engineer - Infrastructure Platform
Procore
Listing collected from Procore's career site. NextChapter is independent of Procore.
Austin, TX · $198k–$273k a year · Posted November 14, 2026
Will your résumé get you an interview here?
Drop your résumé and see in seconds how well it matches what Procore asks for. Free, no account needed.
Just laid off? Start here: a plan for the first weeks
See every open role at Procore
More in Texas job market · Principal Software Engineer jobs in Texas (16) · All Principal Software Engineer jobs (301) · Construction & Real Estate · Engineering jobs
More roles at Procore
- Sales Development Representative - DroneDeploy
- SMB Account Manager · Austin, TX
- Director, MarTech & AI Ops · Austin, TX
- Director, M&A Integrations (Remote)
- Staff Forward Deployment Engineer · Austin, TX
- Enterprise Account Executive, DroneDeploy · Austin, TX
Similar jobs
- Software Engineer - E2 · Sikorsky · Fort Worth, TX
- Embedded Software Engineer Asc · Lockheed Martin · Grand Prairie, TX
- Systems Integration/Test Engineer Stf - E4 · Sikorsky · Grand Prairie, TX
- Lead DevOps Engineer · TWIA · Austin, TX
- Nebula Flight Software Engineer · Intuitive Machines · Houston, TX
- Field Applications Engineer · Supermicro · Austin, TX
Where Austin, TX ranks
Where Austin, TX placed in our monthly rankings, month by month. Each month stays online at its own address.
November 2026
- #1Best cities for pay after cost of living in the Southwest$138k · of 15
- #1Best cities for pay after cost of living in Texas$138k · of 8
- #1Best cities for software and engineering jobs in the Southwest2,069 openings · of 31
- #1Best all-round cities for mid-career professionals in the Southwest85 / 100 · of 15
- #1Best all-round cities for remote workers in the Southwest100 / 100 · of 15
- #1Best all-round cities for AI careers in the Southwest98 / 100 · of 15
Rankings about engineering jobs
- Best cities for software and engineering jobs #1 San Francisco (3,732 openings)
- Best cities for engineering pay after cost of living #1 San Mateo ($163k)
- Most requested AI skills in engineering jobs #1 AI tools in daily work (6.1%)
- AI tools named most often in engineering jobs #1 Claude (1.7%)
- Employers with the most engineering jobs #1 Amazon (2,360 roles)
Pay compared with the market
This listing pays about $235,410 a year. Across 106 open principal software engineer listings that state pay, the middle half runs $228,000 to $320,000 and the median is $283,500. That is inside the middle half of those listings, 17% below the median.
Listed pay is what employers advertise, not what people are paid.
Principal Software Engineer salaries by state · Check your own pay
How AI is used in this kind of work
Among software developers, AI is already used for some of the tasks. Measured exposure for software developers: 29% (some).
Share of this job’s tasks that AI is already used for at work, from real usage. It is not a forecast of job loss, and a low number means no use seen yet. Source: Anthropic Economic Index.
Skills this job asks for
Say which you have and which you want to build. We use it to match you to jobs like this one.
About the job
Principal Software Engineer - Infrastructure Platform - Austin, Texas, United States Kiosk mode
Principal Software Engineer - Infrastructure Platform
221 West 6th Street, Downtown Austin, Austin, Texas, United States, 78701
Principal Software Engineer - Infrastructure Platform
Apply Now
Principal Software Engineer - Infrastructure Platform
R0018525
Austin, Texas, United States
Software Engineering (General)
Engineering
Full_time
We are looking for a Principal Software Engineer to join Procore’s Government Engineering team as the technical lead for how our FedRAMP platform is provisioned, organized, and governed. This is a hands-on architecture and engineering role: you will set the direction for infrastructure as code across the authorization boundary, build the provisioning systems that stamp out compliant accounts, environments, and clusters, and write the software that makes that infrastructure self-service, auditable, and reliable. You will bring an SRE mindset to the work, treating reliability, operability, and compliance as engineering problems to be solved in code rather than in tickets.
The impact of this role is wide: the foundation you design is what every service inside Procore’s FedRAMP authorization boundary runs on, and it MUST respect and protect that boundary. We build with modern tooling, including AI-assisted development and AI-driven automation, so that a small team can run a large, compliant platform without drowning in toil.
This position reports to the Senior Engineering Manager of the Government Engineering team and is a hybrid role based out of our Austin, TX office. Consideration will be made for this role to be based in Carpinteria, the Bay Area, or NYC. This position requires US citizenship to work on FedRAMP-compliant projects. Candidates must be eligible to work on federal government projects requiring FedRAMP authorization.
What you’ll do:
Own infrastructure as code for the boundary: Define the architecture, module standards, and delivery workflow for all FedRAMP infrastructure in Terraform (or similar), and drive the platform toward fully codified, reviewed, and automatically deployed infrastructure.
Design provisioning and organization: Architect how cloud accounts, organizational units, networks, Kubernetes clusters, and environments are structured and provisioned inside the authorization boundary, including landing zones, guardrails, and account vending, so that new workloads land compliant by default.
Build the provisioning platform: Write production software (Go, Python, or TypeScript) for the controllers, pipelines, and internal tooling that turn infrastructure requests into reviewed, policy-checked, automatically applied changes.
Apply AI to infrastructure: Use AI-assisted development tooling daily, and build AI-driven automation into the platform: agents that draft and validate IaC changes against policy, generate compliance evidence from infrastructure state, and detect and remediate drift.
Set technical direction: Own the multi-year platform architecture, write and review design documents, make build-versus-buy decisions, and align engineering, security, and compliance stakeholders on the roadmap.
Engineer for compliance: Translate FedRAMP controls (NIST SP 800-53) for configuration management, change control, and boundary protection into policy-as-code and automated evidence, and partner with security on continuous monitoring (ConMon) and annual assessment readiness.
Run the platform like an SRE: Establish reliability standards, SLOs, and incident practices for the provisioning layer, and lead the response when the foundation itself has problems.
Lead and multiply: Mentor Staff and Senior engineers, lead cross-team migrations onto the standard platform, and act as the final technical authority for infrastructure decisions inside the boundary.
What we’re looking for:
Experience: 12+ years of software, infrastructure, or site reliability engineering experience, including at least 3 years operating within a FedRAMP-authorized or similarly regulated environment, with hands-on AWS GovCloud experience.
Infrastructure as code mastery: Deep, hands-on expertise designing and scaling Terraform (or similar) across many accounts and environments: module design, state management, policy-as-code (e.g., OPA, Sentinel, Checkov), and GitOps-based delivery.
Cloud organization and provisioning: Proven experience designing multi-account cloud organizations, landing zones, account vending, network topology, and IAM boundaries at scale, and an understanding of how those choices map to compliance controls.
Software engineering proficiency: Strong programming fundamentals and a track record of shipping production software in Go, Python, or TypeScript, including internal platforms and developer tooling used by other engineers.
Kubernetes expertise: Extensive experience architecting, provisioning, and hardening Kubernetes clusters as code, including policy enforcement (e.g., OPA/Gatekeeper, Kyverno) and secrets management.
Technical leadership: A history of setting architecture direction for a platform organization, writing design documents that others build from, and influencing without authority across engineering, security, and compliance.
SRE practice: Experience owning reliability for foundational infrastructure, including incident command, postmortems, and systematic toil reduction.
AI tooling: Comfort using AI-assisted development tools in daily work, and a point of view on how AI should be applied to infrastructure automation.
Nice to Have:
Experience with cloud traffic, service mesh, and observability tooling (Isti