Career path deliberation assistant

Weighs a job offer against your current role across pay, growth, stability and work-life balance, laying out the trade-offs objectively instead of telling you what to pick.

PLPromptByte Library@promptbytePublished Aug 10

TextProductivity #career #decision making #job offers #planning

Version 1 of 1 · published Aug 10, 2026Version 1 · only version

Example output

See all results

Anthropic · Claude Sonnet 5 PLPromptByte Library Version 1

Prompt

Version 1 · 2 variables · 2 required

Fill in the values below — the customized prompt updates as you type. marks a required value.

Current position{{current_position}}

Your role, tenure, compensation, how you're performing, what's in flight, and what you like or dislike about it.

Offer details{{offer_details}}

For each offer: salary, equity and vesting, bonus, level, team, stability of the company, growth prospects, location and working pattern.

Fill in Current position, Offer details to copy the customized prompt.

Resultsfor version 1

All models Claude Sonnet 51

Version 1 · only version

Claude Sonnet 5 result by PromptByte Library
Anthropic · Claude Sonnet 5 PLPromptByte Library (@promptbyte)Version 1Published Aug 10
Compare
**Where you stand today** Four years in, strong reviews, and a platform rebuild you own that lands in about five months. That last point is doing quiet work in this decision: leaving before delivery converts a headline achievement into an explanation you'll give in interviews for years. It is not decisive, but it is an asset with a maturity date. **Comparing the two** *Compensation.* The offer's base is higher, but the comparison isn't complete until you price three things: the startup's four-year vesting with a one-year cliff against your existing grant's remaining schedule, what you…
Community submittedFull output
Settings: Unknown
Open result

Showing all 1 public result on version 1.

Usage notes

Deliberately does not pick for you. The rules tell it to stay objective and surface trade-offs, which makes it useful for the stage where you're still assembling the picture rather than the moment you have to answer the recruiter.

Give it real numbers in offer_details — base, equity terms and vesting, bonus structure, notice period, remote policy — and be equally concrete about the current role, including what you'd be walking away from mid-flight. Vague inputs produce a generic pros-and-cons list you could have written yourself.

It reasons about equity and compensation structure, but it is not financial advice and cannot value private company stock. Treat anything about equity as a list of questions to take to the company, not a valuation.

Good follow-up moves: ask it to write the questions you should ask each employer before deciding, or to describe what would have to be true for the option you're currently leaning away from to be right. That second one surfaces assumptions the first pass hides.

Attribution: adapted from https://github.com/f/awesome-chatgpt-prompts by f (contributed by chavez.cheong), licensed CC0-1.0. Source file: https://github.com/f/awesome-chatgpt-prompts/blob/main/prompts.csv

Models represented

Output2,071 characters

**Where you stand today** Four years in, strong reviews, and a platform rebuild you own that lands in about five months. That last point is doing quiet work in this decision: leaving before delivery converts a headline achievement into an explanation you'll give in interviews for years. It is not decisive, but it is an asset with a maturity date. **Comparing the two** *Compensation.* The offer's base is higher, but the comparison isn't complete until you price three things: the startup's four-year vesting with a one-year cliff against your existing grant's remaining schedule, what you forfeit by leaving unvested equity behind, and how the bonus you'd give up compares to the raise you're plausibly due. Private-company equity has no reliable value until there's a liquidity event — treat it as optionality, not salary. *Growth.* The staff title arrives roughly two years earlier than your current path suggests. The relevant question is whether the title carries scope that transfers. A staff role at a fifty-person company can mean broad ownership, or it can mean the same work with a better label — worth probing directly with the hiring manager. *Stability.* Eighteen months of runway is a real constraint, not a footnote. Ask about the raise plan and what happens to headcount if the next round slips. *Work-life balance.* Your current hours are predictable; early-stage teams rarely are. If the hours change materially, some of the pay increase is buying time back that you're simultaneously spending. **Questions to answer before you decide** 1. What does the staff role own that your current path doesn't reach for two more years? 2. What is the total value of unvested equity you'd forfeit, and would they cover it? 3. Where does each path leave you in five years if the company neither fails nor exits spectacularly — the likeliest case? **Trade-off in one line** You are weighing a near-term title and cash increase against delivery credit you've nearly earned, and trading a predictable environment for one with more upside and more variance.

Career path deliberation assistant

Example output

Prompt

Resultsfor version 1

Something wrong with this prompt?

Create a virtual-event run of show with fallback cues

Categorize an expense list with an auditable review queue

Build a packing checklist around a supplied trip plan

Write an asynchronous client handoff for the next team

Resolve a team prioritization deadlock with a fair process

Facilitate a MoSCoW scope-prioritization workshop

Discussion 0

Example output

Prompt

Resultsfor version 1

Something wrong with this prompt?

Related prompts

Create a virtual-event run of show with fallback cues

Categorize an expense list with an auditable review queue

Build a packing checklist around a supplied trip plan

Write an asynchronous client handoff for the next team

Resolve a team prioritization deadlock with a fair process

Facilitate a MoSCoW scope-prioritization workshop

Discussion 0