> Markdown version of [/jobs/ext/4683477-site-reliability-engineer-sre](https://www.wearedevelopers.com/jobs/ext/4683477-site-reliability-engineer-sre). 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). --- # Site Reliability Engineer (SRE) - **Company:** Lovelace Ai - **Location:** Pittsburgh, PA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Abstraction Layers, Artificial Intelligence, Amazon Web Services, Microsoft Azure, Software as a Service, Cloud Computing, Data Files, DevOps, Identity and Access Management, Python (Programming Language), Octopus Deploy, Reliability Engineering, Prometheus, Software Engineering, Datadog, Google Cloud, Cloud Platform System, Grafana, Agentic-AI, Build Management, Kubernetes, Information Technology, Build Tools, Software Coding, Terraform, Marketplace - **Published:** November 12, 2026 - **Apply:** https://www.careerbuilder.com/job-details/site-reliability-engineer-sre-pittsburgh-pa--c433353f-1a92-4787-9de2-7dbde1117914 ## About the Role Reliability Engineering, Analysis Skills, Create Graphs, CENTCOM - Central Command, Computer Science, Cloud Computing, Artificial Intelligence (AI), Data Sets, Reliability Engineering, Software as a Service (SaaS), * 5+ years in software engineering, SRE, DevOps or infrastructure, at a senior level with demonstrated impact * A software engineer at heart: strong coding skills in Python, Go or similar, and you'd rather build tooling than run process * Hands-on deployment experience with evidence of things you built that worked in production * Working familiarity with declarative deployment tools: Kubernetes, Terraform, Helm and Argo CD * A solid grasp of core Kubernetes concepts and how they map to the underlying cloud resources, so we stay independent of any one platform * Experience with at least one major cloud (GCP, AWS or Azure) and the ability to pick up others quickly; we don't expect expertise in all of them, but you shouldn't be tied to just one * Solid grasp of networking, identity and access management, and storage in cloud environments * Comfort with ambiguity: you can walk into an unfamiliar environment, work out what's different, and fix it * Intellectual curiosity and a low ego: you back up conclusions with evidence, stay open to being wrong, and adapt rather than insist on how things were done elsewhere Preferred Skills: * A software engineer who moved into SRE or infrastructure, or an SRE who wants to build systems rather than only maintain them * Experience deploying software into customer-managed, on-prem, multi-tenant or air-gapped environments * Experience packaging software for cloud marketplaces (especially GCP Marketplace) * Familiarity with compliance frameworks such as SOC 2 or SOX * Experience with observability tools such as Prometheus, Grafana or Datadog * A home lab or personal Kubernetes cluster you've built and run * Interest in using agentic tooling to automate deployment and operations ## Description * Lovelace AI is hiring a Site Reliability Engineer to help us deploy and run our platform wherever our customers need it. Customers use our agentic SaaS platform to generate data sets, build context graphs, and give that context to AI agents. A user portal spins up each customer's tenant project automatically, with no manual work. We run primarily on GCP, are building out AWS and Azure, and package for cloud marketplaces. Customers can also host the platform in their own environments, and that list keeps growing. This is a 0-to-1 role. You'll be one of our first dedicated reliability engineers, with real authority over how we architect, deploy and operate across clouds. Much of today's work is still manual or ad hoc. Your job is to turn it into a clear, repeatable system and help us adapt to the next three cloud environments we need to go into., * Design and build the abstraction layer that lets us deploy one platform consistently across GCP, AWS, Azure and customer-hosted environments, so each new environment varies as little as possible (for example, one approach to persistent storage whether it's azurefile or filestore) * Own deployment with Kubernetes, Terraform, Helm and Argo CD for both our hosted SaaS and customer deployments, including cloud marketplace packaging * Solve the hard parts of running in environments we don't control: privileged access, service accounts, persistent connections between systems, and safely shipping updates to deployments we can't touch directly * Build and maintain the tooling behind our multi-tenant SaaS, including the portal that spins up customer tenant projects programmatically * Troubleshoot and fix what breaks when the platform lands in a new environment, then fold those lessons back into reusable tooling * Build proofs of concept for new clouds and bespoke deployment targets, working toward fully disconnected (air-gapped) environments * Help customers meet compliance requirements such as SOC 2 and Sarbanes-Oxley (SOX) when they host Lovelace in their own environment * Turn today's informal incident management and weekly reporting into a lightweight, repeatable practice * Partner with software engineers on architecture so new services are deployable, observable and resilient from the start * Choose and change tooling when it makes sense; there's room to build your own path, * Wide scope and real ownership: cross-cutting architecture that spans many clouds and customer environments * Build, not babysit: most of the work is 0-to-1 design and writing systems, not maintaining a large stable one * A tour across environments: few roles let you work hands-on across AWS, Azure, GCP and customer deployments at once * A small team where your decisions shape how the company ships