The Job Search OS

Role: The Resume Strategist. Objective: ensure your resume clears the ATS filter and gives a hiring manager a reason to keep reading past the summary.

The Recipe

Act as an expert technical recruiter and resume strategist. I want to optimize my current resume for a specific target job description, ensuring it passes automated Applicant Tracking Systems (ATS) while remaining compelling to a human hiring manager.

I am going to paste my target job description and my current raw resume experience.

When I do, please execute the following refinement protocol:
1. Keyword Gap Analysis: Isolate the top 7 high-leverage technical skills, methodologies, or cloud tools mentioned in the job post that are missing or weak in my resume.
2. The Action-Impact Refactor: Take 3 of my existing bullet points and rewrite them using the Google X-Y-Z formula: "Accomplished [X], as measured by [Y], by doing [Z]." Ensure the phrasing matches professional engineering or corporate standards.
3. The Summary Hook: Draft a crisp, 3-sentence professional summary for the top of my resume that aligns my background directly with the core problem this company is hiring to solve.

Ask me to paste the Job Description and my Resume to begin.

What Phase 1 delivers

Output	What it fixes
Keyword Gap Analysis	The invisible filter — keywords the ATS is scanning for that your resume currently lacks
X-Y-Z Bullet Refactor	Vague experience statements converted into metrics-anchored evidence of impact
Summary Hook	The 3-sentence version of “why you, for this role, right now”

The ATS reality

Most enterprise and mid-size company applicant systems score resumes before a human ever sees them. The score is largely based on keyword density matching the job description. The gap analysis step tells you exactly which terms to add — not by keyword-stuffing, but by integrating them naturally into rewritten bullets.

The X-Y-Z formula

“Accomplished [X], as measured by [Y], by doing [Z]” — credited to Google’s recruiting team — converts passive job descriptions into active proof points. “Managed data pipelines” becomes “Reduced pipeline latency by 40% across 3 production systems by migrating batch ETL jobs to a streaming architecture on GCP Pub/Sub.”

Role: The Persuasive Copywriter. Objective: write a cover letter that reads like it was written for this company — because it was.

The Recipe

Act as an elite career strategist and persuasive copywriter. I need a short, high-impact cover letter for a company I am incredibly excited about. I want to completely banish generic, robotic boilerplate ("I am writing to express my interest...") and instead write an authentic, narrative-driven letter that proves deep domain alignment.

My target company and role: [INSERT COMPANY & ROLE]
The company's core mission or recent product launch: [INSERT CONTEXT / EMERGENCE]
My unique edge or professional background: [INSERT YOUR HIGHLIGHT]

Please write a 3-paragraph cover letter using this exact structural architecture:
- Paragraph 1 (The Non-Generic Hook): Start with a specific observation about a challenge, trend, or project the company is working on right now, instantly proving I actually research their space.
- Paragraph 2 (The Proof Point): Pivot to a high-leverage achievement from my past that proves I have already solved a parallel problem. Focus heavily on execution velocity and measurable metrics.
- Paragraph 3 (The Frictionless Close): Connect my personal engineering/professional philosophy to their culture and close with a direct, confident next step.

Keep the tone polished, authoritative, yet human and distinct.

The three-paragraph architecture

Paragraph	Job it does
Non-Generic Hook	Proves you know their world — earns the next 30 seconds of attention
Proof Point	Shows you’ve solved a parallel problem — converts attention into interest
Frictionless Close	Connects your philosophy to their culture — makes asking for a next step feel natural

Why the Hook must be specific

“I’ve long admired your company’s commitment to innovation” gets deleted. “Your recent migration to a serverless event-driven architecture at scale is exactly the class of problem I’ve been building systems to solve for the last three years” gets read. The specificity is the proof that you’re not mass-applying.

What to put in the company context field

A recent product announcement, a blog post from their engineering team, a funding round and what it signals about their roadmap, a specific architectural challenge mentioned in a conference talk by their CTO. Anything that shows you did 20 minutes of actual research.

Role: The Relationship Builder. Objective: bypass the application black hole by reaching actual humans who can move you forward before a recruiter screen.

The Recipe

Act as an organic growth hacker and executive relationship builder. I want to bypass the standard job board application black hole by conducting direct, relational outreach to internal stakeholders (e.g., internal recruiters, hiring managers, or future peers on the team).

The company and role I am targeting: [INSERT COMPANY & ROLE]

Please generate 3 distinct outreach swappable templates tailored to different platform constraints:
- LinkedIn Connection Request (Strict 300-character limit): A frictionless, low-pressure note designed to get an internal peer to accept my request based on shared professional domains or tech stacks.
- The InMail / Cold Outreach Email: A punchy 3-paragraph message targeting the hiring manager. It must briefly state why I admire their engineering/product direction, name-drop a massive data/operational win I've achieved, and ask a low-friction question (e.g., "Are you open to seeing a 1-page breakdown of how I'd approach your team's current architecture pipeline?").
- The Warm Intro Request: A blurb I can send to an existing mutual connection, making it effortless for them to forward my context straight to the hiring team.

The three channel templates

Template	Who it targets	Goal
LinkedIn Connection Request	A peer engineer or team member	Get accepted — no selling yet
Cold InMail / Email	The hiring manager directly	Earn a reply with a low-friction ask
Warm Intro Request	Your mutual connection	Make forwarding effortless for them

The 300-character constraint is a feature

The LinkedIn note limit forces you to lead with shared domain rather than a pitch. “Fellow GCP data engineer — love the real-time ingestion architecture you wrote about on your blog. Would value connecting.” That’s it. The follow-up happens after they accept.

The low-friction question

The InMail close should ask something easy to say yes to — not “can we schedule a call” but “are you open to seeing a 1-pager?” A 1-pager is a concrete, low-commitment artifact. It puts the ask at “yes/no” rather than “find time on my calendar.”

The warm intro blurb formula

Write it so your contact can forward it verbatim without editing. One sentence on who you are, one sentence on the role you’re targeting, one sentence on why you’re a strong fit, and a direct ask. The harder you make it for your contact to forward, the less likely they are to do it.

Role: The Principal Engineer Interviewer. Objective: pressure-test your architectural reasoning in the exact format you’ll face in the loop — no hints, no sample answers, only critique and escalating constraints.

The Recipe

Act as an exacting Principal Engineer and Technical Interviewer. I want to run a rigorous, interactive preparation session for a technical/systems design interview. I need to practice how to scope ambiguity, justify architectural trade-offs, and reason through edge cases.

The role I am interviewing for is: [INSERT ROLE, e.g., Cloud Data Engineer, Senior Full-Stack]
The technical focus/domain of the interview is: [INSERT DOMAIN, e.g., Designing real-time data pipelines on GCP, distributed systems, SQL schema optimization]

Please run the interview following these rules:
1. Do not give me solutions or sample answers. Ask me exactly ONE architectural or situational coding scenario to start.
2. Once I respond, critique my approach. Highlight potential single points of failure, scaling bottlenecks (e.g., network latency, database read/write locks), or edge-case gaps.
3. Force me to iterate on my solution by adding an operational constraint (e.g., "Now, how would you design this if our daily incoming event volume spikes by 100x?").

Let's begin. Present the initial system design challenge.

The interview simulation rules

Rule	Why it matters
No solutions or hints	Replaces the safety net — you’re forced to reason, not recall
Critique after every response	Surfaces the gaps in your thinking before the real loop does
Constraint injection	The most common interview escalation — tests whether your design is extensible or brittle

What interviewers are actually evaluating

Systems design interviews are not tests of memorized architectures. They’re evaluations of:

• How you scope ambiguity — do you ask clarifying questions or assume?
• How you justify trade-offs — do you explain why, or just what?
• How you handle pressure — when the constraint is added, does your reasoning hold up or collapse?

The critique step in this recipe is the most important part. It mirrors what a real interviewer is thinking but not saying.

The constraint injection pattern

Real interviewers escalate. “Now 100x the volume.” “Now the database goes read-only for maintenance.” “Now you have a hard 200ms latency budget.” These aren’t trick questions — they’re tests of whether your design has seams where new constraints can be absorbed. Practice this pattern until it feels like a conversation, not an ambush.

Role: The Performance Coach. Objective: convert your actual career experience into a structured, metrics-anchored story that sounds natural under interview pressure.

The Recipe

Act as an executive performance coach and master storyteller. I want to prep for behavioral interview questions using the STAR framework (Situation, Task, Action, Result). I need my answers to sound structured, high-agency, and metrics-focused without sounding rehearsed or artificial.

Please interview me one question at a time to extract a core professional story from my career. Do not dump the questions all at once. Over our dialogue, help me map out:
1. The Crucible (Situation & Task): What was a complex, high-stakes project, conflict, or failure you faced? What were the explicit technical or business constraints?
2. Your Direct Leverage (Action): What *specific* steps did you personally take to unblock the team, refactor the process, or build the solution? Focus heavily on your autonomy and systems-thinking.
3. The Undeniable ROI (Result): What was the quantifiable outcome? Express this in concrete metrics (e.g., system latency reduced by 40%, saved $50k in compute costs, shipped 3 weeks ahead of schedule).

Once we finish the dialogue, compile this story into a polished, scannable "STAR Matrix Profile" that I can quickly review right before my interview.

Let's begin. Ask me about the initial situation or project.

The three STAR extraction layers

Layer	What it forces
The Crucible (Situation & Task)	Specificity of context — a real high-stakes scenario, not a generic project summary
Your Direct Leverage (Action)	First-person agency — what you specifically did, not what “the team” did
The Undeniable ROI (Result)	Metrics — a number, a percentage, a timeline, a dollar amount

Why “without sounding rehearsed” is the goal

The failure mode of STAR prep is robotic delivery — you’ve memorized the answer so thoroughly it loses all natural texture. The one-question-at-a-time interview format forces you to reconstruct the story in conversation, which is exactly what you’ll do in a real interview. The profile you get at the end is a reference, not a script.

The “direct leverage” trap

Most candidates describe what the team accomplished. Interviewers are evaluating you — they want to hear “I proposed re-architecting the ingestion layer, which I owned end-to-end” not “we decided to refactor the pipeline.” This layer specifically asks for your personal contribution because that’s what the interview is testing.

Build multiple profiles

Run this recipe 3–4 times on different career stories. Behavioral interviews typically ask “tell me about a time when…” across multiple domains: technical challenge, conflict, failure, leadership, ambiguity. Having a matrix profile for each scenario ready to reference gives you confident, specific answers to any angle the interviewer takes.

Role: The Talent Agent. Objective: convert interview completion into maximum-leverage offer outcomes — reinforcing value after the loop, negotiating confidently, and using competing offers to create urgency without burning goodwill.

The Recipe

Act as an expert talent agent and compensation negotiator. I have completed my interview rounds and need to manage the final high-stakes phase of the job search loop: sending thank-you notes that reinforce my value, handling offer callbacks, and initiating compensation negotiations.

Please provide a strategic message suite containing:
- The "Value-Add" Thank You Email: A post-interview note to send within 24 hours to the lead technical interviewer. It should reference a specific technical debate or problem we discussed during the loop and include a brief, high-value insight or link demonstrating I am still actively solving their problem.
- Job Offer Negotiation Opener: An email script to deploy once an initial verbal or written offer is made, handling the transition toward negotiating base salary, sign-on bonuses, or remote equity allocations with collaborative leverage.
- The Multi-Offer Velocity Multiplier: A script to send to another company currently in my pipeline, politely informing them that I have received an offer and accelerating their internal interview timelines to create a competitive bidding environment.

The three closing scripts

Script	When to send	What it does
Value-Add Thank You	Within 24 hours of final round	Keeps you top of mind and demonstrates you’re still thinking about their problems
Negotiation Opener	Once the offer arrives (verbal or written)	Moves toward a higher number collaboratively — not adversarially
Multi-Offer Velocity Multiplier	Once you have an offer from Company A	Accelerates Company B’s timeline using honest competitive pressure

The Value-Add thank-you — why it’s different

A generic thank-you (“thank you for your time — I really enjoyed learning about the role”) is forgotten immediately. A specific one — “after our conversation about your Pub/Sub fanout bottleneck, I pulled together a quick reference on how Spotify handled a similar scale problem that might be relevant to your Q3 architecture decision” — reinforces that you’re already solving their problems. That’s the impression you want going into debrief.

The negotiation opener principle

Never counter with a number first. The opener creates a collaborative frame: “I’m genuinely excited about this opportunity, and I want to make it work. Based on my research into market rates for this scope and my background, I was hoping we could discuss getting the base closer to [X]. Is there flexibility there?” Collaborative language (“I want to make it work”) disarms the adversarial framing that makes most negotiations feel uncomfortable.

The multi-offer multiplier — honesty is the strategy

Don’t invent competing offers. If you have one, use it directly: “I wanted to let you know I’ve received an offer I’m currently evaluating, with a decision deadline of [date]. I’m genuinely excited about [Company B] and wanted to give you the opportunity to move forward before I decide.” This is honest, respectful, and creates real urgency without games.