Staff Software Engineer - Networking

Procore

  • Austin, TX
  • Hybrid
  • Staff/Principal level
  • 8+ yrs experience
  • Platform, Infrastructure & SRE
  • No visa sponsorship
  • $169k–$232k

The role in 30 seconds

This role is a senior hands-on engineering position on Procore's Government Engineering team, focused on networking and observability for a FedRAMP-authorized cloud platform. The engineer writes production software and infrastructure code for cloud traffic, service mesh, ingress/egress, and telemetry pipelines, applying an SRE mindset to reliability, operability, and compliance. The work touches every service inside the FedRAMP authorization boundary and requires translating compliance controls into automated, testable implementations.

Is this role a fit for you?

The backgrounds this role is most likely to hire from, as RoleStack reads the posting.

Strong match

  • B2B infrastructure / API / developer tools
  • Data platform / ML pipeline
  • B2B enterprise platform / workflow software
  • Enterprise-scale
  • Regulated environment

Workable stretch

  • Internal tooling / back-office systems
  • Marketplace / multi-sided platform
  • Growth-stage

Harder transition

  • B2C consumer-facing application
  • Embedded systems / hardware-adjacent
  • Startup / greenfield

Industry: Government / FedRAMP-regulated SaaS. See your personal match score

What they're really screening for

Must-haves

  • CORE 8+ years of software, infrastructure, or site reliability engineering experience
  • CORE At least 3 years operating within a FedRAMP-authorized or similarly regulated environment
  • CORE Strong programming fundamentals and shipping production software in Go, Python, or TypeScript
  • CORE Production experience with high-throughput ingress/egress, L4/L7 routing, DNS, TLS, and container networking at scale
  • CORE Networking tooling experience with Istio, Kong, Cloudflare, and Kubernetes CNIs
  • CORE Hands-on experience designing telemetry pipelines and SLO-based alerting with Datadog, OpenTelemetry, Prometheus, or similar
  • PLUS Using telemetry data to run incident response and drive reliability improvements
  • CORE Extensive experience architecting, operating, and hardening Kubernetes clusters, including policy enforcement (OPA/Gatekeeper, Kyverno) and secrets management
  • PLUS Working fluency with Terraform (or similar), GitOps workflows, and CI/CD pipelines
  • PLUS Experience with on-call ownership, incident command, postmortems, and systematic toil reduction

Nice-to-haves

  • PLUS Experience with IAM architecture (Okta, SAML/OIDC, zero-trust) and FIPS 140-2/140-3 validated cryptography in practice
  • PLUS Experience with secrets management platforms operating in FIPS mode (e.g., HashiCorp Vault)
  • PLUS Familiarity with FedRAMP Rev 5 requirements, STIG application, or CIS benchmark enforcement at scale
  • PLUS Experience building AI agents or ML-driven automation for operations (AIOps)
  • PLUS Security or platform certifications such as CKA/CKS, AWS Certified Security - Specialty, or CISSP
  • PLUS AWS GovCloud experience

Résumé keywords for this role

Terms the posting stresses. Include the ones you can honestly back up.

Tools & technologies

  • Istio
  • Kong
  • Cloudflare
  • Kubernetes
  • CNI
  • Datadog
  • OpenTelemetry
  • Prometheus
  • Go
  • Python
  • TypeScript
  • Terraform
  • GitOps
  • CI/CD
  • OPA/Gatekeeper

Concepts & phrases

  • Staff Software Engineer
  • Government Engineering team
  • FedRAMP platform
  • service mesh
  • cloud traffic
  • observability as a platform
  • telemetry pipelines
  • SLO-based alerting
  • incident response
  • blameless postmortems
  • capacity planning
  • platform migrations
  • infrastructure as code
  • AI-assisted development
  • AI-driven automation

Words that count as the same thing: "SRE" ≈ Site Reliability Engineering, Reliability Engineering · "IaC" ≈ Infrastructure as Code, Terraform, GitOps · "ConMon" ≈ Continuous Monitoring, Ongoing Assessment · "AIOps" ≈ AI-driven operations, ML-driven automation for operations · "service mesh" ≈ Istio, Envoy, Linkerd

Check my résumé against these keywords

Hiring at Procore

Open senior roles RoleStack tracks right now, posted in the last 30 days.

More open roles at Procore

Full job description from Procore

From Procore's posting. View the original

We are looking for a Staff Software Engineer to join Procore’s Government Engineering team as a senior technical contributor on our FedRAMP platform, with a focus on networking and observability. This is a hands-on engineering role: you will write the production software and infrastructure code that runs cloud traffic, service mesh, ingress/egress, and the telemetry pipelines that tell us how all of it is behaving. 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.

Show full description Show less

The impact of this team is wide: it touches every service inside Procore’s FedRAMP authorization boundary, and 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 cloud traffic and service mesh: Design, build, and operate network routing, edge controls, and service mesh for the FedRAMP boundary using Istio, Kong, and Cloudflare, with every component defined in code and deployed through automated pipelines.
• Build observability as a platform: Design the metrics, logs, and traces pipelines (Datadog, OpenTelemetry) that give every team a clear view of their services. Define SLOs, build the alerting and dashboards behind them, and make reliability measurable.
• Write production software: Build the services, controllers, and CLIs (Go, Python, or TypeScript) that automate traffic management, telemetry collection, and compliance evidence, so that platform gaps are closed with code rather than runbooks.
• Apply AI to operations: Use AI-assisted development tooling daily, and build AI-driven automation into the platform: anomaly detection on telemetry, automated triage and remediation of common incidents, and agents that generate and validate compliance artifacts.
• Run the platform like an SRE: Lead incident response, blameless postmortems, and capacity planning for the networking and observability services. Reduce toil systematically and own the reliability roadmap for your area.
• Drive platform migrations: Lead the engineering work that moves internal teams onto centralized, compliant traffic and observability pipelines, from design through cutover.
• Engineer for compliance: Translate FedRAMP controls (NIST SP 800-53) for network security, audit logging, and monitoring into automated, testable implementations, and partner with security on continuous monitoring (ConMon) and assessment readiness.
• Mentor and multiply: Mentor mid-level engineers on SRE practices, infrastructure as code, and compliance-aware design, and raise the engineering bar across the team.

What we’re looking for:

• Experience: 8+ years of software, infrastructure, or site reliability engineering experience, including at least 3 years operating within a FedRAMP-authorized or similarly regulated environment (AWS GovCloud experience is a plus).
• Software engineering proficiency: Strong programming fundamentals and a track record of shipping production software in Go, Python, or TypeScript to build platform services and automation. You write tests, review code, and care about maintainability.
• Networking depth: Production experience with high-throughput ingress/egress, L4/L7 routing, DNS, TLS, and container networking at scale, using tools like Istio, Kong, Cloudflare, and Kubernetes CNIs.
• Observability depth: Hands-on experience designing telemetry pipelines and SLO-based alerting with Datadog, OpenTelemetry, Prometheus, or similar, and using that data to run incident response and drive reliability improvements.
• Kubernetes expertise: Extensive experience architecting, operating, and hardening Kubernetes clusters, including policy enforcement (e.g., OPA/Gatekeeper, Kyverno) and secrets management.
• Infrastructure as code: Working fluency with Terraform (or similar), GitOps workflows, and CI/CD pipelines. You expect every change to the platform to go through code review and automation.
• SRE practice: Experience with on-call ownership, incident command, postmortems, and systematic toil reduction.
• AI tooling: Comfort using AI-assisted development tools in daily work, and interest in applying AI to operations and automation.
Nice to Have:

• Experience with IAM architecture (Okta, SAML/OIDC, zero-trust) and FIPS 140-2/140-3 validated cryptography in practice.
• Experience with secrets management platforms operating in FIPS mode (e.g., HashiCorp Vault).
• Familiarity with FedRAMP Rev 5 requirements, STIG application, or CIS benchmark enforcement at scale.
• Experience building AI agents or ML-driven automation for operations (AIOps).
• Security or platform certifications such as CKA/CKS, AWS Certified Security - Specialty, or CISSP.

Additional Information

Base Pay Range:

168,560.00 - 231,770.00 USD Annual

This role may also be eligible for Equity Compensation and/or Bonus Incentive Compensation. Procore is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location.

This position requires access to technology, software, and data that is controlled or restricted under U.S. law, regulation, executive order, or government contract.

For Los Angeles County (unincorporated) Candidates:

Procore will consider for employment all qualified applicants, including those with arrest or conviction records, in accordance with the requirements of applicable federal, state, and local laws, including the City of Los Angeles’ Fair Chance Initiative for Hiring Ordinance, the Los Angeles County Fair Chance Ordinance for Employers, and the California Fair Chance Act.

A criminal history may have a direct, adverse, and negative relationship on the following job duties, potentially resulting in the withdrawal of the conditional offer of employment: 1. appropriately managing, accessing, and handling confidential information including proprietary and trade secret information, as well as accessing Procore's information technology systems and platforms; 2. interacting with and occasionally having unsupervised contact with internal/external customers, stakeholders, and/or colleagues; and 3. exercising sound judgment.

FAQ

How much does a Staff Software Engineer - Networking at Procore make?

The posted pay for this role is $169k–$232k a year.

How much experience do you need?

The posting asks for 8+ years in software, infrastructure, or site reliability engineering. It is a staff/principal-level role.

Does Procore sponsor visas for this role?

The posting says visa sponsorship is not available.

Is this role remote?

It is a hybrid role: part remote, part in the office.

What tools and technologies does the posting mention?

Istio, Kong, Cloudflare, Kubernetes, CNI, Datadog, OpenTelemetry, Prometheus, Go, Python, TypeScript, Terraform, GitOps, CI/CD, OPA/Gatekeeper.