Career Progression and Role Comparison

Career progression paths, role comparison matrix, and decision authority hierarchy

Category: Team
Tags: salesforce roles career progression

Author: callinj
Name: Joe Callin
Title: Sr. Salesforce Developer
Email: joe@jcallin.dev

Table of Contents

  1. Career Progression Paths
  2. Common Transition Paths
  3. Skills Needed for Advancement
  4. Role Comparison Matrix
  5. Decision Authority Hierarchy
  6. Related Roles
  7. See Also

Career Progression Paths

flowchart TD
    Admin[Salesforce Administrator] -->|Learn to Code| Junior[Junior Developer]
    Admin -->|Requirements Focus| BusinessAnalyst[Business Analyst]
    Junior -->|1-2 years| Mid[Mid-Level Developer]
    Mid -->|2-3 years| Senior[Senior Developer]
    Senior -->|1-2 years, IC Track| Staff[Staff/Principal Developer]
    Senior -->|1-2 years, Leadership| Lead[Lead Developer]
    Lead -->|1-2 years| TechLead[Technical Lead]
    Staff -->|Strategic Focus| TechArch[Technical Architect]
    Staff -->|Strategic Focus| SolArch[Solution Architect]
    TechLead -->|Strategic Focus| TechArch
    TechLead -->|Strategic Focus| SolArch
    TechLead -->|Larger Scope| TechLead2[Technical Lead Larger Team]
    TechArch -->|Larger Scope| SeniorArch[Senior Architect]
    SolArch -->|Larger Scope| SeniorArch

Common Transition Paths

Administrator → Developer

  • Learn Apex and Lightning Web Components
  • Understand development patterns and best practices
  • Build portfolio of development work
  • Timeline: 6-12 months of focused learning

Junior → Mid-Level

  • Gain independence on feature implementation
  • Improve code quality and standards adherence
  • Build understanding of codebase and patterns
  • Timeline: 1-2 years

Mid-Level → Senior

  • Develop deep technical expertise
  • Start mentoring other developers
  • Take on complex problems and architecture
  • Timeline: 2-3 years (4-7 years total experience)

Senior → Staff/Principal Developer

  • Develop advanced architecture and standards expertise
  • Focus on project/program level technical leadership
  • Create processes and frameworks used across teams
  • Timeline: 1-2 years (5-8 years total experience)

Senior → Lead Developer

  • Develop coordination and stream/squad leadership skills
  • Balance hands-on contribution with guiding others
  • Build ownership within a subset of work (stream/squad)
  • Timeline: 1-2 years (4-6 years total experience)

Lead Developer → Technical Lead

  • Take full ownership of codebase and final authority on code
  • Expand from stream/squad to full team coordination
  • Balance technical excellence with delivery at team level
  • Timeline: 1-2 years (5-8 years total experience)

Senior → Technical Lead

  • Alternative path: skip Lead Developer and move directly to Technical Lead when ready for full code ownership
  • Develop coordination and leadership skills; take ownership of codebase and decisions
  • Timeline: 1-2 years (5-8 years total experience)

Staff/Principal → Technical Architect or Solution Architect

  • Develop strategic thinking and system-wide or solution-wide perspective
  • Focus on architecture and design over code
  • Coordinate cross-functional initiatives
  • Timeline: 2+ years (7+ years total experience)

Technical Lead → Technical Architect or Solution Architect

  • Develop strategic thinking and system-wide or solution-wide perspective
  • Focus on architecture and design over code
  • Coordinate cross-functional initiatives
  • Timeline: 2+ years (7+ years total experience)

Skills Needed for Advancement

To Mid-Level

  • Independence and self-sufficiency
  • Strong coding skills and standards adherence
  • Problem-solving ability

To Senior

  • Deep technical expertise
  • Architecture and design skills
  • Mentoring ability
  • Complex problem-solving

To Staff/Principal Developer

  • Advanced architecture and design skills
  • Standards and process development expertise
  • Cross-team technical influence
  • Framework and pattern creation ability

To Lead Developer

  • Stream or squad coordination skills
  • Balance of hands-on work and guiding others
  • Ownership within a subset of work
  • Collaboration with Technical Lead on final decisions

To Technical Lead

  • Full code ownership mindset
  • Final decision-making authority on code
  • Team-level coordination and tasking
  • Balance of technical and business priorities

To Technical Architect or Solution Architect

  • Strategic thinking
  • System-wide perspective
  • Cross-functional coordination
  • Architecture and design expertise

Role Comparison Matrix

Role Code Involvement Decision Authority Focus Area Time Horizon Primary Deliverable
Administrator 0% Configuration within scope User management, configuration Sprint Configured org, user support
Junior Developer 80-90% Implementation within patterns (with review) Learning, implementation Sprint Code, tests, learning
Mid-Level Developer 85-90% Implementation details Independent development Sprint Features, bug fixes
Senior Developer 70-80% Technical approach (with Tech Lead approval) Code architecture, mentoring Sprint-Quarter Complex solutions, mentoring
Staff/Principal Developer 50-60% Technical strategy, coding standards, best practices Advanced code architecture, standards, processes Quarter Architecture, standards, frameworks
Lead Developer 40-55% Technical approach within stream (with Tech Lead approval) Stream/squad leadership, hands-on contribution, mentoring Sprint-Quarter Stream delivery, coordination, mentoring
Technical Lead 20-40% Final authority on code Team coordination, code ownership, guidance, collaboration Sprint-Quarter Code decisions, team delivery, story validation
Technical Architect 10-20% System/platform architecture, technology choices Platform architecture, integrations, technical standards Quarter-Year Architecture, technical design, standards
Solution Architect 10-20% Solution design, business-technology alignment End-to-end solution, business alignment, cross-system Quarter-Year Solution architecture, strategic guidance

Decision Authority Hierarchy

Code Decisions

Technical Lead (Final Authority)
    ↓ (asks for input)
Lead Developer (Stream/Squad Input; authority within stream with Tech Lead approval)
Senior Developer (Technical Validation/Clarification)
    ↓ (provides guidance)
Mid-Level Developer (Implementation)
    ↓ (with supervision)
Junior Developer (Implementation with Review)

Key Point: Technical Lead makes final call on all code decisions, but asks Lead Developer and Senior Developer for technical validation and clarification before making decisions. Lead Developer has authority within their stream subject to Technical Lead approval.

Architecture Decisions

Technical Architect / Solution Architect (Final Authority in scope)
    ↓ (asks for input)
Technical Lead (Team Implementation Input)
    ↓ (provides input)
Lead Developer (Stream/Squad Input)
Senior Developer (Technical Input)

Key Point: Technical Architect and Solution Architect make final call on system/solution architecture in their scope, but ask Technical Lead and Senior Developer for input on implementation feasibility and team impact.

Configuration Decisions

Technical Lead (Approval for Code-Related Config)
    ↓
Administrator (Configuration within Scope)

Key Point: Administrator makes configuration decisions within defined scope. Technical Lead approves configurations that impact code or require developer coordination.

Story/Feature Decisions

Technical Lead (Final Authority on Implementation)
    ↓ (asks for validation)
Senior Developer (Technical Validation/Clarification)
    ↓ (provides input)
Mid/Junior Developer (Implementation Approach)

Key Point: Technical Lead owns story implementation decisions, asks Senior Developer for technical validation, and assigns work to developers based on their skills and capacity.

See Also