Squarespace Software Engineer Career Ladder
Every level of Squarespace's software engineering ladder from L1 to L6 — typical timelines, what changes at each level, why engineers get stuck, and how promotions work.
Last updated: 2026-03-25
Aiming for your next level at Squarespace?
Get a personalized promotion plan with AI coaching.
Level Overview
| Level | Title | Typical Years | Median TC | Terminal? |
|---|---|---|---|---|
| L1 | Software Engineer 1 | 1–2 yr | $133K | No |
| L2 | Software Engineer 2 | 1–3 yr | $164K | No |
| L3 | Software Engineer 3 | 2–3+ yr | $189K | Yes |
| L4 | Senior Software Engineer 1 | 2–3+ yr | $239K | Yes |
| L5 | Senior Software Engineer 2 | 2–4+ yr | $273K | Yes |
| L6 | Staff Software Engineer | 3–5+ yr | $326K | Yes |
Promotion Cycle
Frequency
Not publicly documented (review cycle details not available)
Decision Maker
hybrid
Manager-driven with Engineering Director approval. Your manager builds your promotion case based on demonstrated growth across five competency areas. Engineering Directors review and approve the case. For Staff promotions, cultural and leadership contributions are evaluated alongside technical impact.
Key Details
- •Five competency areas: Knowledge, Scope, Autonomy, Communication, and Delivering Impact
- •Manager builds the promotion case and presents it to Engineering Directors for approval
- •Cultural contributions are evaluated alongside technical performance — internal talks, engineering events, mentoring
- •Staff promotions require evidence of sponsorship: providing exposure and growth opportunities for junior engineers
- •Growth is acknowledged as 'not uniform across competencies' — engineers are expected to be less experienced at some dimensions when first promoted
- •Annual raises are often capped around 5% even for top performers — promotion is the primary comp growth mechanism
- •Promotion depends heavily on manager advocacy and team placement — manager quality is a major variable
- •The criteria for Staff (L6) are less clearly documented than for lower levels — multiple employees report vagueness at this transition
L1 — Software Engineer 1
Entry Level / New GradEntry point for new grads. You execute well-scoped tasks with guidance from senior engineers, focus on learning the codebase, and ship small features reliably.
Typical Time at Level
1–2 years (typical: ~1.5 years)
Total Compensation (US)
$120K–$150K (median: $133K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Not demonstrating growing independence — still needing detailed task breakdowns after 6+ months
- •Staying in one part of the codebase without learning adjacent systems
- •Weak code review habits — not engaging meaningfully with others' code
- •Not asking for feedback or acting on it when given
L2 — Software Engineer 2
Early CareerGrowing autonomy. You own small-to-medium features end-to-end, contribute to design discussions, and work with less day-to-day direction. You start building awareness of how your work connects to the broader system.
Typical Time at Level
1–3 years (typical: ~2 years)
Total Compensation (US)
$145K–$185K (median: $164K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Comfortable with execution but not stretching into design or technical judgment
- •Not taking initiative on ambiguous problems — waiting for clearly scoped work
- •Limited collaboration outside your immediate team
- •Not demonstrating the communication skills needed for L3 scope
L3 — Software Engineer 3
Mid-LevelFull feature ownership. You own medium-to-large features, write design documents, and make technical decisions within your team's domain. Your manager defines the problem area; you figure out the approach.
Typical Time at Level
2–3+ years (typical: ~3 years)
Total Compensation (US)
$170K–$210K (median: $189K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Executing well at L3 scope without demonstrating senior-level judgment — more polished L3 work doesn't earn L4
- •Not writing or leading design docs for projects with cross-team dependencies
- •Limited visibility beyond your team — no evidence of influence outside your immediate group
- •Not mentoring L1/L2 engineers — senior levels at Squarespace expect you to grow others
- •Avoiding ambiguous or politically complex problems
- •Not investing in communication skills — at L4 you need to influence stakeholders, not just write code
L4 — Senior Software Engineer 1
SeniorTeam-level ownership and leadership. You lead multi-person projects, own system-level design decisions, and mentor junior engineers. Cross-team collaboration is expected. You're the technical authority for your area within your team.
Typical Time at Level
2–3+ years (typical: ~3 years)
Total Compensation (US)
$210K–$270K (median: $239K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Staying at team scope when L5 requires influence across teams
- •Leading projects but not shaping technical direction — doing vs. deciding
- •Not building relationships beyond your team that would support a promotion case
- •Manager dependency — promotion trajectory heavily depends on having a supportive manager who will advocate
- •Ignoring cultural contributions — Squarespace evaluates leadership beyond just technical output
- •Annual raises capped around 5% even for strong performers, creating compensation frustration that distracts from promotion focus
L5 — Senior Software Engineer 2
Senior+Deep senior scope. You operate across teams, own architectural decisions that affect multiple services, and are a go-to technical authority in your domain. This is the terminal level for most senior engineers. Getting to Staff from here requires a qualitative shift in how you work.
Typical Time at Level
2–4+ years (typical: ~4 years)
Total Compensation (US)
$240K–$310K (median: $273K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Continuing to operate as a strong individual senior instead of multiplying output across teams
- •Not driving cultural or leadership initiatives — Staff at Squarespace requires more than technical excellence
- •Limited visibility with Engineering Directors — Staff promotions need ED-level buy-in
- •Unclear criteria for what separates L5 from L6 — multiple employees report process gaps at this transition
- •Not sponsoring junior engineers — providing exposure, talks, and growth opportunities for others
- •Organizational constraints — limited Staff headcount means structural ceilings regardless of performance
L6 — Staff Software Engineer
StaffCross-team strategy and architectural ownership. You define technical direction across multiple teams, drive long-term system design, and serve as both a technical and cultural leader. Staff engineers at Squarespace are expected to fill cultural gaps, sponsor junior engineers, and lead internal education, not just write code.
Typical Time at Level
3–5+ years (typical: ~5 years)
Total Compensation (US)
$280K–$370K (median: $326K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Impact limited to a single team or project area
- •Not contributing to engineering culture beyond technical work
- •Lacking VP-level visibility into your contributions
- •Not developing senior engineers into future technical leaders
Additional Context
Squarespace is a website building and hosting platform headquartered in New York City. The company went public via direct listing on the NYSE in May 2021, then was taken private in 2024 after being acquired by Permira for approximately $6.9 billion. Most engineering roles are based in NYC. Squarespace evaluates engineers across five competencies: Knowledge, Scope, Autonomy, Communication, and Delivering Impact. The company's RSU vesting schedule is back-weighted: 15% in year 1, 25% in year 2, 25% in year 3, and 30% in year 4. Staff engineers are explicitly expected to be cultural leaders, not just technical ones.
Data sourced from Levels.fyi (compensation data, March 2026), Team Blind (anonymous employee reports), Squarespace engineering blog (Staff promotion account, competency framework), Indeed and Glassdoor (culture reviews), and H1B salary data. Squarespace does not publicly document its engineering career ladder.