[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792R6MSP3DZYZ1QFX720Z0D":3,"skill-same:01M792R6MSP3DZYZ1QFX720Z0D":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M792R6MSP3DZYZ1QFX720Z0D","job-search",null,"Run the application pipeline: target list, stage tracking, follow-up cadence and a weekly read on where applications die. Use when planning job search pipelines, target companies, or warm outreach.","poorvith-mp\u002Fskills-personal","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792QDKAM6RFV3Y5HAKRG9YF",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fjob-search\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: job-search\nlast_reviewed: 2026-09-06\ngroup: Career\ndescription: >-\n  Run the application pipeline: target list, stage tracking, follow-up cadence and a weekly read\n  on where applications die. Use when planning job search pipelines, target companies, or warm\n  outreach.\n---\n\n# job-search\n\n## Core Philosophy\nSubmitting 400 blind applications through LinkedIn \"Easy Apply\" is a statistical dead end that yields a $\u003C 1\\%$ interview rate and massive emotional burnout. A professional technical job search must be managed like an enterprise B2B sales pipeline: strict target account qualification, reverse-engineering company engineering stacks, activating warm 2nd-degree referrals, and demonstrating proof-of-work through custom technical artifacts before the first interview.\n\n---\n\n## 4-Step Technical Job Search Pipeline\n\n### Step 1: Target Account Curation & Tiering (30 Accounts)\n1. **Tiered Account Architecture**:\n   - *Tier 1 (Top 5 - Dream Accounts)*: Uncompromising fit, high compensation, exceptional culture. Every application gets customized work samples and multi-threaded warm outreach.\n   - *Tier 2 (15 Accounts - Strong Fits)*: High alignment with current skills, growing engineering organizations, Series B through Pre-IPO. Standard tailored resume + warm intro.\n   - *Tier 3 (10 Accounts - Benchmark\u002FSafety)*: Solid roles for pipeline velocity, interview practice, and establishing market compensation baselines.\n2. **Qualification Filters**:\n   - Tech stack match ($\\ge 75\\%$ overlap with your strengths).\n   - Financial runway (profitable or raised within last 12 months).\n   - Engineering leadership pedigree and low Glassdoor\u002FLevels.fyi red flags.\n\n### Step 2: Proof-of-Work Artifact Engineering\n1. **The Pre-Interview Work Sample**:\n   - For Tier 1 accounts, never submit just a PDF resume. Provide a tangible technical artifact:\n     - Audit their public GitHub repositories and open a well-crafted PR or detailed issue.\n     - Build a 1-page technical memo analyzing their API architecture or performance bottlenecks.\n     - Record a 2-minute Loom demonstrating a solution to a problem their job description mentions.\n\n### Step 3: Warm Referral & Multi-Threading Playbook\n1. **Network Triangulation**:\n   - Never apply cold on the careers page if a 2nd-degree connection exists.\n   - Map connections: Search LinkedIn for engineering alumni from your previous companies or universities working at the target account.\n2. **The 3-Touch Referral Outreach (Under 100 Words)**:\n   - *Message to Peer Engineer*:\n     - \"Hey [Name], saw your team at [Company] is scaling the distributed data team. Loved your recent post on [Topic]. I've spent the last 3 years optimizing ClickHouse clusters at [Previous Org]. Would love to ask 2 quick questions about how your team handles schema migrations before I apply formally. No pressure at all!\"\n3. **Direct Hiring Manager Outreach**:\n   - Identify the Director\u002FVP of Engineering or Engineering Manager owning the headcount. Send a concise email highlighting your 3 core relevant wins and attaching your custom technical artifact.\n\n### Step 4: Pipeline CRM Tracking & Conversion Diagnostics\n1. **Pipeline Stage Metrics**:\n   - *Prospecting*: Target identified, contact mapped.\n   - *Outreach Active*: Message sent, awaiting referral response.\n   - *Applied \u002F Referred*: Formal application submitted with internal tag.\n   - *Recruiter Screen*: 30-minute culture and background alignment.\n   - *Technical Screen \u002F Take-Home*: Coding or system design round.\n   - *Onsite Loop*: Multi-round executive and peer panel.\n   - *Offer Stage*: Negotiation and closing.\n2. **Funnel Health Diagnostics**:\n   - If Recruiter Screen conversion $\u003C 40\\%$: Resume bullets lack quantified impact or tech keywords.\n   - If Technical Screen conversion $\u003C 50\\%$: Brush up on DSA or distributed systems fundamentals.\n   - If Onsite-to-Offer conversion $\u003C 33\\%$: Behavioral answers (STAR method) or culture fit signals need calibration.\n\n---\n\n## Deliverable Format: Job Search Pipeline Spec (`JOB-SEARCH-PIPELINE.md`)\n\n```markdown\n# Technical Job Search Pipeline & CRM\n\n## 1. Target Criteria & Constraints\n- **Target Role**: [e.g. Senior Staff Backend Engineer]\n- **Target Comp Band**: [$X - $Y base \u002F total package]\n- **Location \u002F Mode**: [Remote \u002F Hybrid \u002F City]\n- **Core Tech Stack**: [Go, Rust, PostgreSQL, Kubernetes]\n\n## 2. Tier 1 Target Account Matrix\n| Company | Team \u002F Division | Engineering Manager \u002F Recruiter | Warm Angle \u002F Connection | Proof-of-Work Artifact | Status |\n|---|---|---|---|---|---|\n| [Target A] | Core Infra | [Name\u002FProfile] | Ex-colleague at company | Audited open source CLI | Referral requested |\n| [Target B] | Platform | [Name\u002FProfile] | Met at GopherCon | 1-page migration memo | Recruiter screen scheduled |\n\n## 3. Funnel Velocity Dashboard\n- **Total Accounts Mapped**: [Count]\n- **Active Referrals \u002F Conversations**: [Count]\n- **Technical Screens Active**: [Count]\n- **Onsite Loops Scheduled**: [Count]\n- **Offers In Hand**: [Count]\n```\n\n---\n\n## Worked Example: Senior Infrastructure Engineer Transition\n\n- **Strategy**: Bypassed cold job boards. Built a target list of 25 companies using Kubernetes in production.\n- **Proof-of-Work**: Contributed a bug fix to the target company's open-source Terraform provider before reaching out.\n- **Outreach**: Messaged the author of the pull request on LinkedIn with a 3-sentence note referencing the fix.\n- **Outcome**: Secured direct VP of Engineering interview within 48 hours; received offer with 25% compensation increase in 3 weeks.\n\n---\n\n## Verification Checklist\n\n- [ ] Target account list is capped at 30 high-conviction companies categorized into Tiers 1–3.\n- [ ] Cold applications are prohibited for Tier 1 targets; warm intro or custom artifact is mandatory.\n- [ ] Outreach messages are strictly $\u003C 100$ words with zero generic flattery.\n- [ ] Weekly funnel stage conversion rates are calculated to diagnose drop-offs.\n- [ ] Salary expectations and minimum walk-away numbers are documented prior to initial screens.\n\n---\n\n## Anti-Patterns\n\n- **Volume Spam**: Spraying 50 resumes a day to random job posts without customizing a single bullet point.\n- **Passive Waiting**: Waiting for recruiters to discover an unoptimized LinkedIn profile.\n- **Skipping the Hiring Manager**: Relying solely on automated portal submissions rather than finding the engineering leader owning the role.\n","# job-search\n\n## Core Philosophy\nSubmitting 400 blind applications through LinkedIn \"Easy Apply\" is a statistical dead end that yields a $\u003C 1\\%$ interview rate and massive emotional burnout. A professional technical job search must be managed like an enterprise B2B sales pipeline: strict target account qualification, reverse-engineering company engineering stacks, activating warm 2nd-degree referrals, and demonstrating proof-of-work through custom technical artifacts before the first interview.\n\n---\n\n## 4-Step Technical Job Search Pipeline\n\n### Step 1: Target Account Curation & Tiering (30 Accounts)\n1. **Tiered Account Architecture**:\n   - *Tier 1 (Top 5 - Dream Accounts)*: Uncompromising fit, high compensation, exceptional culture. Every application gets customized work samples and multi-threaded warm outreach.\n   - *Tier 2 (15 Accounts - Strong Fits)*: High alignment with current skills, growing engineering organizations, Series B through Pre-IPO. Standard tailored resume + warm intro.\n   - *Tier 3 (10 Accounts - Benchmark\u002FSafety)*: Solid roles for pipeline velocity, interview practice, and establishing market compensation baselines.\n2. **Qualification Filters**:\n   - Tech stack match ($\\ge 75\\%$ overlap with your strengths).\n   - Financial runway (profitable or raised within last 12 months).\n   - Engineering leadership pedigree and low Glassdoor\u002FLevels.fyi red flags.\n\n### Step 2: Proof-of-Work Artifact Engineering\n1. **The Pre-Interview Work Sample**:\n   - For Tier 1 accounts, never submit just a PDF resume. Provide a tangible technical artifact:\n     - Audit their public GitHub repositories and open a well-crafted PR or detailed issue.\n     - Build a 1-page technical memo analyzing their API architecture or performance bottlenecks.\n     - Record a 2-minute Loom demonstrating a solution to a problem their job description mentions.\n\n### Step 3: Warm Referral & Multi-Threading Playbook\n1. **Network Triangulation**:\n   - Never apply cold on the careers page if a 2nd-degree connection exists.\n   - Map connections: Search LinkedIn for engineering alumni from your previous companies or universities working at the target account.\n2. **The 3-Touch Referral Outreach (Under 100 Words)**:\n   - *Message to Peer Engineer*:\n     - \"Hey [Name], saw your team at [Company] is scaling the distributed data team. Loved your recent post on [Topic]. I've spent the last 3 years optimizing ClickHouse clusters at [Previous Org]. Would love to ask 2 quick questions about how your team handles schema migrations before I apply formally. No pressure at all!\"\n3. **Direct Hiring Manager Outreach**:\n   - Identify the Director\u002FVP of Engineering or Engineering Manager owning the headcount. Send a concise email highlighting your 3 core relevant wins and attaching your custom technical artifact.\n\n### Step 4: Pipeline CRM Tracking & Conversion Diagnostics\n1. **Pipeline Stage Metrics**:\n   - *Prospecting*: Target identified, contact mapped.\n   - *Outreach Active*: Message sent, awaiting referral response.\n   - *Applied \u002F Referred*: Formal application submitted with internal tag.\n   - *Recruiter Screen*: 30-minute culture and background alignment.\n   - *Technical Screen \u002F Take-Home*: Coding or system design round.\n   - *Onsite Loop*: Multi-round executive and peer panel.\n   - *Offer Stage*: Negotiation and closing.\n2. **Funnel Health Diagnostics**:\n   - If Recruiter Screen conversion $\u003C 40\\%$: Resume bullets lack quantified impact or tech keywords.\n   - If Technical Screen conversion $\u003C 50\\%$: Brush up on DSA or distributed systems fundamentals.\n   - If Onsite-to-Offer conversion $\u003C 33\\%$: Behavioral answers (STAR method) or culture fit signals need calibration.\n\n---\n\n## Deliverable Format: Job Search Pipeline Spec (`JOB-SEARCH-PIPELINE.md`)\n\n```markdown\n# Technical Job Search Pipeline & CRM\n\n## 1. Target Criteria & Constraints\n- **Target Role**: [e.g. Senior Staff Backend Engineer]\n- **Target Comp Band**: [$X - $Y base \u002F total package]\n- **Location \u002F Mode**: [Remote \u002F Hybrid \u002F City]\n- **Core Tech Stack**: [Go, Rust, PostgreSQL, Kubernetes]\n\n## 2. Tier 1 Target Account Matrix\n| Company | Team \u002F Division | Engineering Manager \u002F Recruiter | Warm Angle \u002F Connection | Proof-of-Work Artifact | Status |\n|---|---|---|---|---|---|\n| [Target A] | Core Infra | [Name\u002FProfile] | Ex-colleague at company | Audited open source CLI | Referral requested |\n| [Target B] | Platform | [Name\u002FProfile] | Met at GopherCon | 1-page migration memo | Recruiter screen scheduled |\n\n## 3. Funnel Velocity Dashboard\n- **Total Accounts Mapped**: [Count]\n- **Active Referrals \u002F Conversations**: [Count]\n- **Technical Screens Active**: [Count]\n- **Onsite Loops Scheduled**: [Count]\n- **Offers In Hand**: [Count]\n```\n\n---\n\n## Worked Example: Senior Infrastructure Engineer Transition\n\n- **Strategy**: Bypassed cold job boards. Built a target list of 25 companies using Kubernetes in production.\n- **Proof-of-Work**: Contributed a bug fix to the target company's open-source Terraform provider before reaching out.\n- **Outreach**: Messaged the author of the pull request on LinkedIn with a 3-sentence note referencing the fix.\n- **Outcome**: Secured direct VP of Engineering interview within 48 hours; received offer with 25% compensation increase in 3 weeks.\n\n---\n\n## Verification Checklist\n\n- [ ] Target account list is capped at 30 high-conviction companies categorized into Tiers 1–3.\n- [ ] Cold applications are prohibited for Tier 1 targets; warm intro or custom artifact is mandatory.\n- [ ] Outreach messages are strictly $\u003C 100$ words with zero generic flattery.\n- [ ] Weekly funnel stage conversion rates are calculated to diagnose drop-offs.\n- [ ] Salary expectations and minimum walk-away numbers are documented prior to initial screens.\n\n---\n\n## Anti-Patterns\n\n- **Volume Spam**: Spraying 50 resumes a day to random job posts without customizing a single bullet point.\n- **Passive Waiting**: Waiting for recruiters to discover an unoptimized LinkedIn profile.\n- **Skipping the Hiring Manager**: Relying solely on automated portal submissions rather than finding the engineering leader owning the role.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Career",1788652800000,"main","1f14747ac341265e37069290b22e87bc66e89e3f","skills\u002Fjob-search",0,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:47",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add poorvith-mp\u002Fskills-personal --skill job-search",{"tool":42,"command":43},"bunx","bunx skills add poorvith-mp\u002Fskills-personal --skill job-search",{"tool":45,"command":46},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-personal --skill job-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fjob-search\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Frouting.yaml","REFERENCE","参考文档",1021,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fjob-search\u002Fevals\u002Frouting.yaml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"job-search.skill","OTHER","其他",3870,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fjob-search\u002Fjob-search.skill",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M792T4GDF6W7QXDWNP84VE0K","voice-profile","Capture how you actually write: rhythm, vocabulary, structural habits, phrases you never use, and real samples. Use when analyzing writing voice, tone rules, rhythm, or anti-AI style.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fvoice-profile\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M792T0V505Q91SNSNN02WGRF","travel-planning","Build itineraries with daily schedules, accommodation and transport options and budget breakdowns. Use when planning trip itineraries, flights, travel logistics, or packing.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Ftravel-planning\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M792SY9CK4VJ5V87EX3A5191","travel-planner","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Ftravel-planner\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M792SWC86JAVXZBFW29YEWSA","second-brain-architect","Moved to note-system in skills-personal. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fsecond-brain-architect\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M792SR0VR1G543PG1PPAFE49","resume","Tailor a resume to a named job description with ATS-safe formatting and quantified achievement bullets. Use when crafting resumes, CVs, impact bullets, or ATS optimization.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fresume\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M792SMT6ESD9V46YM3JBDYFT","resume-optimizer","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-personal\u002Fblob\u002Fmain\u002Fskills\u002Fresume-optimizer\u002FSKILL.md",[],[]]