Career framework · IC I–Principal

Vibe SWE Job Ladder

For HR, hiring managers, and career conversations

Vibe SWE is a subdomain of vibe engineering: humans in the loop, AI-native from day one. Models act as senior collaborators; the person owns intent, review, and the ship. This ladder overlays familiar IC tracks. Don’t invent parallel titles overnight.

How to use this ladder

Treat levels as expectation bands, not titles you must rename.
Map approximately: I ≈ L3 · II ≈ L4 · Senior ≈ L5 · Staff ≈ L6 · Principal ≈ L7+.
Score craft, not prompt volume or loyalty to a model brand.
Prefer evidence: Ship Cards, stakeholder briefs, PRs with ownership notes, security reviews, and post-ship learnings.

Craft dimensions

The same five dimensions at every level. The scope and stakes change.

Dimension	What good looks like
Intent & stakeholders	Turn messy human asks into outcomes, constraints, non-goals, and approvers — without laundering ambiguity into confident nonsense.
Build	Brief models like senior collaborators. Juggle tools without losing the thread. Read every shipped diff.
Ship	Land small, reversible, visible work with proof: tests, evals, screenshots, users. Security is part of done.
Learn	Change defaults after each ship. Taste and judgment show up as cuts, not just adds.
Scope	Own systems, people, and risk end-to-end. Breadth grows with the level.

Five levels. One accountable practice.

Vibe SWE I

~L3

Associate / early career

New grad or career-redefining builder

Intent: Restate tickets in one outcome sentence. Clarify before prompting.
Build: Use AI daily under guidance. Never ship unread output.
Ship: Deliver small ships with a reviewer and basic proof.
Learn: Write a short ‘what I’d change’ note after each ship.
Scope: A single feature or well-bounded task. Low blast radius.
Promotion signals: Readable diffs. Trusted clarifications. No ‘I didn’t know the model wrote that.’

Vibe SWE II

~L4

Mid / solid IC

Independent feature ownership

Intent: Write full briefings unprompted: outcome, constraints, non-goals, approvers, and risks.
Build: Work fluently across tools. Know when not to use a model. Kill model-suggested scope.
Ship: Own a vertical slice. Put security in the definition of done.
Learn: Improve personal defaults: checklists, evals, and review habits.
Scope: A full feature or small service. One or two stakeholder groups.
Promotion signals: Peers copy briefing habits. Ships land with evidence. Fewer fuzzy-ask rework loops.

Senior Vibe SWE

~L5

Senior IC

Team-level judgment and leverage

Intent: Negotiate scope. Kill requests that should die in conversation.
Build: Set team norms for AI-assisted work. Review others’ AI diffs for taste and risk.
Ship: Design proof strategies: evals, canaries, and rollback. Security is non-negotiable.
Learn: Turn incidents into shared practice.
Scope: A multi-feature area or critical path. Mentor Vibe SWE I–II.
Promotion signals: Team ships get safer and clearer. The hiring bar for human-in-the-loop work rises.

Staff Vibe SWE

~L6

Staff IC

Cross-team systems and standards

Intent: Align multiple stakeholder streams. Prevent org-level ambiguity laundering.
Build: Architect human, model, and agent patterns across teams. Pick standards, not fads.
Ship: Own cross-team release quality and evidence culture.
Learn: Publish durable frameworks others cite and use.
Scope: Org-level systems. Unblock several teams.
Promotion signals: Other teams adopt the practices. AI-assisted thrash and incidents measurably decline.

Principal Vibe SWE

~L7+

Principal / distinguished

Company and industry influence

Intent: Shape how the company talks to customers and regulators about AI-assisted delivery.
Build: Set long-horizon strategy for human-in-the-loop building.
Ship: Own portfolio-level risk and proof standards.
Learn: Contribute external thought leadership that strengthens practice, not hype.
Scope: Company or industry influence on what good AI-native engineering means.
Promotion signals: External credibility backed by internal systems that outlast individuals.

Interview signals

Level	Look for	Red flags
Vibe SWE I~L3	Curiosity, clarifying questions, and reading their own output.	Pastes model output unread.
Vibe SWE II~L4	A written brief before the build. Evidence of cutting scope.	Tool worship. No proof of ship.
Senior Vibe SWE~L5	Mentors review habits. Makes security part of done.	‘The model said so.’
Staff Vibe SWE~L6	Cross-team standards and durable documentation.	Heroics without institutionalization.
Principal Vibe SWE~L7+	Strategy with external clarity and internal follow-through.	Hype without ownership.

Anti-patterns at any level

Shipping unread AI output.
Treating vibe coding — prompt and hope — as production practice.
Competing with vibe engineering instead of nesting under it.
Measuring tokens or PR counts instead of owned outcomes.
Hiding human judgment behind “the model decided.”

Map expectations. Keep your titles.

Overlay these expectation bands on your existing ladder during calibration. An L5 who cannot brief stakeholders or prove ships is not operating as a Senior Vibe SWE — regardless of title. Use the evidence to name the gap, not a new title to hide it.