Skip to content
Lovelace

Site Reliability Engineer (SRE)

Lovelace HQLocation unclear
FullTime · Engineering
POSTED 26 OCT
Apply Ask
Role
20 days opentrue age
Posted 26 Oct
CompanyLovelace →
3open roles
Opened · 30d
+0
Closed · 30d
−0
8d of snapshots · 30d window
Market
3,226open · DevOps / SRE / Infra
Opened · 7d
+2698% of open
All devops / sre / infra
6,922open
All tracked boards · live 16 Nov · n=3,226
PythonGoAWSGCPAzureKubernetesTerraform

About Us

Lovelace is the only provider of enterprise-scale context engines capable of analyzing trillions of real-time data points to create knowledge graphs that are usable by autonomous agents at the speed, scale, and accuracy required for mission-critical analysis.

Lovelace’s context engine platform, Elemental, uniquely integrates data ingestion, entity resolution, and graph building into a single pipeline that empower agentic deployments, delivering 1000X the investigative power for complex queries. With its proprietary ground-breaking YottaGraph, Lovelace provides enterprises with real-time, real-world context, enabling agents to understand the impact of global intelligence on enterprise data for unmatched insights with millisecond precision.

Founded in 2023 by Andrew Moore, former head of Google Cloud AI, dean of Carnegie Mellon’s School of Computer Science, and first AI advisor for U.S. CENTCOM, Lovelace currently works with some of the largest public and private enterprises in the world.

Job Summary

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.

Key Responsibilities

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

Qualifications

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

Source · LovelaceFirst seen 7 NovOriginal ↗