First 30 Days of a US Job: Onboarding Playbook

The 30/60/90 Framework

Day 30: learn the terrain. Day 60: deliver. Day 90: own. Ask your manager to co-write the 90-day success criteria in the first week — it becomes the first self-assessment language (use the performance review generator to draft it).

Culture Reading

Watch three signals: how decisions get made (docs, meetings, Slack), who gets promoted, and what gets punished. Remote culture is the same with fewer signals — get in-office anchors for the first month (the remote proposal generator formalizes hybrid schedules without hurting the ramp).

Co-write the success criteria in week one

The first review cycle is decided by the criteria that exist, not by the work you did. If nobody wrote criteria, write them yourself and ask your manager to confirm. That email becomes the language of your first self-assessment and your first raise argument.

1. Ask for three to five measurable outcomes with dates: what ships, by when, and how it is measured.
2. Ask how the role is graded. The level definition and the band are the map; ask which level you were hired into and what that level owns.
3. Send a confirmation email. Restate the criteria in your own words, with the dates, and ask the manager to correct anything wrong.
4. Book the checkpoint. A 30-day and a 60-day check-in on the calendar beats an unscheduled review at day 90.

Draft the criteria and the later self-assessment with the performance review generator, and when your scope has already grown past the level, use the promotion request letter. Log the dates in the application tracker so the checkpoint is not lost inside onboarding.

The evidence file that survives a reorg

Reorgs happen in the first year more often than managers admit, and your record travels badly unless you keep it in a format you control. Keep one dated file:

• Decisions you made: the document, the date, who approved it, and what changed after.
• Deliverables with numbers: before and after metrics, not adjectives.
• Meetings and commitments: who promised what, in which meeting, on which date.
• Feedback received: verbatim quotes, because later ratings often paraphrase them badly.
• Your own scope statement: what you own, what you do not, and when that changed.

Write the file weekly in a personal document. The night before a review, do not reconstruct from memory. If the org changes and a new manager inherits your team, that file is the only thing that explains your first 90 days. When a rating lands below the evidence, respond in writing with the raise denial response letter and ask for measurable targets.

Common onboarding failures and the recovery move

• Access and tooling take weeks. Send one escalation naming each missing item and the work it blocks, with a date you need it by. Use the deadline extension request for the deliverables stuck behind it.
• Scope is vague. Write a one-page scope statement and ask the manager to confirm or correct it. Silence is what turns into a surprise rating.
• Your manager leaves in month two. Send the handoff note to the new manager on day one: criteria, decisions, metrics, and open items. Do not restart from zero.
• Return-to-office or schedule surprise. Ask for the policy in writing and propose a measured pilot with the remote work proposal generator, rather than negotiating on vibes.
• Health or family strain during the ramp. Request accommodation through the interactive process with the ADA request letter; do not resign from rights you have not used.

The pattern is the same in every case: convert the ambiguity into one dated document, send it to the decision maker, and keep the reply.

For the current text behind these numbers, start with the California job exit rules page and the New York job exit rules page, along with the At-Will Employment definition and the hiring references non competes guide hub. Those sources state the rule in full; this page only points at them.

Frequently Asked Questions

Should I ask for a raise during the first 30 days?

No. Prove scope in the first cycle and negotiate in the next one with written evidence. Early money asks read as a transaction; a documented win plus band data reads as a case.

What do I do if onboarding has no structure?

Create the structure: ten informational meetings, a written scope statement, one small measurable win, and a 30-day check-in on the calendar. Self-structured ramps read as ownership and give you a record if the manager changes.

How do I survive a reorg in my first year?

Keep a dated evidence file you control: decisions, metrics, commitments, verbatim feedback, and your scope statement. Send it to any new manager on day one so your first 90 days are explained in writing, not reconstructed.

What is the fastest credible win in a new role?

One small, quantified fix everyone complains about: a document, a dashboard, a script, or a process change, shipped and presented with before and after numbers. A concrete win outperforms a month of passive learning.

Ask for a raise in month 2?

No. Prove scope in cycle 1; negotiate at cycle 2 with the promotion generator.

What if onboarding is chaotic?

Create your own map: 10 informational calls, one skill doc, one win. Self-structured ramps read as ownership.

The 30, 60, and 90-day clocks in a new role are onboarding and plan rules, and the reimbursement mandate, the pay window, and the claim deadline behind your prior job's wages are state rules graded in this build from reported sources. Confirm the reimbursement mandate and the pay window with the state agency named on the state rule pages, and keep the 90-day criteria request, the election snapshot, and the pay terms in writing in the application tracker.