# Talent Strategy and Resume Narrative Read this before selecting bullets for any JD-tailoring task. ## 1. Interpret the talent problem Read the JD as evidence of the business problem behind the hire, not as a list of words to repeat. Infer: - what the person must make true in the first 6-18 months - which decisions, systems, or outcomes they will own - who must trust them and why - likely failure modes in the role - the minimum credible background and the differentiators above that minimum - what the JD states explicitly versus what the company context implies Separate hard screens, operating requirements, and cultural signals. Treat generic employer language cautiously unless the rest of the evidence supports it. ## 2. Build a company-context model Use the JD and reliable company evidence to reason across multiple dimensions: - company stage, growth rate, and organizational maturity - product category, customer, business model, and economic engine - functional maturity of the team being joined - role altitude: executor, owner, architect, leader, or thought partner - ambiguity, pace, risk tolerance, and expected autonomy - audience: recruiter, hiring manager, functional leader, and executive - talent density and the likely comparison set Translate context into selection and language choices. An early team may reward zero-to-one construction, range, and leverage; a scaling team may reward repeatable systems and operating cadence; a mature organization may reward depth, governance, and decision quality. These are examples, not fixed rules. Reason from the actual company rather than classifying by stage alone. ## 3. State the talent thesis Before opening the bullet vault, write an internal talent thesis: ```text They need a who can in . Darsh is credible because he has already , , and . The resume must make easy to understand without sounding defensive. ``` Then define: - one candidate identity in plain language - 2-4 proof pillars - the strongest evidence for each pillar - the main screening risk or narrative gap - what should be de-emphasized even if impressive - the tone: builder, scaling operator, subject-matter expert, strategic partner, or another context-specific combination The identity must emerge from evidence. Do not invent a slogan and force every bullet to repeat it. ## 4. Design the resume story Treat the resume as a sequence: 1. The top bucket establishes fit and gives the reader a reason to continue. 2. Education supplies relevant credibility without interrupting the narrative. 3. Current experience proves present-day level, judgment, and trajectory. 4. The most role-relevant experience proves direct pattern match, even when it is not the most recent. 5. Older experience adds a distinct capability rather than more of the same. 6. Additional material provides authentic affinity or technical leverage. Use Darsh's canonical format: 1. `Why ` 2. `Education` 3. `Professional Experience` 4. `Additional` Do not make the top bucket an enthusiasm paragraph. It should bridge the candidate to the role with concrete proof and restrained product affinity. Keep the current role first, then place the strongest direct pattern-match role second even when it is older than another role. End with one substantive side project rather than a generic certification-and-tools line. ## 5. Select experiences multidimensionally Score candidate evidence internally across: - direct mandate match - quality and credibility of the result - ownership and judgment - scale and complexity - company-context transferability - distinctiveness versus likely candidates - recency and career progression - keyword coverage - narrative contribution - explanation cost and line efficiency - specificity dividend: whether a domain detail improves the target reader's conclusion enough to justify its explanation cost - factual confidence Do not use a mechanical total. Use the dimensions to expose tradeoffs, then make an editorial judgment. A bullet earns space only if it proves something the target reader needs to believe and does so better than the available alternative. Prefer a coherent portfolio over maximal coverage. Avoid five bullets that all prove modeling skill while leaving leadership, operating judgment, or business results unproven. ## 6. Position titles and domains honestly Mirror the target's functional language when the underlying work supports it, while preserving official titles and dates. Use a truthful functional descriptor or sub-role to help the reader interpret a non-obvious designation. Flag any strong title reframe for user approval. When a company brand creates the wrong stereotype, explain the relevant product surface through the experience itself. For Epic, foreground Unreal Engine or the relevant developer-platform, licensing, creator-tool, or enterprise context when that is the work being described. Translate gaming-specific customer segments and mechanisms into accurate, transferable commercial language unless the original detail materially improves fit, scale, or credibility. Do not apologize for the company name. ## 7. Run the narrative test Before drafting, answer internally: - After a 20-second scan, what three things should the recruiter remember? - Does the first half of the page prove the role's central mandate? - Does each section advance the same candidate story? - Is the candidate differentiated or merely qualified? - Is any bullet present because it is impressive in isolation but irrelevant? - Does the language fit the company's operating culture without mimicry? - Would a skeptical talent partner understand the fit without insider context? - Does every domain-specific detail help bridge the candidate to the target, or does any detail pull the story back toward an unwanted stereotype? If these answers are unclear, revise the talent thesis before rewriting bullets. ## 8. Calibrate competitive risk Use bold but defensible framing by default: - choose the strongest accurate action verb - foreground the largest supported stakes or consequence - remove timid qualifiers and internal-process language - state the strategic implication when it is a reasonable reading of the work - use a truthful functional descriptor to make non-obvious experience legible - prefer the best-supported causal version over a merely chronological account Distinguish framing stretch from factual fabrication. Framing stretch can elevate emphasis, simplify mechanism, and express significance. It cannot invent an employer, title, date, credential, metric, completed outcome, direct report, customer, or sole ownership. If the competitive version depends on a missing fact, ask a targeted question or use the strongest supported wording. When two versions are both defensible but carry different interview risk, prefer the bolder version and preserve enough underlying detail that Darsh can explain it naturally in an interview.