RR

Principal Engineer, Discoverablity

Accepting applications

Rocket Resume · San Francisco Bay Area

Full-Time Mid_senior AIateganrfrtl
Posted
3d ago
Category
Test
Experience
Mid_senior
Country
United States
About Rocket Resume

Rocket-Resume.com is the flight deck for the modern career. In an era where AI defines the hiring process, we empower millions of job seekers to build high-velocity, high-impact resumes. We don’t just build documents; we build data-driven career narratives. As we scale toward becoming the world’s #1 career intelligence platform, we are looking for an AI SEO Specialist to bridge the gap between technical site architecture and the next generation of Answer Engine Optimization (AEO).

We are looking for a Principal Engineer to own and evolve the infrastructure that makes our content discoverable by the next generation of engines, working closely with our Technical Lead to define the future of the platform.

The Discipline

Discoverability Engineering is the engineering of how content and data are discovered, retrieved, cited, and reasoned over by any engine: human-search, answer-engines, or autonomous agents.
The industry has multiple framings for adjacent work—SEO, GEO, AEO, LLMO, Relevance Engineering, Corpus Engineering. None of them quite fit the architectural problem we are solving.
Some of the things we think about:
Agent-First Architecture: We are not a product that bolts agent support onto a human-designed site. The data layer serves both surfaces—agent-readable and human-readable—from a single curated source. Same URL, no drift between them.
Curated Content & Curation Timing: Curation can happen at different points—write-time, query-time, or somewhere in between. The choice has architectural implications, and the right answer depends on the corpus.
Multi-Tenant by Design: What we build for Rocket-Resume extends to future brands on the same platform.
We want you to extend our thinking, push back, and sharpen our approach.

The Role
In this role, you will lead the engineering and strategic vision for the discoverability layer of the platform—defining what gets built, designing how it’s built, and shipping code alongside the engineering team. You own the infrastructure that makes content discoverable and converts intent into revenue.

Specifically, you’ll engage with problems like:
How does our content model render to both an agent-readable surface and a human-readable one, from a single source, without drift?
How do we orchestrate an architectural SEO strategy that turns tens of thousands of pieces of content into genuinely original assets—each one passing strict quality bars in its own right?
How do we develop, manage, and scale a content roadmap optimized specifically for subscription conversions?
How do we make per-tenant configuration extend to discoverability so each brand inherits the platform's capability with its own identity?

Some of these are already partly answered. Most are partly open. You will have opinions; we want to hear where they take ours.

What You Bring

We are not enumerating year-counts or specific tool-stacks. The attributes that matter to us are:
First-Principles Thinking: When you encounter a new problem, you reason from the structure, not from old playbooks. The discipline is evolving rapidly; the playbooks aren't trustworthy yet.
Strategic Execution: You have a proven track record of leveraging deep experience with AI, AEO, and Google standards to explode organic clicks and conversions.
Conversion-Minded Architecture: You understand the relationship between data structures and user behavior, capable of tying content roadmap infrastructure directly to subscription conversions.
Engineering Fluency: You can talk about content negotiation, schema design, and vector retrieval—and the trade-offs between them—without needing a translator.
Working Knowledge of the Space: SEO, GEO, AEO, LLMO, and the broader retrievability landscape—you have engaged with it deeply enough to know what is load-bearing and what is industry-vocabulary churn.
Architectural Posture, Not Optimization Posture: You see SEO/AEO as a primary consumer of an underlying data architecture, not as a bolt-on afterthought.
Critical Engagement: You read what is above and have immediate responses. You will push back where we are wrong, extend where we are directionally right but incomplete, and tell us what we are missing.

If the way we've framed the discipline above already has you thinking "yes, and also..."—that's the signal we're looking for.

What This Isn't

So you can self-select:
It isn't pure traditional SEO. We are past that framing.
It isn't a hands-off architect role. You are part of the engineering team—in the code, in the data, shipping.
It isn't a role for retrofitted-paradigm thinkers. The architecture we're building is incompatible with bolt-on optimization.
How to Apply
Tell us how you would extend, push back on, or sharpen what is written above. What have you built that is adjacent? If you have thought about agent-era discoverability, orchestrated SEO strategies, and conversion architecture from a systemic level—not just a tactical one—we want to talk.

Why Rocket Resume?

Remote-First Culture: Work from wherever you are most productive.
Cutting-Edge Stack: We aren't fighting legacy tech; we are building the future of career tech.
Impact: Your work directly helps millions of people navigate the most important transitions of their lives.
"If you see SEO as a branch of Information Science rather than just Marketing, we want to talk to you."

Are you ready to launch? Apply now and show us how you’d optimize Rocket Resume for the next five years of AI evolution.
Show more Show less