> Markdown version of [/jobs/ext/4726082-staff-software-engineer-networking](https://www.wearedevelopers.com/jobs/ext/4726082-staff-software-engineer-networking). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer - Networking - **Company:** Procore - **Location:** Austin, TX, United States - **Experience:** Expert - **Salary:** $168,560 - $231,770 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Audit Trail, Code Review, Domain Name System (DNS), Federal Information Processing Standards (FIPS), Identity and Access Management, Python (Programming Language), Key Management, Network Security, Machine Learning, Routing, OpenID, Reliability Engineering, Site Reliability Engineering Practices, Prometheus, Zero Trust Network Access, Security Assertion Markup Language (SAML), Software Engineering, TypeScript, Datadog, Network Routing, Transport Layer Security, Okta, Istio, Delivery Pipeline, Agentic-AI, Kubernetes, Hashicorp, Cloudflare, Terraform, AIOps - **Published:** November 15, 2026 - **Apply:** https://jobs.localjobnetwork.com/apply/add/87581554/1 ## About the Role * 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. ## Description * 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.