Developers who've been at a company for years (like 5 years in this case) haven't updated their resume or documented accomplishments, making the sudden need to job search feel overwhelming on top of the emotional weight.
A background tool that integrates with Git, Jira, Slack, and PR tools to passively log your accomplishments, complex projects, and impact metrics over time. When layoff hits, you export a rich, quantified resume and portfolio in minutes instead of trying to recall years of work from memory.
Subscription - $8/month while employed, captures everything passively. Pays for itself the moment you need it.
This is a 10/10 pain at the moment of layoff but averages to 9 because it's latent — people don't feel it until the crisis hits. The Reddit post (1098 upvotes, 246 comments) captures raw emotional proof. The pain is real, universal among employed devs, and has no current solution. However, latent pain is harder to monetize than active pain because users must pay today for a future emergency.
~30M professional software developers globally, ~5M in the US alone. At $8/month, even 0.1% penetration (30K users) = $2.9M ARR. TAM for 'career tools for developers' is probably $500M-$1B when you include resume builders, portfolio tools, and career coaching. The market is large enough to build a meaningful business.
This is the critical weakness. $8/month is cheap, but the value is invisible while employed — it's career insurance. Most developers won't pay for something they don't actively use daily. Churn will be brutal after the initial 'scared by layoff news' sign-up period. The people who need it most (complacent employed devs) are least likely to pay. Comparison: most developers won't even pay for a password manager. Counter-signal: the people who DO pay will be highly engaged during job transitions, but that's a short window.
MVP is buildable in 4-8 weeks for a strong full-stack dev with OAuth/API experience. Git integration (GitHub/GitLab APIs) is straightforward. Jira and Slack APIs are well-documented. The hard parts: (1) transforming raw commits/tickets/messages into meaningful achievement narratives requires solid LLM prompting and context assembly, (2) handling enterprise SSO/permissions for Slack and Jira in larger orgs is painful, (3) data privacy concerns around ingesting Slack messages will slow enterprise adoption. Score is 7, not 9, because the AI narrative generation quality IS the product — and getting that right is genuinely hard.
This is the strongest signal. Nobody occupies this exact niche. Engineering analytics tools (LinearB, Jellyfish) have the data ingestion but serve managers. Resume tools (Teal, Rezi) have the output format but require manual input. Brag doc tools proved demand but are manual. The bridge between 'passive data capture from dev tools' and 'career-ready narrative output for individual developers' is completely empty. This is rare in 2026.
Subscription model makes structural sense — you need continuous capture to deliver value. But retention will be the Achilles heel. Users will sign up after a scare, capture a few months of data, then cancel when they feel safe. The 'set it and forget it' pitch only works if the product is truly invisible. Consider annual billing heavily discounted ($60/year vs $96/year) to lock in retention, or charge more at export time rather than monthly.
- +Massive, validated pain point with clear emotional proof (viral Reddit posts, dev Twitter sentiment post-layoffs)
- +Competition gap is genuinely wide — no one bridges passive dev tool capture to career narrative output
- +TAM is huge (millions of software developers) and growing as tech employment becomes less stable
- +The product gets more valuable over time (years of accumulated data = massive moat per user)
- +Low price point ($8/month) removes friction; developers can expense it as a career tool
- +AI/LLM maturity in 2026 makes the narrative generation technically viable for the first time
- !Willingness-to-pay for 'career insurance' while employed is unproven — latent pain is hard to monetize
- !Churn will be severe: users sign up scared, cancel when comfortable, return when scared again
- !Data privacy concerns around ingesting Slack messages and proprietary code/tickets could kill enterprise adoption
- !Enterprise IT/security teams may block OAuth connections to Git/Jira/Slack for an unknown third-party tool
- !GitHub Copilot or LinkedIn could add this feature as a minor addition to their existing platform
- !AI narrative quality must be exceptional — mediocre auto-generated resume bullets will destroy trust immediately
All-in-one career management platform with job tracking, achievement journaling, AI resume tailoring, and cover letter generation. Has a 'Work History' tracker for logging accomplishments.
AI-powered resume builder focused on ATS optimization. Uses AI to write bullet points, score resume quality, and target keywords for specific job descriptions.
Engineering analytics platforms that connect to Git, Jira, and CI/CD to measure engineering output — cycle time, throughput, code churn, review participation. LinearB and Jellyfish are the market leaders.
Professional social network built around a timeline of 'highlights' — achievements, projects, talks, side projects. Closest thing to a structured brag document in social network form.
Simple web apps and templates inspired by Julia Evans' influential blog post on maintaining a 'brag document.' Developers manually log accomplishments in a structured format for performance reviews and job searches.
Start with GitHub-only integration. User connects their GitHub account, the tool ingests commits, PRs, code reviews, and repo contributions. An LLM processes this into structured achievement bullets with quantified impact (e.g., 'Led migration of authentication service from REST to gRPC, reducing API latency by 40% across 12 microservices — based on PR #1247 and 34 related commits'). Export as a formatted resume section or brag document. Skip Jira and Slack for MVP — GitHub alone has enough signal for a compelling demo. Add a simple manual 'quick capture' for non-code achievements. Ship in 4-6 weeks.
Free tier: Connect GitHub, see your last 90 days of achievements summarized (capped). Paid ($8/month or $60/year): Unlimited history, Jira + Slack integrations, AI resume generation, portfolio export. Premium ($15/month): Team features for engineering managers who want to help reports document achievements for promo packets. Enterprise ($25/user/month): SSO, data retention policies, manager dashboards. Long-term upsell: career coaching marketplace, interview prep from your actual work history, salary benchmarking based on verified contributions.
8-12 weeks. 4-6 weeks to build GitHub-only MVP, 2-4 weeks to launch on Product Hunt, Hacker News, and dev Twitter. First revenue likely from the launch spike. Sustainable MRR growth will take 4-6 months of content marketing around layoff preparedness and career documentation.
- “I'm not looking forward to interviewing or the job hunt in general”
- “Did a lot of complex UI work and a lot of backend work. Did some DevOps and SRE work as well”
- “here on Monday morning I'm just sad that I have to even do any of this”