Offers and Leveling

The title arrives before the job does

Maya has two offers after a long search. One is for Senior Software Engineer on a public company’s platform-reliability team. The other is for Staff Engineer at a private startup. The startup offers the larger title and describes more upside. The public company offers more cash and a title Maya already holds.

After months of being assessed, it is difficult not to read those offers as verdicts. Staff appears to say that one company understood her better. Senior appears to say that the other did not. Neither title yet tells her what she will be able to do on a Tuesday morning six months after joining.

An offer becomes meaningful only when its parts describe the same job: the level, the work, the authority to do it, the manager and team, the way success will be judged, the compensation risk, and the terms that shape daily life. Maya’s task is to reconstruct that job before she negotiates either package.

Begin with what is known

Maya asks each recruiter for the complete written package and keeps a short record of what the interviews established. She does not fill gaps with the most flattering interpretation.

Offer A — public company
Known: internal senior level; platform-reliability team; named manager;
base, target bonus, and stock award; remote work with quarterly travel.
Still unclear: first two projects; promotion evidence; stock refresh practice.

Offer B — private startup
Known: public title of Staff Engineer; base; option grant; founder-manager;
broad responsibility for product infrastructure.
Still unclear: internal level; team after a pending reorganization; final
decision rights; option terms; expected office attendance.

The unknowns are not footnotes. A pending team assignment can erase the manager and mission Maya evaluated. “Broad responsibility” can mean useful technical leadership, or accountability for decisions made elsewhere. An option grant without its instrument, vesting, exercise, and termination terms cannot yet be compared with cash or traded shares.

She gathers evidence in the order that changes the decision. First come the internal level and public title; the systems, decisions, and outcomes the role owns; the reporting line, team, and first projects; and the six- and twelve-month expectations. Then come the package components and governing documents. Finally she checks the terms that reach beyond the work itself: location, travel, start date, any probation or introductory period, confidentiality and intellectual-property language, restrictive terms, and repayment obligations.

Verbal answers still have evidentiary value. A manager’s explanation can reveal judgment, candor, and local practice. But a promise that is material to the decision—team placement, remote status, compensation, or a start-date condition—needs to survive beyond the conversation.

Make the level observable

Companies use titles and levels differently. “Senior” may describe ownership of a bounded service family in one organization and cross-team architecture in another. “Staff” may belong to a mature ladder, or it may be the title a small company uses when it needs an experienced engineer to handle whatever arrives.

Maya therefore treats the level as three claims. The first is the label: the internal level and the title used outside the company. The second is operating scope: the systems, decisions, teams, and outcomes she will own. The third is the evaluation standard: what successful work at that level looks like after six months and after a year.

She asks each hiring manager the same pair of questions:

What evidence led to this level, and what distinguishes engineers who succeed
at this level here?

What would you expect me to own, influence, and deliberately defer during my
first two quarters?

The manager for Offer A describes ownership of a reliability roadmap for two service families, leadership of incident follow-up, and influence over a neighboring team’s adoption work. Maya would set technical direction within that boundary; her manager would resolve staffing and product-priority conflicts. Promotion would require sustained influence beyond the two service families, not merely completing the first projects.

Offer B resists the same questions. The founder describes company-wide architecture influence, but product leadership will set weekly priorities and retain final authority over delivery trade-offs. The role is accountable for reliability across the product, although the reorganization has not settled which engineers will work with Maya.

That answer does not prove the startup is a bad place to work. It reveals a specific risk: staff-sized accountability with unsettled control. Conversely, Offer A’s lower title is not automatically a downlevel. It is a bounded role with an explicit route to broader scope. The useful comparison is no longer Senior versus Staff. It is clear authority within a smaller domain versus larger responsibility whose authority is still being negotiated.

If no one can explain a level, treat the ambiguity as part of the offer. Do not upgrade a vague answer into a credible promotion path, and do not assume that every lower level is an insult. A title can be corrected in a document; a job without the conditions needed to succeed is harder to repair after joining.

Follow the authority into the team

Scope becomes real through people. Maya wants to know who evaluates her, who can change her priorities, and who controls the decisions for which she will be held responsible. She asks whether the offer is tied to the manager and team she met, and whether placement can change before her start date. She asks about the on-call rotation, current incidents, roadmap commitments, hiring gaps, technical debt, and dependencies that could consume the first two quarters.

The quality of an answer matters alongside its content. A manager need not pretend the work is orderly. A credible answer might say that on-call is noisy, one migration is late, and a product deadline will constrain the first design. It should also say who can change the deadline, how escalation works, and what support Maya will have. “Fast-paced” or “high impact” does not answer those questions.

Offer A’s manager names the rotation, the late migration, the two engineers joining the first project, and the product leader who owns schedule trade-offs. Offer B’s founder is candid that team placement depends on the reorganization and that decision boundaries are still evolving. Candor makes the uncertainty easier to price; it does not make it disappear.

Read compensation through certainty, time, and downside

The packages use different instruments, so one total-compensation figure would manufacture a clean comparison. Maya separates money she can reasonably expect to receive from money that depends on performance, continued employment, market price, exercise, or an uncertain liquidity event.

Offer A contains base salary, a target bonus, and a stock award that vests over time. Base is the clearest component. The bonus depends on the plan’s actual rules. The stock has an observable market value, but its eventual value still depends on price and vesting.

Offer B contains lower base salary and options in a private company. The options may have upside, but the grant count alone says little. Maya needs the type of instrument, vesting schedule, exercise price, liquidity conditions, and what happens to vested and unvested portions when employment ends. She also needs to know whether refresh grants are a practice, a discretionary possibility, or merely part of the recruiting story.

Her questions become mechanical rather than optimistic:

Which components are guaranteed, which are contingent, and which depend on a
market or liquidity event? When does each component vest or pay?

Could you send the plan and grant documents that describe the instrument,
vesting, exercise requirements, liquidity rules, and treatment when
employment ends?

Are sign-on, relocation, education, or other payments repayable if I leave
before a specified date?

Equity, tax, immigration, and employment rules vary by instrument and jurisdiction. Recruiter summaries are orientation, not a substitute for the governing documents or qualified advice. The point of this review is not to perform amateur legal or tax analysis. It is to notice when the value of an offer depends on a term Maya has not yet seen.

Find the promises that can evaporate

Some of Maya’s largest risks sit outside compensation. Offer A describes a remote arrangement with quarterly travel, but she checks whether both pieces are written and whether the company can change them. Offer B calls the role “flexible,” while leaders expect senior engineers in the office during planning weeks. Maya asks for an expected pattern, including who decides when an exception becomes a requirement.

She reads the remaining terms in plain language before seeking specialist help. Where is she expected to work? How much travel is normal, and who pays? Can she meet the start date without violating an existing notice obligation? What changes during any probation or introductory period? Which side projects or inventions fall under the intellectual-property terms? Do restrictive covenants or repayment clauses constrain her future choices?

The right response to an unclear term depends on the term. Some need a factual answer from the recruiter. Some need a written amendment. Some require advice from a lawyer, tax professional, or immigration specialist familiar with the applicable jurisdiction. And some are clear but unattractive trade-offs that Maya must either accept knowingly or decline.

She marks each unresolved item with one verb:

clarify     learn the missing fact
negotiate   ask the company to change the package or condition
review      obtain qualified advice on a material term
accept      take a known risk because the rest of the role justifies it
decline     refuse a risk or mismatch that cannot be made workable

This prevents a common failure in offer review: treating every concern as another compensation ask. More cash may price some risk. It cannot create decision rights, restore a different manager, or make an unclear legal term understood.

Maya chooses the job she can name

The startup supplies the option documents and confirms that office attendance will be more frequent than Maya can sustain. The reorganization still prevents the founder from naming her team, and final product trade-offs will remain outside her control. Those facts make Offer B more legible, not more suitable. Its staff title now describes high-variance responsibility, meaningful upside, and a working pattern that conflicts with Maya’s constraints.

The public company confirms the team, first projects, remote arrangement, and travel pattern in writing. Its manager gives Maya examples of the broader influence required for the next level. The package has less upside, but more of its value is observable and its authority matches its accountability.

Maya chooses Offer A because her priorities are durable senior scope, a strong manager, family cash stability, and remote work. Someone with different constraints might choose Offer B after the same investigation. The method does not reward large companies or caution. It exposes the work and risk so the candidate, rather than the title, can make the trade.

Before negotiating, Maya writes the offer she believes she is considering:

Level and title:
Internal senior level; public title Senior Software Engineer.

Work and authority:
Own reliability direction for two service families and incident follow-up;
influence adoption across one neighboring team; manager owns staffing and
escalates product-priority conflicts.

Manager and placement:
Named manager and confirmed platform-reliability team; first two projects and
on-call rotation known.

Success:
Six-month delivery and reliability outcomes are explicit; broader promotion
evidence requires sustained cross-team influence over later review cycles.

Compensation and terms:
Base, target bonus rules, stock vesting, remote status, quarterly travel, and
start date documented. Stock refresh practice still needs clarification.

Decision:
The role is acceptable as described. Clarify refresh practice; negotiate only
the package priorities that would materially improve the decision.

That page is more useful than a weighted score. One severe mismatch should not disappear inside an average, and personal priorities should not pretend to be universal coefficients. The record gives Maya a stable account of the job before the next conversation tries to improve its terms.

The offer is ready for negotiation when she can say what work she is accepting, what authority makes that work possible, how the company will judge it, which risks remain, and which promises are durable enough to rely on. Until then, the headline number and title are answers to a smaller question.

Related links

• Reverse-Interviewing the Company
• References and Background Checks
• Level Calibration
• Choose the Right Role Before Preparing
• Negotiation