Cite as: Real Problem AI problem “Why does onboarding a second engineer onto our AI codebase take weeks?”. Opportunity score 7.3 out of 10 (severity 7, AI feasibility 8, market signal 7, competition gap 7). Category AI / Agents. Trend Agents. Source signal: YC Slack threads (Winter 2026 batch), r/cscareerquestions "my new job's codebase is AI slop" posts.. Canonical URL: https://www.realproblem.ai/archive/why-does-onboarding-a-second-engineer-onto-our-ai-codebase-take-a-month.
Why does onboarding a second engineer onto our AI codebase take weeks?
AI-first startups have weird codebases: half human, half Cursor, half deprecated. New hires can't read it because Claude wrote it differently each session.
Who has it: Seed-stage CTOs and tech leads hiring engineer #2 onto an AI-heavy codebase.
Evidence
Engineers describe new hires asking why the codebase uses several patterns for the same job, and the honest answer being that the AI wrote it differently each time.
Our summary of a complaint that recurs in public posts, not a quote. Nobody submitted it to Real Problem AI.
Seen in: YC Slack threads (Winter 2026 batch), r/cscareerquestions "my new job's codebase is AI slop" posts.Scoring breakdown
Existing players
- Sourcegraph Cody · Search-heavy, no onboarding flow
- Greptile · PR review, not onboarding
- Internal docs · Always stale
What they are missing
An onboarding agent that walks new hires through the codebase the way the senior dev would: "here's why this folder is weird", "here's the convention we settled on", with auto-generated runbooks and a quiz mode that surfaces gaps.
Stack hint
#AI37 · Canonical URL: https://www.realproblem.ai/archive/why-does-onboarding-a-second-engineer-onto-our-ai-codebase-take-a-month