PROJECT CASE STUDY // TECHNICAL NARRATIVE

AI Career CoPilot

Multi-Agent Job Application Assistant & Kanban Tracking Engine

YOUR ROLE & SCOPEFull-Stack AI Developer
TIMELINE6 Weeks
CORE CONSTRAINTSManaging LLM API rate limits during high-volume job description processing
error_outline

1. THE PROBLEM

Applying for technical jobs requires hours of manual work tailoring cover letters, matching key experience items to job specs, and keeping track of application statuses across multiple platforms.

architecture

2. TECHNICAL APPROACH & DECISIONS

1Decoupled Celery Worker Architecture

✓ DECISION CHOSEN

Offloaded heavy multi-agent LLM calls (discovery, cover letter generation, ATS check) to background Celery tasks backed by Redis.

✕ REJECTED ALTERNATIVE

Synchronous HTTP API requests

LLM generation loops take 5–15 seconds per job post. Asynchronous queue workers prevent HTTP gateway timeouts and allow users to queue multiple applications simultaneously.

2ChromaDB Vector Matching

✓ DECISION CHOSEN

Stored vectorized user project snippets in ChromaDB to dynamically pull the 3 most relevant project achievements for every new job description.

✕ REJECTED ALTERNATIVE

Static templates with variable replacement

Dynamic vector retrieval ensures that a ML job application emphasizes PyTorch experience, while a Full-Stack application automatically pulls Next.js achievements.

balance

3. TRADE-OFFS & HONEST REFLECTION

Running background Celery workers required introducing Redis infrastructure overhead, but completely solved user experience lag during LLM generation.

task_alt

4. CONCRETE OUTCOME & METRICS

Automated candidate-job alignment, custom cover letter drafting, and real-time Kanban pipeline state updates.

Async Celery + RedisTask Processing
ChromaDB Embedding StoreVector Index
Google Gemini APILLM Engine
Explore Project Sources
Review live deployment or inspect codebase on GitHub.