Where We Are

Engineers spend their days switching between dashboards, terminals, and observability tools. They diagnose issues, chase alerts, and do the repetitive work that keeps systems running. Most of it isn't hard. But it's constant. It crowds out the work that actually makes systems better.

Cleric is an AI SRE teammate. We autonomously diagnose production issues across complex distributed systems. Not just the big outages. The small stuff too. No fix is too small. Engineers can focus on building. Systems get more resilient because problems actually get addressed.

Think of it this way: coding agents are becoming the future of the IDE. Cleric is the equivalent for production operations. We're the future replacement for the dashboards and terminals where engineers who monitor production live today.

It's working. Gartner named us a Cool Vendor in SRE and Observability. 80% of diagnoses are rated as accurate by senior engineers. Teams see value in 24 hours. Two-week pilots convert to one-year contracts. Customers include BlaBlaCar, the largest long distance mobility platform in Europe and we've raised $9.8M from Zetta and Vertex.

What we need now is someone to turn that into a consistent, qualified pipeline.

The Role

You'll build the marketing function. The infrastructure, the programs, and the team. You'll own how it all comes together and scale it as we grow.

You’ll lead the marketing function, collaborating with our senior product marketer to scale our technical narrative into high-impact programs and pipeline. You'll riff with us on messaging, take it to market, and iterate with your team. You own execution. High autonomy, hands-on, and full agency to experiment.

Growth

• Build programs that reach platform and infrastructure engineers. Create content and programs that engineers find genuinely useful. The community follows from that.

• Design and run lead generation across content, events, community, partnerships, and outbound

• Work with founders and sales on ICP, qualification, and sales handoff

Messaging & Channels

• Turn our product story into campaigns that run. Website, events, sales enablement.

• Keep quality and consistency across everything external

• Manage PMM, writers, agencies, contractors. Brief them well. Hold the bar.

Infrastructure

• Own the stack. CRM, lifecycle, analytics, attribution.

• Build dashboards tied to pipeline and revenue. Know what's actually working.

• Test and iterate. We care about what generates quality pipeline, not activity metrics.

Team

• Execute hands-on first. Prove what works before building a team around it.

• Hire early marketing team members as we scale

• Decide what to build, what to outsource, when to change the model

Who You Are

• Based in SF and excited to work in-office.

• CS degree or equivalent technical foundation. You can hold a 30-minute conversation with a platform engineering lead without getting lost.

• You're scrappy. You ship imperfect things, learn fast, iterate.

• You've done this before there was a big team, clean data, or an established playbook

• You've built or scaled demand gen at an early-stage B2B company selling to engineers, SREs, platform teams, or DevOps

• You're comfortable owning a pipeline number

How We Work

We bias toward launching and learning. A campaign that ships next week and teaches us something beats a comprehensive plan that ships next month.

Some marketing orgs optimize for polish and coordination. We optimize for speed and iteration. Both approaches can work. Ours requires comfort with imperfect information and a willingness to be wrong.

What Success Looks Like

Six months in:

• Qualified leads that match our ICP. Not just volume.

• Clear picture of which channels and programs drive pipeline

• Sales treats marketing as a source of opportunities, not a cost center

• Pipeline that doesn't depend on founder heroics

• A community of engineers who genuinely care about Cleric - they share, refer, and engage because they're excited, not prompted

Why Now

The product works and we have real traction. What's missing is the engine to turn that into consistent growth. You'd be building it at a company where the hard part—making something engineers actually want—is already in place.