Add interview source notes on PhD-to-EdTech transition

Added comprehensive notes from a webinar with Brian Josh on transitioning from PhD to EdTech careers, covering hiring practices, interview processes, job titles, networking strategies, and industry trends.
mrdesouzaphd-cmyk · Jun 2, 2026 · Jun 2, 2026 · Jun 5, 2026 · Jun 5, 2026 · Jun 5, 2026
commit 58fa83bdd8168f01dc23fa27a88aa85435e9f7f8
diff --git a/brianjosh/references/interview-source.md b/brianjosh/references/interview-source.md
@@ -0,0 +1,202 @@
+# Brian Josh Interview: PhD-to-EdTech Career Coaching Source
+
+> Source: ~53-minute recorded webinar with Brian, a career-transition professional whose observations inform this skill. This is the primary reference for the BrianJosh skill.
+
+---
+
+## 1. Why PhDs Are Hired in EdTech
+
+- EdTech companies (like Khan Academy) hire PhDs for **disciplinary precision** — e.g., knowing that "most mitochondrial DNA" should be "about 60%" because the field has evolved. Undergrads might not catch that; PhDs do.
+- Art history, economics, history, humanities — not just STEM — all have PhDs in edtech because **nuance in content accuracy** matters.
+- Having a PhD is a **checkbox** for content-creation roles: it signals disciplinary depth without requiring external expert review.
+- Two PhDs (a professor and a curator) co-maintained Khan Academy's art history content. One PhD faculty member wrote the economics content.
+
+---
+
+## 2. Entry Points: Individual Contributor, Not Manager
+
+- Most PhDs entering edtech start at **individual contributor (IC) level** — responsible for their own work scope, with a manager overseeing them (similar to a PhD supervisor).
+- Brian entered Khan Academy at manager level because of unusual prior experience (running a team at Stanford, managing a large budget, supervising full-time staff) — this is **rare** for someone coming straight from a PhD.
+- For most candidates: expect IC roles first. Don't overpitch for management without that actual experience.
+
+---
+
+## 3. Interview Process and Portfolio
+
+- For content roles: the interview often includes **homework assignments** — e.g., "Write two questions on this topic and a 200-word accessible article on the same topic."
+- The homework tests **two things**: factual accuracy AND the ability to translate complex PhD-level ideas into clear, accessible language for broader audiences.
+- Portfolio tip: If you don't have a formal portfolio, look for examples from your teaching, seminar design, TA work, or any content you created where you made something accessible.
+
+---
+
+## 4. Job Titles: The Diversity Problem
+
+EdTech job titles are highly inconsistent — even within the same company. A role that designs a high school biology course could be listed as:
+- **Instructional Designer**
+- **Educator**
+- **Teacher**
+- **Subject Lead**
+- **Content Lead**
+- **Curriculum Manager / Curriculum Developer**
+- **Subject Matter Expert (SME)**
+
+> Brian: "We'll often post three versions of a job description under three separate titles and accept only one person."
+
+**Search strategy**: Search MULTIPLE titles when looking for the same type of role. Don't assume one title = one job. Use EdSurge (edtechspecific job board) in addition to LinkedIn and Indeed.
+
+Also search for:
+- Learning Designer
+- Learning Experience Designer (LXD)
+- eLearning Developer
+- Education Program Manager
+- Content Strategist (Education)
+- Learning & Development Specialist
+
+---
+
+## 5. Soft Skills Translation: The Key Move
+
+When communicating soft skills from a PhD to industry, the most important technique is **keyword mirroring from the job description**:
+
+1. Read the job description with a highlighter — find every soft skill word: "collaborate," "cross-functional," "highly matrixed," "communicate," "emotional intelligence."
+2. In your **cover letter**, use those exact words: "I'm excited about this role because in my time doing X, I leveraged my ability to [use the job description's exact language]."
+3. In your **CV/résumé**, don't just list the job title ("Program Manager for Lecture Series") — in the bullet descriptions, mirror the language from the job description.
+4. The goal: **make the hiring manager's job easy** by letting them see their own words reflected back.
+
+**PhD skills → industry language translations:**
+- Leading a seminar → Cross-functional meeting facilitation
+- Socratic teaching / discussion management → Stakeholder alignment across diverse teams
+- Co-designing a course with another faculty member → Cross-departmental collaboration
+- Organizing a conference across 5 departments → Matrixed project coordination
+- TA supervision → People management / mentoring
+- Managing a grant or lab budget → Resource allocation / financial oversight
+- Backward course design (start from learning objectives) → Instructional design principles (even without the title)
+
+---
+
+## 6. Experience vs. Expertise: A Critical Distinction
+
+Brian drew a sharp line between **expertise** (deep knowledge in a domain) and **experience** (time actually doing a specific job function):
+
+> "If you were a PhD student for seven years and TA'd for three semesters, that's not seven years of experience as an instructional designer. That's one and a half years of relevant experience — three semesters."
+
+**Rule of thumb**: When a job description asks for "5 years of program management experience" and you managed a seminar series for one semester, that's probably not the job for you right now. Be honest and strategic — apply for IC roles that match your actual functional experience, not your years of expertise.
+
+This also means: when writing your CV, don't claim "7 years of teaching experience" if you only TA'd for a year. Be precise about scope and duration.
+
+---
+
+## 7. Salary Strategy: Desubjectivize It
+
+Brian recommends removing personal financial goals entirely from the salary conversation. Instead:
+
+1. Research sites like **Payscale** and **PaySA** (sometimes spelled "PASA").
+2. Find equivalent roles at organizations of similar size, sector, and location.
+3. Location matters: San Francisco pays significantly more than Bozeman, Montana — same job, different cost of living.
+4. If your research shows the range is $90,000–$110,000, say: **"When I've looked at similar roles in this area on these salary research sites, the range I see is [X]. I'd expect something within that range."**
+
+Why this works:
+- It uses **objective market data**, not personal financial need.
+- It opens the door for the employer to either confirm ("Yes, we're in that range") or explain a difference ("We have exceptional benefits that offset a lower base").
+- It never puts you in the position of naming a number out of personal preference.
+
+---
+
+## 8. Nonprofit vs. For-Profit: Less Relevant Than You Think
+
+Brian suggests reframing the nonprofit vs. for-profit question entirely:
+
+Better questions to ask:
+- **Who does this organization serve?** Can users access it for free?
+- **What's the revenue model?** (Nonprofits also charge for things — College Board charges for SATs and AP exams.)
+- **Is this a high-performing or low-performing organization?** (High-performing nonprofits like Khan Academy operate with significant industry efficiency.)
+
+Key insight: High-performing edtech nonprofits often bring in talent from industry, run goal-setting on quarterly cycles, and operate with urgency. They can feel more like a fast-moving startup than an academic department.
+
+---
+
+## 9. Vendor / Contract Jobs: The Hidden Market
+
+Many edtech jobs don't appear on Apple's, Google's, or Microsoft's job boards because they're filled through **vendors and contractors**:
+
+- Large companies hire **vendors** to build and manage their educational content.
+- Those vendors hire subject matter experts (PhDs, teachers, curriculum specialists) on 1–5 year contracts.
+- If you're looking for edtech work at a major tech company, **search for the vendor layer** — the companies that create content for Apple, Google, Microsoft, Adobe — rather than going directly to the company's job board.
+- Contract work can start quickly ("We need someone, 40 hours/week, start next week, six-month contract").
+
+This is a major insight: the path into Google's or Microsoft's education ecosystem may go *through* a vendor, not directly through the company.
+
+---
+
+## 10. Networking Strategy: Light Touch, High Value
+
+Brian's LinkedIn networking approach:
+
+1. **Search LinkedIn's 1st and 2nd degree connections** at organizations you're interested in — you'll be surprised who you already know who works there.
+2. When reaching out to someone (especially a 2nd-degree connection): **keep the ask very light**.
+   - Bad ask: "Could we hop on a call for an hour and discuss the field?"
+   - Good ask: "I saw you worked at Khan Academy. I'm exploring edtech and had a specific question about [X role/team]. Would you be open to a 10-minute chat or even a quick email exchange?"
+3. Give them **an easy out** — acknowledge they're busy, keep your request specific.
+
+**EdSurge** (backed by the Gates Foundation) is specifically recommended:
+- Job board for edtech roles
+- Industry publication covering trends
+- Hosts in-person events that bring together educators, students, and industry in organic networking settings
+
+---
+
+## 11. Early-Career Strategy: Backward Design Your PhD
+
+For PhD students who know they want edtech careers:
+
+1. Attend events like this webinar to understand what job categories exist.
+2. Look at multiple job descriptions across instructional design, curriculum, content creation — find the **skills that appear consistently** (e.g., "data-driven decision making in instruction").
+3. Ask: "Where on campus can I get experience with this skill?" — Find TA opportunities, campus programs, student-facing projects that match.
+4. Seek internships or part-time roles that build the specific **experience** (not just expertise) the market wants.
+
+---
+
+## 12. Building EdTech Skills Without a Formal ID Background
+
+For PhDs who don't have formal instructional design (ID) training:
+
+- **LinkedIn Learning**: Short 20-minute courses on job functions you've never heard of (product marketing managers, LXDs, etc.) — useful for learning the language and logic of new roles.
+- **Claim your teaching as instructional design**: If you started with learning objectives, backward-designed your course, created assessments aligned to outcomes — that IS instructional design. You just called it teaching.
+  - In interviews: "You won't find the title 'instructional designer' in my history, but I've practiced instructional design principles throughout my teaching. I start with outcomes, backward design, and align assessments."
+- **Video skills**: Increasingly required in edtech. The ability to communicate clearly on video and use video as an effective instructional medium is becoming a must-have.
+
+---
+
+## 13. EdTech Trends to Know (From the Interview)
+
+Three major trends Brian identified:
+1. **Micro-learning / shortened content** — Rethinking how long educational experiences need to be. The 50-minute lecture is a historical artifact. Five-minute videos can deliver most of the learning.
+2. **Video as primary medium** — K-12 teachers and students increasingly prefer video over text. Anyone wanting to work in edtech needs video literacy.
+3. **Flipped / blended learning** — Learning basic content at home (via video), then using synchronous class time for discussions, hands-on activities, application. This model is reshaping what "classroom" means.
+
+---
+
+## 14. Key Job Boards and Resources
+
+- **EdSurge** (edsurge.com): EdTech-specific job board + industry publication + networking events
+- **LinkedIn**: Search jobs AND use for 2nd-degree network discovery
+- **Indeed**: General job board, useful for broad searches
+- **LinkedIn Learning**: Short courses for learning new job function language quickly
+- **Payscale / PaySA**: Salary research tools — use for objective market data
+- **Conference networking**: EdSurge events bring educators and industry together organically
+
+---
+
+## 15. Key Brian Quotes (Verbatim from Transcript)
+
+- "We would employ PhDs there because the level of precision that you know often teachers or students wouldn't know — it was sort of that built-in expert disciplinary expertise."
+- "Most folks, especially coming straight from a PhD, enter at what nonprofits and industry call the individual contributor level."
+- "If you were a PhD student for seven years and TA'd for three semesters, that's not seven years of experience — that's a year and a half."
+- "It's different from expertise. You might have had seven years building expertise, but it's not experience for that specific job."
+- "Read the job description really, really closely because for many companies, a lot of time went into choosing the specific bullet points and the specific words."
+- "Make the hiring manager's job easy to see, oh great, they're using the language I used in my job description."
+- "When I look at salary websites, these are the ranges I see. So if I had to guess, you are using these similar ranges."
+- "Desubjectivize it — don't say 'my personal expectations because of my financial goals are X.'"
+- "Those are the people that get stuff done in universities — and being able to translate that into another nonprofit or business environment, I found, usually makes people very excited."
+- "You won't find the title 'instructional designer' in the work I've done in the past, but I have done it. I've done it when I teach."
+- "[Vendor jobs] finding those opportunities doesn't look like looking on Apple and Google's job boards because you won't find them."