How We Built an AI Career Co‑pilot that Turns Knowing into Doing for Disadvantaged Students

Podcast artwork for Just Now Possible with bold white and yellow title on a navy background, teal network diagram, the line with Teresa Torres, and a banner reading Building a Career Co-Pilot @ Zero Gravity.

How do you help disadvantaged students take action on opportunities they don't even know exist? That question has been top of mind for me as I’ve explored how AI can augment—not replace—human mentorship. Recently, I dug into the work behind Zero Gravity, a UK-based platform using mentoring, community, and learning pathways to unlock elite career opportunities for state school students. Their approach reframed a core problem I care deeply about: the "knowing-doing gap."

I sat down with Elliot Little (Product Manager) and Dan St. Paul (Software Engineer) from Zero Gravity to unpack how they’re tackling this gap with an AI career co‑pilot. They’ve intentionally positioned the system as an orchestrator, not an automation tool—bridging the space between knowing what to do and actually doing it. As a product leader, I see this as a powerful pattern for Generative AI: use AI to coordinate steps, personalize guidance, and empower action in moments where confidence and clarity are fragile.

What resonated most was the humility of their build journey. They started with grand visions of AI mentors and synthetic avatars, then scaled back to something simpler and more effective. The first prototype—a job suitability summary—didn’t deliver the "wow moment" they expected. And they discovered that hiding the "LLM magic" backfired—students needed to feel the personalization. That insight aligns with my own experience: users must perceive the value for trust and motivation to compound.

From a UX standpoint, the team chose text chat over voice input and leaned into guided prompts rather than empty text boxes. That decision lowered cognitive load and increased completion rates—classic product management tradeoffs that privilege momentum over novelty. In my view, this is what good AI product strategy looks like: invite action with structure, then expand autonomy as confidence grows.

The technical backbone is equally thoughtful. Multi‑month journeys require rigorous context window management to avoid exploding token counts and degrading quality. I appreciated their pragmatic toolkit: context management techniques like removing stale tool calls, summarizing history, exposing tools conditionally. They also used application logic rather than complex RAG architectures to manage tool availability and context freshness. This is the kind of disciplined engineering that keeps systems reliable at scale without overcomplicating the stack.

Model selection was fit‑for‑purpose, not one‑size‑fits‑all. They’re using different models for different tasks, including "GPT-5 Nano for structured outputs, lighter models for quick replies." That modularity enables speed and cost control while preserving high‑fidelity moments where structure matters most.

Safeguarding was treated as a first‑class concern—non‑negotiable when you’re building AI for 16‑year‑olds. Their safeguarding architecture pairs moderation endpoints with external verification via Unitary. They also invested in building a failure taxonomy through internal red team/green team exercises. This is AI risk management done right: define failure modes early, test ruthlessly, and wire safety into the product surface area—not just the model layer.

Evaluation was grounded in outcomes, not demos. The team focused on whether students progressed from insight to action: applying, interviewing, and engaging with mentors. That aligns with how I run eval‑driven development—ship narrowly, measure real behavior, and iterate toward a repeatable "wow moment" that students can actually feel.

Looking ahead, I’m excited by what’s next: long‑term memory management for multi‑year student journeys. It’s a hard problem—balancing privacy, provenance, and portability—but it’s precisely where an AI career co‑pilot can compound value over time. The vision is compelling: a resilient companion that remembers goals, adapts to context, and orchestrates the right next step.

If you want to dive deeper, you can listen to the full conversation on Spotify and Apple Podcasts:

Listen to this episode on: Spotify | Apple Podcasts

Resources mentioned:

Zero Gravity: https://zerogravity.co.uk/

Unitary – AI-powered content moderation: https://www.unitary.ai/

Blue Dot Impact AI Safety Course – free AI safety course Elliot recommended: https://bluedot.org/

My key takeaways: build AI that augments human relationships, not replaces them; don’t hide the personalization—let learners feel it; privilege application logic over unnecessary architectural complexity; and treat safety, context, and evaluation as product features, not afterthoughts. That’s how we bridge the "knowing-doing gap" with integrity and scale.


Inspired by this post on Product Talk.


Book a consult png image

What is the AI career co-pilot designed to do?

It is an AI system designed to augment human mentorship for disadvantaged students. The team positions it as an orchestrator that coordinates steps, personalizes guidance, and helps students move from insight to action.

What problem does it aim to solve?

It addresses the knowing-doing gap by bridging the space between what students know and what they actually do. It focuses on turning insights into concrete actions like applying, interviewing, and engaging with mentors.

What UX decisions were highlighted in the build?

From a UX standpoint, they chose text chat over voice input and leaned into guided prompts rather than empty text boxes. This lowered cognitive load and increased completion rates, aligning with inviting action and later expanding autonomy as confidence grows.

What technical approaches keep the system reliable?

They manage multi-month journeys with context window management to avoid token counts exploding and quality degradation. They used application logic to control tool availability and context freshness, and they employed model specialization, including GPT-5 Nano for structured outputs and lighter models for quick replies.

How is safeguarding implemented?

Safeguarding is treated as a first-class concern, with a safeguarding architecture that pairs moderation endpoints with external verification via Unitary. They built a red team/green team failure taxonomy to test and refine safety.

What’s next for the AI co-pilot?

Long-term memory management for multi-year learner journeys is the next frontier. It balances privacy, provenance, and portability to become a resilient companion that remembers goals and orchestrates the next step.

Where can I listen to the full conversation?

Listeners can find the full conversation on Spotify and Apple Podcasts.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Signup for Weekly Digest Emails

Categories

Archieve