Life as Sakti

I fed my resume to an LLM and asked it to interview me until one of us gave up.

That single experiment changed how I think about career relevance. Not relevance as a buzzword, but as a discipline; something you practice, measure, and compound over time.

Staying relevant today is harder than it has ever been. The shelf life of a skill set is shrinking. New tools, frameworks, and paradigms show up faster than most professionals can absorb them. And the real danger is not falling behind; it is not knowing you have fallen behind. Most people discover their skill gaps only when they are already in a high-stakes situation: an interview, a performance review, a project that exposes what they cannot do.

I wanted to flip that. I wanted a repeatable, honest system for auditing myself before the market does it for me.

What emerged is a five-stage loop I call The Relevance Flywheel: Stress Test → Spot the Gap → Close the Gap → Build to Prove → Share to Compound. Each stage feeds the next, and the cycle never truly ends. That is the point.

Stage 1: Stress Test Your Skills

Most people confuse knowledge with skill. You can know how Kubernetes orchestration works and still fumble when asked to design a deployment strategy for a multi-region healthcare application under compliance constraints. Knowledge is what you have read. Skill is what you can do under pressure.

The Stress Test stage is about finding out where you actually stand.

How it works: Take your resume, feed it to an LLM, and ask it to conduct a rigorous, role-relevant technical and behavioral interview. Not a casual Q&A. A real stress test: probing, follow-up-heavy, designed to find the edges of your competence.

The key instruction: keep going until one of you gives up.

When the interview is done, ask the LLM to generate a comprehensive skills assessment report. Save it as myskillworth.md. This becomes your honest baseline; not what you claim on paper, but what you can actually defend in conversation.

Prompts for the Stress Test

Prompt 1: Setting up the interview

I am going to share my resume with you. I want you to act as a senior technical 
interviewer with 20+ years of experience hiring for roles at the intersection of 
[your domain, e.g., "enterprise software engineering and leadership"].
Conduct a rigorous interview based on the skills, experience, and claims in my 
resume. Follow these rules:
1. Start with the areas where my resume makes the strongest claims. Probe depth, 
   not surface familiarity.
2. Ask follow-up questions. If my answer is vague or theoretical, push for 
   specifics: real examples, trade-offs I have navigated, decisions I have made 
   and their outcomes.
3. Cover both technical skills and leadership/strategic thinking.
4. Do not softball. If you sense a weak spot, stay on it.
5. Do not stop until I explicitly say "I give up" or you are satisfied that you 
   have mapped my skill boundaries.
After the interview, provide a detailed Skill Worth Report covering:
- Skills where I demonstrated genuine depth (with evidence from my answers)
- Skills where I showed surface-level familiarity only
- Skills claimed on my resume that I could not adequately defend
- Blind spots: areas relevant to my profile that I did not mention or address
- An overall "skill confidence score" on a 10-point scale with justification

Prompt 2: Deepening the stress test (round 2, optional)

Now I want you to replay the three weakest areas from the interview we just 
completed. For each area:
1. Give me a realistic scenario or problem statement that a professional at my 
   level should be able to work through.
2. Let me attempt a response.
3. Then score my response on clarity, depth, and practical applicability 
   (each on a 5-point scale).
4. Identify what a strong answer would have included that mine did not.
This is not about getting the "right" answer. It is about exposing the gap 
between what I think I know and what I can actually execute.

Stage 2: Spot the Gap

Now that you know what you are worth, the next question is: worth it for what?

Pick a role. Not necessarily a job you are applying for today; pick a role that represents where you want to be, or a role you believe you should already be qualified for. Find a real job description for it.

Feed both your myskillworth.md and the job description to the LLM. Ask it to run a gap analysis: not a generic comparison, but a structured evaluation of where your proven skills meet the role’s demands and where they fall short.

Save the output as mygoalgap.md.

This is where ego meets evidence. The gap report does not care about your years of experience or your title. It cares about what you can demonstrably do versus what the role requires.

Prompts for Spotting the Gap

Prompt 1: Structured gap analysis

I am going to provide you two documents:
1. My Skill Worth Report (from a recent skills stress test): [paste myskillworth.md]
2. A Job Description for a role I want to benchmark myself against: [paste JD]
Conduct a thorough gap analysis following this structure:
A. SKILL MATCH MATRIX
   For each skill or competency required in the JD, rate my current level as:
   - STRONG MATCH: Demonstrated depth in the stress test
   - PARTIAL MATCH: Some evidence, but gaps in depth or recency
   - WEAK MATCH: Claimed or surface-level only
   - MISSING: Not evidenced at all in my skill profile
B. PRIORITY GAPS (ranked by impact)
   Identify the top 5 gaps that would most likely cause me to be screened out or 
   underperform in this role. For each, explain:
   - Why this gap matters for the specific role
   - How critical it is (dealbreaker vs. nice-to-have)
   - Estimated effort to close (quick win / moderate investment / deep rework)
C. HIDDEN STRENGTHS
   Identify any skills in my profile that the JD does not explicitly mention but 
   would be a genuine differentiator for this role. Explain why.
D. HONEST VERDICT
   If I were interviewing for this role tomorrow, what is the likely outcome? 
   Be direct.

Prompt 2: Competitive positioning analysis

Based on the gap analysis you just completed, answer these questions:
1. If 100 professionals with similar years of experience applied for this role, 
   where would I likely rank based purely on demonstrable skills (not credentials)?
   Top 10%? Top 25%? Middle of the pack? Below average? Justify your estimate.
2. What are the two or three things I could do in the next 90 days that would 
   move me up the most in that ranking?
3. Which of my gaps are the kind that get exposed in interviews (and can be 
   studied for) versus the kind that get exposed on the job (and require real 
   practice to close)?

Stage 3: Close the Gap

This is where most frameworks stop: “here are your gaps, now go learn.” That is not enough.

Take both documents, myskillworth.md and mygoalgap.md, and ask the LLM to design a targeted preparation plan. But more importantly, ask it to interview you again on your gap areas. Not a lecture; an interview. Force yourself to articulate, reason through problems, and think on your feet in precisely the areas where you are weakest.

The learning that follows will vary by person. Some people learn by reading papers. Some learn by watching walkthroughs. Some learn by arguing with an LLM until the concept clicks. The method matters less than what comes next.

Using my Skill Worth Report and my Goal Gap Analysis, design a focused 
preparation plan for my top 5 priority gaps. For each gap:
1. Give me a 15-minute "explain it back to me" interview question that tests 
   whether I truly understand the concept, not just recognize the terminology.
2. Suggest one hands-on exercise or mini-project that would force me to apply 
   this skill in a realistic context.
3. Recommend one high-quality resource (article, repo, talk, or book chapter) 
   that goes deep, not a beginner tutorial.
After I complete each area, re-interview me on it and compare my performance 
to my original stress test answers. Show me the delta.

Stage 4: Build to Prove

Learning without creation is consumption. Consumption without output is forgetting.

Whatever you have just learned, build something with it. The form does not matter as much as the act:

• Write a blog post that explains the concept to someone two years behind you.
• Draw a mind map that connects the new skill to your existing knowledge architecture.
• Build a small app, a tool, a prototype, a script that puts the skill to work.
• Create an explainer video where you teach it to a camera (or to no one; it does not matter).

The point is not perfection. The point is proof of understanding. When you build, you discover what you actually absorbed versus what you merely nodded along to. The gaps in your build are the gaps in your learning, made visible.

This is the oldest principle in education, and it still holds: creation is the highest form of learning.

Stage 5: Share to Compound

Here is where the flywheel starts to generate momentum beyond your own skill development.

In a world of noise, perception is not vanity; it is strategy. The people who stay relevant are not just the ones who learn; they are the ones who are known for learning. Sharing what you have built and what you have learned does three things simultaneously:

1. It builds your professional identity. Not a personal brand in the shallow sense, but a genuine signal to your network and your industry about what you think about, what you work on, and how deeply you engage with your craft.

2. It creates accountability. When you publish, you invite scrutiny. That scrutiny keeps you honest. You cannot bluff in a published article the way you can in a hallway conversation.

3. It inspires the next cycle. Writing about what you learned reveals what you still do not understand. The comments and conversations that follow expose adjacent gaps. And suddenly you are back at Stage 1, feeding a new version of yourself into the Stress Test.

The medium is your choice: a LinkedIn post, a Substack article, a conference talk, an internal tech talk at your company, a GitHub repo with documentation. What matters is that you close the loop by making your learning visible.

The Flywheel Effect

Here is why this is a flywheel and not a checklist.

Each cycle makes the next one more effective. Your myskillworth.md gets more honest over time. Your gap analyses get more precise because your self-awareness sharpens. Your builds get more ambitious because your foundations are sturdier. Your published work attracts feedback, collaborations, and opportunities that feed right back into the next audit.

The compounding is the point.

In a landscape where models, tools, and entire technology paradigms shift every eighteen months, the professionals who thrive will not be the ones with the most certifications or the longest resumes. They will be the ones with the tightest feedback loop between what they can do today and what the world will need tomorrow.

The Relevance Flywheel is how you build that loop.

Start with your resume. Start with an honest conversation. See where it takes you.