Free lesson · The Job Search System
What Is a Discoverability Stack?
What Is a Discoverability Stack?
Student: Swati, in the last module you kept using this phrase - "discoverability stack." You said my resume, LinkedIn, GitHub, portfolio, and network all need to work together. Can you break that down? What exactly is a discoverability stack, and why does it matter?
Swati: Okay, let me start with something I've observed across hundreds of candidates I've either hired, coached, or watched fail.
Most engineers think of their job search materials as a collection of separate things. Resume is one thing. LinkedIn is another. GitHub is over there somewhere. Portfolio maybe exists, maybe doesn't. Network is something they think about when they're desperate.
The problem with that mental model is that these things aren't separate. They're a system. They work together - or they don't work at all. A recruiter who finds your LinkedIn profile and clicks through to your GitHub and sees nothing? That's a signal. A hiring manager who reads your resume, Googles your name, and finds no portfolio, no blog, no evidence of your work beyond bullet points? That's a signal too. And silence - the absence of presence - is a negative signal, not a neutral one.
Student: What do you mean by "negative signal"?
Swati: I mean that in the absence of evidence, people fill in the blanks with assumptions. And the assumptions are almost never in your favor. If a recruiter can't find you on LinkedIn, they don't think "this person values privacy." They think "this person isn't serious about their career." If your GitHub is empty, they don't think "this person does all their work in private repos." They think "this person doesn't code outside of work." Are those assumptions fair? No. Are they real? Absolutely.
So a discoverability stack is the complete set of signals you put into the world that allow recruiters, hiring managers, referral contacts, and opportunity to find you and form a positive impression of you. It's five layers, and each layer does a different job.
The Five Layers
Let me lay out the five layers, what each one does, and how they interact.
graph TD
A["Layer 1: RESUME<br/>Your controlled narrative<br/>Sent directly to companies"] --> B["Layer 2: LINKEDIN<br/>Your search engine<br/>How recruiters find you"]
B --> C["Layer 3: GITHUB<br/>Your proof of work<br/>Evidence you can build"]
C --> D["Layer 4: PORTFOLIO<br/>Your showcase<br/>Projects with context and impact"]
D --> E["Layer 5: NETWORK<br/>Your amplifier<br/>People who vouch for you"]
E -->|"Referrals send<br/>your resume"| A
B -->|"Recruiter checks<br/>your GitHub"| C
A -->|"Hiring manager<br/>Googles you"| D
style A fill:#ff6b6b,color:#fff
style B fill:#339af0,color:#fff
style C fill:#51cf66,color:#fff
style D fill:#fcc419,color:#000
style E fill:#7950f2,color:#fff
This diagram shows the five layers of the discoverability stack arranged vertically. Layer 1 is Resume, your controlled narrative sent directly to companies. Layer 2 is LinkedIn, your search engine and how recruiters find you. Layer 3 is GitHub, your proof of work and evidence you can build. Layer 4 is Portfolio, your showcase with projects in context. Layer 5 is Network, your amplifier through people who vouch for you. Arrows show cross-layer interactions: referrals from your network send your resume, recruiters who find you on LinkedIn check your GitHub, and hiring managers who read your resume Google you and find your portfolio.
Layer 1: Resume - Your Controlled Narrative
Your resume is the one document you have complete control over. It's what you send when you apply. It's what your referral attaches to their internal recommendation. It's what the hiring manager prints out before your interview.
The resume's job is to tell a specific, targeted story about your professional identity in a format that survives ATS parsing, recruiter skimming, and hiring manager evaluation. We covered in Module 00 how each of those stages works. Module 02 is entirely about building a resume that wins at all three.
Student: Is the resume still the most important piece? I keep hearing that "resumes are dead" and it's all about LinkedIn now.
Swati: Resumes are not dead. That's marketing copy from people selling LinkedIn courses. Every company I've hired for - Yahoo, LinkedIn (ironically), Stripe, Google - requires a resume. It's the universal document. LinkedIn is where you get found, but the resume is what gets evaluated. They serve different functions.
That said, the resume is necessary but not sufficient. A perfect resume with no LinkedIn presence, no GitHub, and no network is a package sitting in a warehouse with no shipping address. It exists, but it's not going anywhere.
Layer 2: LinkedIn - Your Search Engine
I explained in Module 00 how recruiters use LinkedIn Recruiter to search for candidates using Boolean queries and filters. Your LinkedIn profile is not a social media presence - it's a search engine listing. Every keyword in your headline, summary, experience, and skills section is an indexable term.
The resume is what you push out. LinkedIn is what pulls opportunity in. When you're not actively applying, your LinkedIn profile is still working - recruiters are still searching, still browsing, still building shortlists. A strong LinkedIn profile means you receive opportunities you never applied for. A weak one means you're invisible to the entire passive recruitment channel.
Student: And those two channels - inbound from LinkedIn and outbound through applications - they're different?
Swati: Very different, and the conversion rates are dramatically different. Let me show you:
| Channel | How It Works | Typical Conversion to Interview |
|---|---|---|
| Cold application (resume only) | You apply through a career page | 2–5% |
| Cold application + referral | Employee submits your resume internally | 15–30% |
| Recruiter finds you on LinkedIn | They reach out via InMail | 25–40% |
| Warm introduction through network | Someone connects you to hiring manager | 30–50% |
These numbers aren't precise for every company but they reflect the pattern I've seen consistently across 14 years and four companies. The channels where you are discovered or introduced convert massively better than the channels where you apply cold into a pile.
Your discoverability stack exists to maximize the probability that Channels 2, 3, and 4 are active - not just Channel 1.
Layer 3: GitHub - Your Proof of Work
For engineers specifically, GitHub serves a function that no other profession has an equivalent for. It's public, verifiable evidence that you can build things. Your resume says you built a payment processing system - your GitHub can show the code.
Student: But most of my work is in private repos at my company. I can't share proprietary code.
Swati: That's the case for most working engineers, and it's not a disqualifier. GitHub doesn't need to contain your employer's codebase. It needs to contain something - personal projects, open source contributions, even well-documented solutions to coding challenges. The point isn't to prove you wrote production code at your company. The point is to show that you care enough about engineering to write code outside of the 9-to-5. It's a credibility signal, not a portfolio replacement.
That said, GitHub's importance varies by career stage. For a new grad with no work experience, GitHub is critical - it might be the primary evidence of your skills. For a senior engineer with 10 years of experience and a strong resume, GitHub is a nice-to-have. We'll get into this in Topic 03 of this module.
Layer 4: Portfolio - Your Showcase
A portfolio is where you show completed projects with context - not just code, but the problem you solved, the decisions you made, the results you achieved. Think of it as a case study format for your engineering work.
Student: Is a portfolio the same as GitHub?
Swati: No, and this is a distinction a lot of engineers miss. GitHub shows how you build. A portfolio shows what you built and why it matters. A recruiter looking at your GitHub might see a React app repository with 50 files. Cool, but what does it do? Why did you build it? What problems did you solve? A portfolio page for that same project would show a screenshot, a one-paragraph description of the problem, a technical overview of the approach, and a result or metric.
Some engineers host this on a personal website. Some use a well-written GitHub README. Some use a Notion page. The format matters less than the content. What matters is that somewhere, publicly accessible, there's a narrative version of your technical work.
Layer 5: Network - Your Amplifier
Your network is the human layer that amplifies everything else. A great resume is 10 times more effective when someone hand-delivers it with a personal recommendation. A LinkedIn profile is 10 times more effective when people in your network engage with your posts, endorse your skills, and think of you when they hear about openings.
Student: I feel like networking is the one thing everyone tells you to do but nobody teaches you how.
Swati: You're not wrong. "Network more" is the "eat healthy" of career advice - true but useless without specifics. Module 06 is entirely about how to network as an engineer, including how to ask for referrals without being awkward, how to do cold outreach that actually gets responses, and how to network when you're an introvert who would rather debug code than make small talk.
But for now, the key insight is this: your network is not a nice-to-have addition to your stack. It's the layer that makes all other layers work harder. Without it, you're relying entirely on machines (ATS) and strangers (recruiters) to evaluate you. With it, you have people who know your work and will actively advocate for you.
How the Layers Work Together
Student: So each layer does something different, but they all connect. Can you show me how they interact in a real scenario?
Swati: Yes. Let me walk you through two scenarios - one where the stack is broken and one where it works.
Scenario 1: Broken Stack. You apply to a company cold. Your resume is decent but not tailored. The ATS parses it, scores it medium. The recruiter sees it in the queue, glances for 6 seconds. Your LinkedIn is sparse, so there's no supporting evidence. Your GitHub is empty. You have no referral. Result: no response. You're one of 300 names in a spreadsheet.
Scenario 2: Working Stack. You apply to the same company, but this time: your resume is tailored to the JD using AlgoInsight's AI Resume Builder. Your LinkedIn is keyword-optimized, so the recruiter has already seen your profile in a search last week. Your GitHub has three well-documented projects relevant to the role. And a former colleague at the company submitted a referral for you with a note saying "she's the best engineer I've ever worked with." Result: the recruiter recognizes your name from LinkedIn, reads your resume fully because of the referral, checks your GitHub and sees real work, and schedules a phone screen within 48 hours.
Same person. Same skills. Same company. Completely different outcome.
graph LR
subgraph "Broken Stack"
A1["Resume ⚠️<br/>Not tailored"] --> B1["ATS<br/>Medium score"]
B1 --> C1["Recruiter<br/>6-sec glance"]
C1 --> D1["No LinkedIn<br/>to verify"]
D1 --> E1["❌ No response"]
end
subgraph "Working Stack"
A2["Resume ✅<br/>Tailored + ATS-optimized"] --> B2["ATS<br/>High score"]
B2 --> C2["Recruiter<br/>Full read"]
C2 --> D2["LinkedIn ✅<br/>Already seen profile"]
D2 --> E2["GitHub ✅<br/>Relevant projects"]
E2 --> F2["Referral ✅<br/>Internal advocate"]
F2 --> G2["✅ Phone screen<br/>within 48 hours"]
end
style E1 fill:#ff6b6b,color:#fff
style G2 fill:#51cf66,color:#fff
This diagram compares two scenarios side by side. The broken stack scenario: an untailored resume gets a medium ATS score, the recruiter gives it a 6-second glance, there's no LinkedIn to verify the candidate, and the result is no response. The working stack scenario: a tailored, ATS-optimized resume gets a high ATS score, the recruiter does a full read, they recognize the candidate from LinkedIn, check GitHub and see relevant projects, a referral provides an internal advocate, and the result is a phone screen within 48 hours.
Student: That's stark. So it's not that any single layer is magic - it's that they multiply each other?
Swati: Exactly. I think of it as a multiplication equation, not an addition equation:
Outcome = Resume × LinkedIn × GitHub × Portfolio × Network
If any one of those is zero, the product is zero. A world-class resume with no network and no LinkedIn presence gives you: world-class resume × 0 × 0 = 0. But even a decent resume with a solid LinkedIn, some GitHub presence, and one strong referral gives you: decent × solid × some × 1 × strong = a real chance.
Important: The multiplication principle of discoverability. Your job search materials don't add to each other - they multiply. A zero in any critical layer collapses the entire stack. Before you spend 40 hours perfecting your resume, make sure your LinkedIn isn't a zero. Before you obsess over GitHub, make sure you have at least one person who could refer you somewhere. Balance beats perfection.
The Common Failure Patterns
Student: What are the most common ways people's stacks are broken?
Swati: I see four patterns repeatedly:
Pattern 1: Resume-only candidate. They have a great resume and nothing else. No LinkedIn, empty GitHub, no portfolio, no network. They apply cold to everything and wonder why the response rate is 2%. The resume is strong but there's nothing to amplify it.
Pattern 2: LinkedIn-heavy, resume-light. They have a beautiful LinkedIn profile with a great headline and detailed experience. But their actual resume - the document that gets sent to the ATS - is outdated, poorly formatted, and not tailored. They get recruiter InMails but fail to convert because the resume doesn't match the promise of the LinkedIn profile.
Pattern 3: GitHub-only engineer. They have 50 repositories, daily green squares, and contributions to open source. But no LinkedIn, no resume worth speaking of, and no network. Recruiters never find them because recruiters don't search GitHub - they search LinkedIn. The proof of work exists but nobody sees it.
Pattern 4: Network-only candidate. They know people, they get referrals, but their resume is weak and their online presence is thin. The referral gets them past the initial filter, but the hiring manager Googles them, finds nothing, and forms a lukewarm impression before the interview even starts.
Warning: The most dangerous failure pattern is number 1 - the resume-only candidate. Not because their resume is bad, but because they feel productive. They're applying to 20 jobs a week. They're tailoring resumes. They're tracking applications in a spreadsheet. They're doing work. But they're doing work in only one layer while four other layers sit at zero. The math doesn't forgive this.
What You're Going to Build
Student: So over the next several modules, we're building all five layers?
Swati: Yes. And we're building them in a deliberate order. Here's the sequence and the reasoning behind it:
Module 02: Resume. We start here because the resume is the universal document - every other layer eventually drives toward it. Even a referral needs a resume attached. We build a strong resume first so that as we optimize the other layers, the resume is ready to convert.
Module 03: Cover Letters. Short module, but important for the companies and roles where cover letters matter - they're not dead everywhere.
Module 04: LinkedIn. Once the resume is solid, we optimize your LinkedIn to align with it. Keyword optimization, headline engineering, the About section, and content strategy. This opens the passive recruitment channel.
Module 05: GitHub and Portfolio. Technical presence. What to build, how to document it, how to make projects tell a story. Also covers technical blogging and building presence without being an extrovert.
Module 06: Networking. The human amplifier. Referral strategy, cold outreach, coffee chats, and how to build a professional network from scratch - because Arun had to do exactly that as a 22-year-old with 14 rejections and no industry connections.
Module 07: Project Portfolio. How to build and present projects that interviewers care about. Connecting projects to interview answers.
By the end of Module 07, your entire discoverability stack will be built. Modules 08 onward focus on using that stack - finding jobs through the AlgoInsight Jobs Portal, running targeted applications, managing the pipeline, handling interviews, and negotiating offers.
Tip: Don't try to fix everything at once. After the self-audit in the next topic, you'll know which layers are strongest and which are weakest. Start with the weakest - that's where the highest marginal return is. Going from a zero to a 3 in one layer does more for your job search than going from a 7 to a 9 in another.
Interview: Your Discoverability Stack IS an Interview Answer
When a behavioral interviewer asks "Tell me about a time you had to build something from scratch" or "Describe a situation where you identified a problem and built a system to solve it" - your job search process is that answer. You audited your current state, identified gaps across five layers, built a plan, executed module by module, measured results, and iterated. That is systems thinking in action, and it maps perfectly to the STAR format:
Situation: I was getting a 2% response rate on job applications. Task: I needed to systematically improve my visibility to recruiters and hiring managers. Action: I built and optimized a five-layer discoverability stack - resume, LinkedIn, GitHub, portfolio, and network. Result: My response rate increased from 2% to 15%, I received 3 recruiter InMails per week, and I converted 2 of my first 5 applications to phone screens.
This isn't hypothetical. Candidates who build their stack thoughtfully can genuinely tell this story. We cover STAR in depth in Behavioral Interview Mastery.
Exercise: Starter: List all five layers of your discoverability stack and write one sentence about the current state of each. Be honest - "I don't have one" counts. This is diagnostic, not judgmental.
Intermediate: For each layer, score yourself 0 to 10. 0 means "doesn't exist." 5 means "exists but not optimized." 10 means "best it could possibly be." Calculate your product (multiply all five scores). If the product is under 1,000 (out of a maximum 100,000), you have significant gaps. Identify the single lowest score - that's your priority fix.
Advanced: Find a job posting for your dream role. For each of the five layers, write down specifically what that company would want to see. What keywords should your resume contain? What should your LinkedIn headline say? What kind of projects should be on your GitHub? Who do you know at the company? This exercise turns the abstract framework into a concrete action plan.
Student: I think I've been a Pattern 1 candidate this whole time - resume-only. I have a solid resume but basically nothing else. That explains a lot.
Swati: It explains everything. And the good news is that you now know exactly what to fix. In the next topic, we're going to do a structured self-audit - a formal assessment of your current stack across all five layers. You'll walk out of that lesson with a clear picture of your gaps and a priority order for filling them.
Let's go.