# Career Transition Pack **Prepared for:** PM with 6 years experience at a mid-stage fintech company **Date:** 2026-03-17 **Target paths:** Developer Relations (DevRel) vs. Product Marketing Management (PMM) at developer tools companies --- ## A) Current State + Constraints Snapshot **Current role/scope:** - Product Manager, 6 years experience, mid-stage fintech company - Likely owns a product area with cross-functional leadership across engineering, design, and data teams **Why change now (top pushes + pulls):** - *Pushes (inferred):* Desire for a role with more external-facing impact; possible ceiling on growth at current company; fintech may feel narrowing - *Pulls:* Strong writing portfolio (blog + internal docs); conference speaking experience (2 talks); attraction to developer tools ecosystem; interest in roles that leverage communication and technical empathy **Timeline:** - Decision date: End of 6-week experiment plan (approx. week of April 28, 2026) - Earliest start date for active job search: May 2026 (after experiments validate a path) **Constraints (must-haves / dealbreakers):** - Must remain fully remote - Compensation floor: $180k total (base + variable) - Bandwidth: 8 hours/week for transition work (while employed full-time) - No relocation **Bandwidth + runway:** - 8 hours/week = ~1.1 hrs/day or two 4-hour blocks on weekends - Currently employed; no financial urgency; can run a measured process **Assumptions/unknowns:** - *Assumption:* Currently employed and not at imminent risk of layoff - *Assumption:* Open to both IC and lead-level roles (not seeking people management immediately) - *Assumption:* "Strong writing portfolio" includes publicly accessible blog posts and potentially shareable internal documentation samples - *Unknown:* Exact current compensation (assumed near or above $180k given 6 YOE in fintech PM) - *Unknown:* Risk tolerance (assumed medium -- willing to experiment but not quit without a plan) - *Unknown:* Whether conference talks were technical or product-focused - *Unknown:* Depth of existing network in developer tools ecosystem --- ## B) Progress Metric + Push/Pull Map ### Progress Metric (next 12 months) **Primary:** Increase in external influence and community impact -- measured by the number of meaningful external interactions (talks, published content, community engagement) per month, growing from ~1/month today to 4+/month in the target role. **Secondary:** Learning rate in a new domain -- measured by ability to ship a proof artifact (talk, guide, campaign) in the developer tools space within 6 weeks. ### Push/Pull Map | Push (pain/friction) | Evidence | Pull (attraction) | Evidence | |---|---|---|---| | Limited external-facing work in current PM role | Conference talks and blog are side projects, not core job | DevRel: role *is* external communication + community building | Existing blog + 2 conference talks show natural fit | | Fintech domain may feel constraining long-term | Considering entirely different sectors (dev tools) | Developer tools ecosystem: fast-growing, mission-driven, remote-friendly | Many dev tools companies are remote-first and pay competitively | | PM work may feel too far from the "building" side | Internal docs suggest love of technical communication | PMM: translate product value into market narratives | Writing portfolio demonstrates ability to frame complex ideas clearly | | Desire for more creative autonomy over output | PM output is filtered through eng/design execution | Both paths offer more direct ownership of final artifact | DevRel owns talks/content; PMM owns positioning/campaigns | ### "Never Again" List 1. A role where writing and speaking are side projects rather than core responsibilities 2. A role with zero external visibility or community interaction 3. A company that requires full-time on-site presence --- ## C) Genie Goal + 10-Year Backcast ### Genie Goal (if success were guaranteed) "I would become a recognized voice in the developer tools space -- someone who helps developers succeed through content, community, and product storytelling. I'd combine my PM instincts (knowing what to build and why) with my communication strengths (writing, speaking) to shape how a developer tools company connects with its community." ### 10-Year Outcome (headline) "From PM to Head of Developer Experience: built the developer community strategy for a category-defining dev tools company, grew the community from thousands to hundreds of thousands, and became a trusted voice developers seek out." ### 3-Year Waypoint - Senior individual contributor or team lead in DevRel or PMM at a well-known developer tools company (e.g., Vercel, Supabase, Linear, Postman, Datadog tier) - Published 20+ substantive pieces of developer-facing content - Spoken at 6+ industry conferences or community events - Known within a specific developer niche as a go-to resource ### Next 12 Weeks (6 key moves) 1. **Weeks 1-2:** Complete 4-6 informational interviews across DevRel and PMM roles at dev tools companies 2. **Weeks 2-3:** Publish 1 developer-tools-adjacent blog post (repurpose PM expertise for a dev audience) 3. **Weeks 3-4:** Attend 2 developer community events or meetups (virtual counts); engage actively 4. **Weeks 4-5:** Complete a mini-project that simulates target role work (see Experiment Plan) 5. **Weeks 5-6:** Update scorecard with evidence from interviews and experiments; make a path decision 6. **Week 6:** Begin targeted outreach to 3-5 specific companies with proof artifacts in hand --- ## D) Target Archetypes + Fit Filters ### Archetype 1: Developer Advocate / Developer Relations Engineer **Role + environment:** - IC Developer Advocate at a Series B-D developer tools company (50-500 employees) - Creates technical content (tutorials, guides, sample apps), speaks at conferences, engages developer communities, feeds product insights back to the team - Remote-first; async-heavy culture; values clear writing **Fit signals (what would convince me it's a good fit):** - The team values writing quality and strategic thinking, not just code demos - DevRel has a seat at the product table (not just a marketing sub-function) - Manager has a background in DevRel or product (not pure marketing) - Success metrics include community health and product feedback loops, not just "content volume" - Existing conference speaking and blog writing are seen as strong assets during interviews **No-go signals:** - DevRel is treated as a support/ticket-deflection function - Role requires deep daily coding (e.g., building SDKs full-time) with no content/community component - Team is isolated from product decisions - Comp package is below $180k for someone with 6 YOE and PM background - Role requires >25% travel **Likely skill gaps:** - Hands-on developer tooling experience (may need to deepen technical credibility in a specific stack) - Community management at scale (Discord/forum moderation, metrics) - Creating technical tutorials with working code samples **First 3 people to talk to:** 1. A Developer Advocate at a mid-stage dev tools company (e.g., someone at Supabase, Railway, or Planetscale) 2. A DevRel manager/director who hires PM-to-DevRel converts 3. A PM who successfully transitioned into DevRel in the last 2 years --- ### Archetype 2: Product Marketing Manager (Developer-Focused) **Role + environment:** - PMM at a Series B-D developer tools company, focused on developer audience - Owns positioning, messaging, launch campaigns, competitive intelligence, and sales enablement for a developer product - Remote-first; cross-functional with product, sales, and developer relations teams **Fit signals (what would convince me it's a good fit):** - PMM is strategic (shapes positioning and GTM), not just "make the slides" - Close collaboration with product team (PM background is valued, not sidelined) - Developer audience means the work requires technical depth, not just marketing polish - Company has product-led growth motion (PLG) where PMM shapes the self-serve experience - Writing quality matters; not a "volume of MQLs" culture **No-go signals:** - PMM is a support function to sales with no product influence - Role is primarily event logistics and collateral production - No developer audience (generic B2B SaaS marketing) - Comp below $180k - Heavily metrics-driven on short-cycle lead gen (not aligned with progress metric of influence/impact) **Likely skill gaps:** - Formal GTM launch process and competitive analysis frameworks - Marketing analytics and attribution (MQL/PQL funnels, campaign ROI) - Sales enablement artifacts (battle cards, objection handling, win/loss analysis) **First 3 people to talk to:** 1. A PMM at a developer tools company (e.g., someone at Datadog, HashiCorp, or Vercel) 2. A Head of Product Marketing who has hired PMs into PMM roles 3. A PM-turned-PMM who can describe the day-to-day reality and adjustment curve --- ### Comparison: DevRel vs. PMM at a Glance | Dimension | DevRel (Archetype 1) | PMM (Archetype 2) | |---|---|---| | Primary audience | Developers (community) | Developers + buyers + internal teams | | Core output | Content, talks, community, product feedback | Positioning, launches, campaigns, enablement | | Leverages writing | Heavily (tutorials, blog, docs) | Heavily (messaging, case studies, web copy) | | Leverages speaking | Heavily (conferences, meetups, videos) | Moderately (webinars, sales kickoffs) | | PM skills transfer | Product thinking, user empathy, prioritization | Market analysis, positioning, cross-functional GTM | | Typical comp range (6 YOE, remote) | $160k-$220k (varies widely by company stage) | $170k-$230k (often includes variable/bonus) | | Career trajectory | Sr. Advocate -> Staff -> Head of DevRel/DX | Sr. PMM -> Group PMM -> Head/VP of PMM | | Risk factor | Some companies undervalue DevRel; org instability | Some PMM roles are glorified content production | --- ## E) Option Scorecard + Decision Rule ### Criteria + Weights | Criteria | Weight | DevRel (1-5) | PMM (1-5) | Notes | |---|---:|---:|---:|---| | **External influence + community impact** (primary progress metric) | 30% | 5 | 3 | DevRel is inherently community-facing; PMM influence is more indirect | | **Learning rate / new skill acquisition** | 20% | 4 | 4 | Both require new skills; DevRel = community + technical content; PMM = GTM + analytics | | **Leverage of existing strengths** (writing, speaking, PM) | 20% | 5 | 4 | DevRel directly uses writing + speaking; PMM uses writing + PM strategy but less speaking | | **Compensation meets floor ($180k+)** | 15% | 3 | 4 | Both achievable; PMM comp slightly more predictable at this level | | **Remote-first availability** | 10% | 5 | 4 | DevRel is overwhelmingly remote-first; PMM mostly remote but some companies prefer hybrid | | **Long-term career optionality** | 5% | 4 | 4 | Both open doors; DevRel -> DX/Product; PMM -> CMO/VP Marketing path | | **Weighted Score** | 100% | **4.45** | **3.70** | DevRel leads on primary metric; PMM is strong alternative | ### Decision Rule "I will choose the path that scores highest on the scorecard **after** completing at least 3 informational interviews per archetype and 1 proof-artifact experiment per path. If the weighted scores are within 0.5 points of each other after evidence gathering, I will choose the path where my informational interviews produced the strongest 'I could see myself doing this daily' signal. I will make this decision by **April 28, 2026**." ### Top Unknowns + How to Resolve | Unknown | Resolution method | Target date | |---|---|---| | 1. Day-to-day reality of DevRel (is it content factory or strategic?) | 3+ informational interviews with DevRel ICs | Weeks 1-3 | | 2. Whether PM experience is valued or discounted in DevRel hiring | Talk to 1-2 DevRel hiring managers | Weeks 2-3 | | 3. Actual comp ranges for PM-to-PMM/DevRel converts at target companies | Ask directly in informational interviews; check levels.fyi | Weeks 1-4 | | 4. Whether my technical depth is sufficient for DevRel | Attempt a technical tutorial as a proof artifact; get feedback | Weeks 3-5 | | 5. Whether PMM at dev tools companies is strategic or execution-heavy | 3+ informational interviews with dev tools PMMs | Weeks 1-3 | --- ## F) Opportunity Pipeline Plan ### Target People List (20 contacts) **DevRel track (10 people):** 1. Developer Advocate at a target company (find via Twitter/X, dev.to, or company blog bylines) 2. Developer Advocate at a second target company 3. Head of DevRel at a mid-stage dev tools company 4. PM-to-DevRel convert (search LinkedIn for "former product manager" + "developer advocate") 5. DevRel hiring manager at a company currently hiring 6. Conference organizer from a conference you've spoken at (warm connection) 7. Developer community leader (Discord/Slack community moderator for a dev tools community) 8. Technical writer at a dev tools company (adjacent role; can describe the content culture) 9. A developer advocate you follow and admire on social media 10. An ex-colleague who now works at a dev tools company (any role -- for warm intro) **PMM track (10 people):** 1. PMM at a developer tools company 2. PMM at a second developer tools company 3. Head of Product Marketing at a dev tools company 4. PM-to-PMM convert (search LinkedIn) 5. PMM hiring manager at a company currently hiring 6. Content marketer at a dev tools company (adjacent role) 7. Sales/solutions engineer at a dev tools company (understands what PMM enables) 8. A PMM whose positioning work you admire (e.g., someone behind a great dev tools landing page) 9. A recruiter specializing in marketing roles at tech companies 10. An ex-colleague in any marketing-adjacent role for a warm intro ### Weekly Cadence (8 hours/week budget) | Activity | Time/week | Details | |---|---|---| | Outreach messages (new) | 1.5 hrs | Send 4-5 personalized messages (LinkedIn, email, Twitter DM) | | Informational interviews | 2 hrs | 1-2 calls per week (20-30 min each + prep + notes) | | Content creation / proof artifacts | 3 hrs | Blog post, tutorial, or positioning exercise | | Community engagement | 1 hr | Participate in 1-2 dev tools communities (Discord, Twitter, forums) | | Pipeline tracking + reflection | 0.5 hrs | Update tracker; capture learnings; adjust plan | ### Tracking Method Simple spreadsheet or Notion table with these fields: | Name | Role | Company | Channel | Status | Date Contacted | Response | Interview Date | Key Insight | Follow-Up | |---|---|---|---|---|---|---|---|---|---| | (fill in) | | | LinkedIn/Email/DM | Not contacted / Awaiting / Scheduled / Complete | | | | | | ### Next 7 Days (scheduled actions) 1. **Day 1 (Mon):** Build initial pipeline list -- identify 10 specific people by name using LinkedIn and Twitter search. Save to tracker. 2. **Day 2 (Tue):** Send 3 outreach messages (2 DevRel, 1 PMM) using scripts below. 3. **Day 3 (Wed):** Join 2 developer tools community Discords/Slacks (e.g., Supabase Discord, Vercel community, or a DevRel-specific community like DevRel Collective). 4. **Day 4 (Thu):** Send 2 more outreach messages (1 DevRel, 1 PMM). 5. **Day 5 (Fri):** Research 5 target companies (developer tools, remote-first, Series B-D, currently hiring DevRel or PMM). Note comp data from levels.fyi and job postings. 6. **Day 6 (Sat):** Begin outlining proof artifact #1 -- a developer-facing blog post that bridges your fintech PM expertise with a dev tools audience (e.g., "What fintech taught me about developer experience"). 7. **Day 7 (Sun):** Review pipeline tracker; prep questions for any scheduled interviews next week. ### Outreach Scripts **Script 1: Informational Interview Request (DevRel)** > Subject: Quick question about your DevRel work at [Company] > > Hi [Name] -- I'm a PM with 6 years of experience exploring a move into developer relations at a developer tools company. I've been writing a technical blog and have spoken at a couple of conferences, and I'm trying to understand what DevRel actually looks like day-to-day versus what I imagine from the outside. > > Would you be open to a 20-minute chat in the next two weeks? I'd love to hear how you spend a typical week and what you'd do differently if you were breaking into DevRel today. If a call doesn't work, I'm happy to send 3 specific questions by email instead. > > Thanks, > [Your name] **Script 2: Informational Interview Request (PMM)** > Subject: Quick question about PMM at a dev tools company > > Hi [Name] -- I'm a Product Manager (6 YOE, fintech) considering a transition into product marketing at a developer tools company. Your work on [specific campaign/launch/positioning you noticed] caught my attention. > > I'd love to understand how PMM at a dev tools company differs from what I'd expect coming from a product background -- especially the day-to-day work and how much of it is strategic vs. execution. > > Would you have 20 minutes in the next couple of weeks? Happy to work around your schedule, or I can send a few targeted questions by email if that's easier. > > Thanks, > [Your name] **Script 3: Follow-Up / Thank You + One Ask** > Hi [Name] -- thanks again for the conversation today. The part about [specific insight they shared] was especially helpful and gave me a clearer picture of [what you learned]. > > One quick follow-up: is there 1-2 people you'd recommend I talk to who could help me understand [specific unknown you're trying to resolve]? Happy to mention you introduced us. > > Thanks again -- I'll keep you posted on how things evolve. > [Your name] **Script 4: Warm Intro Request (to an ex-colleague at a dev tools company)** > Hi [Name] -- hope things are going well at [Company]! I'm exploring a career move into [DevRel / PMM] in the developer tools space, and I noticed [Company] has been doing great work in [specific area]. > > Would you be comfortable introducing me to someone on the [DevRel / Marketing] team for a quick informational chat? I'm not asking about open roles yet -- just trying to understand the space better before I commit to a direction. > > Totally understand if the timing isn't right. Either way, would love to catch up soon. > [Your name] --- ## G) Skills & Proof Plan ### Top 5 Gaps + Learning Plan | Gap | Relevance | Learning Sprint | Proof Artifact | Feedback Loop | |---|---|---|---|---| | 1. **Technical tutorial writing** (DevRel) | Core DevRel deliverable; demonstrates ability to teach developers | Weeks 2-4: Write 1 hands-on tutorial using a developer tool (e.g., build something with Supabase, Vercel, or an API product) | Published tutorial on personal blog or dev.to | Share with 2 DevRel practitioners for feedback | | 2. **Developer community engagement** (DevRel) | Shows ability to build relationships in dev communities | Weeks 1-6: Active participation in 2 dev tools communities; answer questions, share resources | Documented community contributions (screenshots, links); 10+ meaningful interactions | Track engagement metrics; ask community members for feedback | | 3. **Product positioning exercise** (PMM) | Core PMM deliverable; demonstrates strategic marketing thinking | Weeks 3-5: Write a positioning document for a real dev tool (pick a product you admire; do the exercise as if you were their PMM) | 1-page positioning doc (target audience, value prop, competitive differentiation, messaging pillars) | Share with 1-2 PMMs for feedback during informational interviews | | 4. **GTM launch understanding** (PMM) | Key PMM competency; your PM experience gives you 60% of this but you need the marketing lens | Weeks 2-4: Study 3 recent dev tools launches (read launch blogs, Product Hunt pages, Twitter threads); deconstruct what the PMM likely did | Written analysis of 1 launch ("PMM teardown") posted as a blog or shared in informational interviews | Review with a PMM contact | | 5. **Public narrative: "Why I'm making this transition"** (Both) | Hiring managers will ask; your answer must be crisp and compelling | Week 1-2: Write a 500-word narrative connecting PM experience -> target role; refine through conversations | Polished "About my transition" paragraph usable in outreach, interviews, and LinkedIn | Test in informational interviews; refine based on reactions | ### Existing Strengths to Leverage (Portfolio) - Blog writing portfolio (directly applicable to both paths) - 2 conference talks (strong signal for DevRel; useful for PMM credibility) - Internal documentation skills (translates to technical writing, positioning docs, enablement content) - 6 years of PM experience (product thinking, user empathy, cross-functional leadership) - Fintech domain expertise (valuable if targeting dev tools in the payments/financial infrastructure space, e.g., Stripe, Plaid, Unit) --- ## H) Experiment Plan (6 Weeks) ### Overview | Week | Focus | Hours | Key Deliverable | |---|---:|---|---| | 1 | Pipeline setup + first outreach | 8 | Pipeline tracker populated; 5 messages sent; 1 blog outline started | | 2 | Informational interviews begin + first proof artifact | 8 | 2 interviews completed; transition narrative drafted | | 3 | Deepen interviews + DevRel proof artifact | 8 | 2 more interviews; technical tutorial draft complete | | 4 | PMM proof artifact + community engagement | 8 | Positioning exercise complete; 1 PMM teardown posted | | 5 | Final interviews + scorecard update | 8 | 2 more interviews (6+ total); scorecard updated with evidence | | 6 | Decision + next steps | 8 | Decision made; targeted outreach to 3-5 companies begun | ### Detailed Experiments --- **Experiment 1: Informational Interview Sprint** - **Goal:** Resolve unknowns about day-to-day reality, hiring criteria, and comp for both paths - **Steps:** 1. Identify and contact 10+ people (5 DevRel, 5 PMM) in weeks 1-2 2. Conduct 6-8 interviews over weeks 2-5 (target: 3+ per archetype) 3. Use a standard question set: (a) Walk me through a typical week, (b) What does success look like in your first 6 months, (c) What would you do differently breaking in, (d) What's the comp range for someone with my background, (e) What's the biggest misconception about this role 4. After each interview, update the pipeline tracker with key insights 5. After every 3 interviews, update the option scorecard - **Pass signal:** After 6+ interviews, I can clearly articulate the day-to-day difference between DevRel and PMM, and my scorecard scores have moved based on evidence (not assumptions) - **Fail signal:** After 6 interviews, I still can't distinguish the paths or my scores haven't changed -- indicates I'm asking the wrong questions or talking to the wrong people - **Timeline:** Weeks 1-5 --- **Experiment 2: DevRel Proof Artifact (Technical Tutorial)** - **Goal:** Test whether I enjoy and can produce DevRel-quality technical content - **Steps:** 1. Choose a developer tool I find interesting (week 2) 2. Build something small with it -- a mini-project or integration (week 2-3) 3. Write a tutorial walking through the process, aimed at a developer audience (week 3-4) 4. Publish on personal blog and cross-post to dev.to (week 4) 5. Share with 2 DevRel practitioners for honest feedback (week 4-5) - **Pass signal:** I enjoyed the process; the tutorial is coherent and received positive feedback from at least 1 DevRel practitioner; I want to do more of this - **Fail signal:** The process felt tedious; feedback indicates the technical depth is insufficient; I dreaded writing it - **Timeline:** Weeks 2-4 - **Scorecard update:** Directly updates "External influence" and "Leverage of existing strengths" scores for DevRel --- **Experiment 3: PMM Proof Artifact (Positioning Exercise)** - **Goal:** Test whether I enjoy and can produce PMM-quality strategic marketing work - **Steps:** 1. Select a real developer tool product (ideally one I've used as a PM) (week 3) 2. Research the competitive landscape, target audience, and current positioning (week 3) 3. Write a 1-page positioning document: target persona, core value prop, 3 messaging pillars, competitive differentiation (week 3-4) 4. Share with 1-2 PMM contacts from informational interviews for feedback (week 4-5) - **Pass signal:** I enjoyed the strategic framing; feedback says the positioning is clear and actionable; I can see myself doing this for different products - **Fail signal:** I found it abstract and disconnected from users; feedback says it reads like a PM spec, not marketing positioning - **Timeline:** Weeks 3-5 - **Scorecard update:** Directly updates "External influence" and "Leverage of existing strengths" scores for PMM --- **Experiment 4: Community Immersion** - **Goal:** Test whether I naturally engage in developer communities (key for DevRel; useful for PMM) - **Steps:** 1. Join 2-3 developer tools communities: DevRel Collective Slack, a product-specific Discord (e.g., Supabase, Vercel), and Twitter/X dev tools conversations (week 1) 2. Spend 1 hour/week engaging: answer questions, share useful resources, comment on threads (weeks 1-6) 3. Track interactions: number of meaningful contributions, connections made, insights gained - **Pass signal:** After 4 weeks, I've made 10+ meaningful contributions and 3+ genuine connections; I look forward to the community time - **Fail signal:** It feels performative; I dread the engagement; contributions don't come naturally - **Timeline:** Weeks 1-6 (ongoing) - **Scorecard update:** Updates "External influence" score for DevRel; updates "Learning rate" for both paths --- **Experiment 5: Comp Validation** - **Goal:** Confirm that $180k+ is achievable for PM-to-DevRel or PM-to-PMM transitions at target companies - **Steps:** 1. Research levels.fyi, Glassdoor, and Blind for DevRel and PMM comp at target companies (week 1) 2. Ask about comp ranges directly in informational interviews (ongoing) 3. If possible, get a signal from 1 recruiter on realistic ranges for a 6 YOE PM converting (week 3-4) - **Pass signal:** 3+ data points confirm $180k+ is standard for the target role/level at target company stage - **Fail signal:** Data suggests $180k requires senior/staff level that may not be accessible for a career changer - **Timeline:** Weeks 1-4 - **Scorecard update:** Directly updates "Compensation" score for both archetypes --- ### Week-by-Week Schedule **Week 1 (Mar 17 - Mar 23)** - [ ] Build pipeline tracker (Day 1) - [ ] Identify 10 specific people by name for outreach (Day 1-2) - [ ] Send 5 outreach messages (Day 2-5) - [ ] Join 2 developer tools communities (Day 3) - [ ] Begin comp research on levels.fyi (Day 5) - [ ] Outline blog post / transition narrative (Day 6-7) - [ ] Research 5 target companies (Day 5-6) **Week 2 (Mar 24 - Mar 30)** - [ ] Conduct 2 informational interviews - [ ] Send 3-5 follow-up or new outreach messages - [ ] Draft "why I'm making this transition" narrative (500 words) - [ ] Choose developer tool for tutorial experiment; begin building mini-project - [ ] 1 hour community engagement - [ ] Update pipeline tracker **Week 3 (Mar 31 - Apr 6)** - [ ] Conduct 2 informational interviews (aim for 1 DevRel + 1 PMM) - [ ] Complete technical tutorial draft - [ ] Begin positioning exercise: select product, research competitive landscape - [ ] Send 3 new outreach messages - [ ] 1 hour community engagement - [ ] First scorecard evidence update (after 4 interviews) **Week 4 (Apr 7 - Apr 13)** - [ ] Conduct 1-2 informational interviews - [ ] Publish technical tutorial on blog + dev.to - [ ] Complete positioning document - [ ] Share both proof artifacts with relevant contacts for feedback - [ ] Comp validation checkpoint: compile data from interviews + research - [ ] 1 hour community engagement **Week 5 (Apr 14 - Apr 20)** - [ ] Conduct final 1-2 informational interviews (6+ total) - [ ] Collect and synthesize feedback on both proof artifacts - [ ] Full scorecard update with all evidence - [ ] Write "PMM teardown" of a recent dev tools launch (optional bonus artifact) - [ ] 1 hour community engagement - [ ] Reflect: which proof artifact did I enjoy more? Which felt like "home"? **Week 6 (Apr 21 - Apr 28)** - [ ] Final scorecard review: update all scores with evidence - [ ] Apply decision rule: compare weighted scores; if within 0.5, use "daily reality" gut check - [ ] Write decision memo (1 page: "I'm choosing [X] because [evidence]") - [ ] Identify 3-5 specific companies to target for applications - [ ] Send 3 warm outreach messages to contacts at target companies (shift from informational to opportunity-focused) - [ ] Update LinkedIn headline, summary, and portfolio to reflect chosen path - [ ] Schedule next 4 weeks of focused job search activity --- ## I) Risks / Open Questions / Next Steps ### Risks | Risk | Likelihood | Mitigation | |---|---|---| | DevRel comp at smaller companies falls below $180k floor | Medium | Target Series B+ companies; negotiate with total comp lens (equity); validate in interviews | | PM-to-DevRel transition is discounted by hiring managers ("not technical enough") | Medium | Proof artifacts (tutorial) + conference talks offset this; target companies that value PM-to-DevRel converts | | 8 hours/week is not enough to run all experiments | Low-Medium | Prioritize experiments 1 and 2/3 (interviews + one proof artifact); drop experiment 4 to a lighter touch if needed | | Current employer discovers job search activity | Low | Keep activity external (personal blog, personal LinkedIn); do informational interviews outside work hours | | Both paths score similarly after 6 weeks; decision paralysis | Medium | Decision rule includes a tiebreaker (daily-reality gut check); worst case: pick one for 3 months and course-correct | | Developer tools market cools; fewer open roles | Low | DevRel and PMM are growing categories; diversify across 5+ companies; keep current job as fallback | ### Open Questions 1. **How technical does my tutorial need to be for DevRel credibility?** -- Resolve via informational interviews and artifact feedback (weeks 2-4) 2. **Do I prefer the strategic framing of PMM or the community-facing nature of DevRel?** -- Resolve via proof artifact experiments (weeks 3-5) 3. **Are there hybrid roles (e.g., "Developer Marketing Manager") that combine both?** -- Ask about in informational interviews 4. **Would a fintech dev tools company (Stripe, Plaid, Unit) be the ideal bridge?** -- Research and add to target company list 5. **Is my conference speaking experience recent and strong enough to be a competitive advantage?** -- Get feedback from a DevRel hiring manager ### Stop Doing List (what NOT to pursue right now) - Do not apply to any roles until week 6 (premature applications waste signal) - Do not pursue a management-track transition (stay focused on IC/senior IC paths) - Do not invest in paid courses or certifications (proof artifacts beat credentials) - Do not try to network in more than 2-3 communities (depth over breadth) - Do not quit your current job or reduce hours before the 6-week experiment concludes ### Next Steps (next 7 days) 1. **Today:** Create a pipeline tracking spreadsheet with the fields listed above 2. **Day 1-2:** Identify 10 specific people by name for initial outreach using LinkedIn search 3. **Day 2-3:** Send first 3 outreach messages using the scripts in this pack 4. **Day 3:** Join DevRel Collective Slack and one product-specific developer community Discord 5. **Day 4-5:** Send 2 more outreach messages; begin researching target companies 6. **Day 6:** Start outlining your first proof artifact (blog post bridging fintech PM -> dev tools) 7. **Day 7:** Review pipeline tracker; prepare for any interviews scheduled for week 2 --- ## Quality Gate Self-Assessment ### Rubric Scores | Dimension | Score (0-2) | Rationale | |---|---|---| | **Clarity** | 2 | Crisp progress metric (external influence + learning rate), explicit constraints with dates, clear decision rule with evidence requirements and deadline (April 28) | | **Options quality** | 2 | 2 distinct archetypes with specific fit signals, no-go signals, and tailored rationale; comparison table makes trade-offs explicit | | **Evidence + de-risking** | 2 | 5 experiments sequenced over 6 weeks, mapped to top unknowns, each with pass/fail criteria and explicit scorecard update mechanism | | **Pipeline realism** | 2 | 20-person target list with categories, weekly cadence within 8-hour budget, 4 ready-to-send outreach scripts, next 7 days fully scheduled | | **Execution fit** | 2 | Plan fits 8 hrs/week; week 1 is fully specified; "stop doing" list included; experiments prioritized by leverage | | **Total** | **10/10** | Passing bar: >= 7/10 | ### Checklist Verification **Structural:** All 9 deliverables present (snapshot, push/pull, backcast, archetypes, scorecard, pipeline, skills/proof, experiments, risks/open/next). Constraints and timeline explicit. Assumptions listed. Scorecard weighted. Outreach cadence with next-7-days actions. **Decision-quality:** 2 archetypes (not a giant list). Each has fit and no-go signals. Decision rule states evidence required. Plan respects 8 hrs/week. "Stop doing" list included. **Experiment:** Each experiment has goal, steps, pass/fail signal. Experiments resolve biggest unknowns first. Learnings update scorecard. Next 2 weeks include conversations and proof artifact work. **Safety + ethics:** No confidential employer information requested. No irreversible decisions recommended. Plan maintains current employment throughout.