Lead a project that shapes how
the world understands Exalate
docs.exalate.com is one of our highest-traffic properties. This is the project to make it work better — for users, for search engines, and for AI systems discovering us every day.
Two documentation sites, one pipeline, and a clear finish line
Right now, Classic Exalate and New Exalate share the same documentation surface at docs.exalate.com. That’s a problem: search engines get confused, users land on the wrong version, and our auto-generation pipeline can’t run cleanly on a mixed surface.
This project fixes that — by separating them into two independently maintained sites and standing up an AI-assisted pipeline that covers the full documentation lifecycle: gathering, generation, and SDD production. That means active collaboration with engineering and BAs, not just automating what happens at release time.
Why it matters beyond the docs team: docs.exalate.com is indexed, it ranks, and it is increasingly used by AI systems as source material for answering questions about Exalate. Accurate documentation improves ranking, strengthens AI-channel discoverability, and a live pipeline means releases ship with current docs instead of lagging weeks behind.
High visibility. Real impact. Cross-company reach.
This is not a back-office project. You will be touching one of Exalate’s key digital assets and working directly with engineering, product, content, and SEO specialists to deliver something with a tangible, measurable effect on how Exalate is found and understood.
A key company initiative
docs.exalate.com is one of our highest-traffic properties. The work you do here has a direct line to business impact.
Work across the whole company
Engineering, product, content, SEO — this role gives you a rare view across every function that makes Exalate run.
You own the outcomes
A defined scope, specialist support, and the autonomy to drive decisions across teams — without needing to be the expert yourself.
The must-haves — and the nice-to-haves
You don’t need to be a technical specialist. You do need to be someone who can hold a cross-functional project together and drive it to a finish line.
- Project management experience shipping cross-functional work with engineering, content, and product.
- Ability to coordinate specialists — SEO, pipeline engineering, content — without needing to be the specialist yourself.
- Willingness to drive decisions across teams that do not report into this role.
- Familiarity with docs.exalate.com as a user or contributor.
- Prior exposure to documentation tooling, static site generators, or content pipelines.
- Working understanding of SEO fundamentals; GEO exposure a plus.
Four things that define success at ~6 months
The project has a finish line. Here is what it looks like when you get there.
- 1Site separation delivered Classic and New Exalate live on independently maintained documentation surfaces, cleanly separated.
- 2Auto-generation pipeline live for New Exalate The pipeline is running, with a defined quality-review loop in place before content publishes.
- 3URL architecture and content hierarchy locked in SEO and GEO input was at the table when decisions were made — not bolted on afterwards.
- 4Release cadence coordinated with product The pipeline stays current because the input is current — you’ve built the loop that keeps it that way.
You coordinate the experts. You don’t have to be one.
This role comes with specialist support built in. Here is how it works in practice.
Specialist input is available. The PM convenes — you do not need to own the expertise.
An engineering lead owns implementation and BAs contribute to documentation gathering and SDD production. The PM owns scope, acceptance criteria, and timeline.
A content owner signs off on auto-generated output. The PM owns the design of the review loop.
What this move actually looks like in practice
We want you to have the full picture before you even walk into the room. Here is the honest version of what this opportunity involves.
Simple, focused, and no surprises
Because this is an internal move and we already know each other, we’re keeping this tight — one or two conversations at most. Here is what to expect.
Coffee conversation
An open, informal chat. We talk through the project in real terms — what it involves, what support looks like, and whether it’s the right fit for you at this point in time. No preparation needed for this one.
Competency conversation + short case study
We check the things that matter most for this role: cross-functional coordination, driving decisions without direct authority, and scoping work clearly. There’s a small, practical case study — nothing open-book, nothing that requires deep technical knowledge. We care about how you think and how you’d approach the work.
Depending on how things go, we may combine both steps into a single session.
A few things worth thinking about beforehand
You don’t need to prepare a presentation or memorize anything. The most useful thing you can do is reflect honestly on the following before we talk.
- What does coordinating work across teams you don’t manage look like in your experience? Think of a specific example where you had to drive a decision or keep alignment across people with different priorities.
- How do you scope a project with many moving parts? How do you decide what’s in, what’s out, and what comes later?
- docs.exalate.com — spend 10–15 minutes on it if you haven’t already. What do you notice? What would a user or an AI system make of it today?
- This role involves a temporary shift away from your current work. What does that mean for you practically — and is this the right moment for it?
- What questions do you have? Bring them. We would rather you come in with hard questions than leave uncertain.
On the case study: It will be short and practical. We are not testing deep technical knowledge. We want to see how you think about scope, coordination, and decision-making in a real-ish scenario. No advance research required — just show up thinking clearly.