UNOPREP · CAREER MAP

See your next role, and the path to get there.

A guided plan from where you are today to the role you want, with the skills to build on the way.

  1. MILESTONE 1

    Where you stand today

    Tell us your field and level. We'll map the rest.

    SPECIALISATION
  2. MILESTONE 2

    Your path up the ladder

    Two ways up after Senior SDE (SDE III): stay hands-on, or lead people.

    SDE II → Engineering Manager · 5–7 yr · 2 steps

    ↘ Switch to management track

    Tip: select any rung to make it your target.

  3. MILESTONE 3

    What you bring vs what's needed

    How the job changes between SDE II and Engineering Manager.

    Competency comparison
    ■ TODAY■ NEEDED
    Scope & influence

    a feature to a whole team

    Problem complexity

    one feature's code to the team's frontend architecture

    Execution

    your own tasks to the team's delivery plan

    AI readiness

    using AI tools day to day to setting team norms for AI tools

    How long, typically
    5–7 yr

    SDE II: usually 2–5 yr of experience. Engineering Manager: 7–12 yr.

    YEARS OF EXPERIENCE2 → 7+
    023 yr

    Guidance, not a guarantee: pace depends on your track record, the scope you take on, and how much of your current craft transfers.

  4. MILESTONE 4

    Close the gap

    The skills that matter most for Engineering Manager in Frontend, in priority order.

    Scope & influence

    4 topics
    1. 1 · Running 1:1s and growth plans
      TOP PRIORITY

      Why it matters: As a manager, your output is your team's output.

      Practise: Hold weekly 1:1s with someone you mentor, using a shared doc for goals and feedback.

      RESOURCES
      • The Manager's Path (Camille Fournier)
    2. 2 · Hiring and interviewing frontend engineers

      Why it matters: Managers own who joins the team, and hiring mistakes are expensive.

      Practise: Interview others in 3 UnoPrep mock interviews and write structured feedback for each.

    3. 3 · Leading without authority across design, product and other teams

      Why it matters: Most of your team's work depends on teams you don't manage.

      Practise: Lead the API or scope discussion with a partner team for your next feature.

      RESOURCES
      • Leadership: Practical Leadership Skills

    Problem complexity

    5 topics
    1. 1 · Frontend system design at scale
      TOP PRIORITY

      Why it matters: At the next level you own how the frontend is structured, not just one feature.

      Practise: Run the design review for your team's next feature.

    2. 2 · Design systems and component architecture

      Why it matters: Shared components set the whole team's speed and consistency.

      Practise: Audit duplicate components in your app and propose a shared-library roadmap.

    3. 3 · Micro-frontends and BFF patterns: when to split

      Why it matters: Splitting too early can cost a team months.

      Practise: Write a decision record on whether your app needs micro-frontends or a BFF.

    Execution

    5 topics
    1. 1 · Team delivery planning and estimation
      TOP PRIORITY

      Why it matters: You commit dates for the team, not just for yourself.

      Practise: Run planning for the next two sprints and compare forecast with actual.

    2. 2 · Rendering performance and Core Web Vitals

      Why it matters: Performance is a product feature, and someone has to own the budget.

      Practise: Add an LCP/INP budget to CI and report it monthly.

      RESOURCES
    3. 3 · Frontend testing strategy

      Why it matters: Flaky tests slow the whole team down.

      Practise: Map your tests to the testing trophy and remove the 5 flakiest end-to-end tests.

    AI readiness

    3 topics
    1. 1 · Rolling out AI coding tools to a team
      TOP PRIORITY

      Why it matters: Managers decide the tools and the review rules.

      Practise: Run a two-week pilot with clear review rules and measure cycle time.

      RESOURCES
      • AI Coder: Complete Claude Code & Coding Agents Course
    2. 2 · Shipping LLM features in the UI

      Why it matters: Streaming, latency and failure states are frontend problems.

      Practise: Prototype a streaming answer with loading, error and retry states.

      RESOURCES
      • AI Engineering (Chip Huyen)
    3. 3 · Reviewing AI-generated code safely

      Why it matters: Quality, security and privacy risks from AI code land on reviewers.

      Practise: Write a review checklist for AI-generated code and use it on your next 5 reviews.

  5. FINISH

    Practise it with a peer

    Interview for Engineering Manager with someone who's already there.

    The fastest way to find your real gaps is a mock interview. Book a free session with a verified peer or mentor at Engineering Manager level.

    Book a mock interview