The Nine-Month Pitch¶

Who You Are at April 27, 2027¶

This file contains six versions of the same truth. One pitch sentence, six formats, six different rooms. Each is grounded in specific shipped artifacts — not in “experience” or “passion” or “dedication.” If you can’t point to a live link, don’t say the thing.

Read this file for the first time in M7. Rehearse from M8. Deliver from M9.

The M9 sentence (say this first, before everything else):

“I’m an applied ML engineer who spent 9 months rebuilding CS foundations from scratch — complexity theory through competitive programming — and shipped 6 public artifacts proving it. I can now solve LeetCode Hard problems and have a rated Codeforces history.”

Everything below is that sentence, expanded for its context.

Version 1 — 30-Second Elevator Pitch¶

Use when: an engineer or manager asks “what have you been working on outside of work?” at a conference, meetup, or Zoho event.

“For the past 9 months, I ran a structured self-study program to rebuild my CS fundamentals from scratch. I’m an ML engineer, so I’d been using a lot of tools without really understanding the underlying algorithms. I wrote a DP pattern handbook that’s on GitHub, got to Pupil/Specialist on Codeforces, and solved 160+ LeetCode problems including Hards. The goal wasn’t job prep — it was actually understanding what I was doing.”

What not to say: “I’ve been studying algorithms.” Too generic. “I’ve been on a self-improvement journey.” Too vague and soft.

Version 2 — 2-Minute Recruiter Call¶

Use when: a recruiter or hiring manager asks “can you walk me through your background?”

“I’m a 2-year applied ML engineer at Zoho. I build and deploy ML models for [your specific work domain]. Over the past 9 months I ran a deliberate program to close the gap between knowing how to use ML tools and understanding the CS foundations underneath them.

Concretely: I implemented core data structures from scratch, built a public DP pattern handbook covering 10+ patterns that’s been referenced in the Codeforces community, competed in rated Codeforces contests and hit [your rating], and solved 160+ LeetCode problems including Hards. The public artifacts are all timestamped and linkable.

The reason I did this is that I was tired of reaching for libraries without understanding them. I wanted the mental models, not just the outputs. That shift is visible in how I approach production ML problems now.”

Artifacts to have ready on that call: GitHub profile link, LeetCode profile link, Codeforces profile link, DP handbook link.

Version 3 — 5-Minute Technical Introduction¶

Use when: you’re meeting a senior engineer or technical lead who asks about your background before a deeper conversation.

“My background is applied ML engineering — model deployment, inference optimization, pipeline design at Zoho. For the past 9 months I ran a structured CS fundamentals rebuild alongside my full-time work.

The arc: Phase 0 was complexity theory and mathematical thinking — I can now formally derive time and space for any algorithm I write, not just state it by pattern. Phase 1 through 3 covered data structures and graphs — I implemented a complete library from scratch: arrays, linked lists, hash tables, heaps, tries, union-find, all with unit tests on GitHub.

Phases 4 and 5 were DP and advanced algorithms — I wrote the DP Pattern Handbook, which covers 10 patterns with full state definitions and recurrences, currently posted on GitHub and the Codeforces blog. I got review comments from the CF community and incorporated them.

Phase 6 was competitive programming. I have [N] rated Codeforces contests, current rating [X]. The interesting part of CP for me wasn’t the competition itself — it was the precision it forces. You can’t fake O(n log n) in a 2-second time limit.

The ML connection: Viterbi is Bellman-Ford on a sequence DAG. Beam search is best-first search over a heap. Once you see those structures, ML systems stop being magic and start being mechanisms. That’s what the 9 months bought me.”

Artifacts: Have all links open in a browser tab before this conversation.

Version 4 — Portfolio Landing Page (GitHub Capstone README intro)¶

This is the text for Rung 8: your public capstone showcase.

# 9-Month DSA Foundations Rebuild
## Applied ML Engineer → Algorithmic Thinker

I'm a 2-year applied ML engineer at Zoho. In 2026–2027 I ran a 9-month structured
program to rebuild CS foundations from the ground up — while working full-time,
10–15 hours/week personal time.

**The problem I was solving:** I could train models, deploy pipelines, and hit
production targets. I couldn't derive why the heap operation was O(log n) or
explain why my hash table degraded under adversarial input. I was effective but
not fluent. This is the record of becoming fluent.

## What I Built (All Timestamped)

| Artifact | Link | Completed |
|----------|------|-----------|
| Complexity Audit | [link] | Sep 2026 |
| Data Structures Library | [link] | Nov 2026 |
| Algorithm Visualizer Posts | [link] | Dec 2026 |
| LeetCode 100 Medium | [link] | Jan 2027 |
| Graph Algorithm Showcase | [link] | Mar 2027 |
| DP Pattern Handbook | [link] | Mar 2027 |
| Codeforces Rating ([X]) | [link] | Apr 2027 |

## By the Numbers
- 9 months · 10-15h/week · alongside full-time ML engineering work
- 160+ LeetCode problems (Easy/Medium/Hard)
- [N] rated Codeforces contests · Rating: [X] (Pupil/Specialist)
- 6 public artifacts with live links

## The One-Sentence Version
An applied ML engineer who rebuilt CS foundations from scratch — complexity
theory through competitive solving — over 9 months, shipping 6 public
proof-of-work artifacts that demonstrate systematic algorithmic thinking.

Version 5 — LinkedIn Headline and Bio¶

Use when: updating your LinkedIn profile in M9.

Headline options (pick one, don’t combine):

Applied ML Engineer · DSA Practitioner · Codeforces [Rating] · Built the foundations
ML Engineer at Zoho · Rebuilt CS from scratch in 2026–27 · DP Handbook on CF blog
Applied ML Engineer · Competitive programmer (CF [Rating]) · Complexity-first thinker

About section addition (insert after your current bio):

In 2026–2027, alongside my full-time ML engineering role, I ran a 9-month structured program to rebuild CS foundations from scratch: complexity theory, data structures, graph algorithms, dynamic programming, and competitive programming. I shipped 6 public proof-of-work artifacts including a DP Pattern Handbook referenced in the Codeforces community and a rated CF history. The goal wasn’t credential-chasing — it was closing the gap between using ML tools and understanding the mechanisms underneath them.

What NOT to put on LinkedIn: “Passionate about algorithms.” “Lifelong learner.” “On a journey.” These are noise. Link the artifacts instead.

Version 6 — “Why hire / assess / admit me” Answer¶

Use when: in any formal evaluation — interview, panel review, scholarship application, grad school interview.

“I can tell you specifically what I’ve built and what I can do, and you can verify all of it.

I’m an applied ML engineer with 2 years at Zoho. Over 9 months in 2026–2027, I ran a self-directed CS fundamentals rebuild — structured like a graduate curriculum, executed alongside a full-time job. I completed 7 phases: from complexity theory through competitive programming.

What that produced: I can formally analyze and derive time/space complexity for any algorithm I write. I implemented a complete data structures library from scratch with tests. I wrote a DP Pattern Handbook covering 10+ patterns that’s on the Codeforces blog and received community review. I have [N] rated contest timestamps and a rating of [X].

What I’m not claiming: I’m not claiming FAANG-level prep or 5 years of competitive programming experience. I’m claiming 9 months of disciplined, verifiable, artifact-producing self-study that closed a real gap in my CS foundation.

You can verify the timeline from the GitHub commit timestamps, the LeetCode profile, and the Codeforces contest history. The work happened. The artifacts exist. The question you’re assessing is whether this kind of structured self-direction is what you’re looking for.”

Rehearsal Schedule¶

When	Action
M7 (Feb 2027)	Read this file for the first time. Note which version feels most foreign. That’s the one to practice first.
M8 (Mar 2027)	Say Version 1 (30-second) out loud 3 times. Record yourself once. Listen back.
M8 (Mar 2027)	Populate all artifact links in Version 4 capstone README.
M9 (Apr 2027)	Say Version 3 (5-minute technical) out loud without notes. Time yourself.
Apr 27, 2027	Update LinkedIn headline. Publish Rung 8 capstone README.

One rehearsal rule: The pitch only works if you can say it without reading it. If you need the file open to remember what you built, you haven’t internalized the arc. The artifacts are the evidence. The pitch is just the door.

What NOT to Claim¶

This is as important as what to claim.

Do NOT say you have “years of competitive programming experience.”
Do NOT say you’re “ready for any FAANG interview” (this is a different preparation track).
Do NOT say you “mastered” algorithms (mastery is ongoing; you’ve built a foundation).
Do NOT pad the problem count (honest 160 > inflated 300).
Do NOT claim the Codeforces rating is higher than it is (it’s on a public profile; they can see it).

The pitch sentence is precise. It says exactly what is true. It is also rare enough to be true for very few people you’ll encounter — an applied ML engineer who did this, completed it, and shipped the artifacts. That specificity is the signal.

Return to [06_background_alignment.md] · Return to [README.md]