Engineering Competency Framework
Level Overview
| Level | Title | Years | Scope |
|---|---|---|---|
| L1 | Junior Software Engineer | 0-2 | Feature development, bug fixes |
| L2 | Software Engineer | 2-5 | Component ownership, system design |
| L3 | Senior Software Engineer | 5-8 | System architecture, technical leadership |
| L4 | Staff Software Engineer | 8-12 | Cross-system architecture, org impact |
| L5 | Principal Engineer | 10-15 | Company technical strategy |
| L6 | Distinguished Engineer | 15-20 | Industry technical leadership |
| L3-M | Engineering Manager | 5-10 | Team management (5-8 engineers) |
| L4-M | Senior Engineering Manager | 8-12 | Multiple teams (15-25 engineers) |
| L5-M | Director of Engineering | 10-15 | Division leadership (50+ engineers) |
| L6-M | VP of Engineering | 12-20 | Site/org leadership |
| L7 | CTO | 15+ | Company technology vision |
KRA Weightage Distribution (IC Track)
| KRA | Junior | Engineer | Senior | Staff | Principal | Distinguished |
|---|---|---|---|---|---|---|
| Code & Delivery | 70% | 60% | 45% | 30% | 20% | 10% |
| System Design | 10% | 20% | 25% | 30% | 25% | 20% |
| Technical Leadership | 5% | 10% | 15% | 20% | 25% | 30% |
| Innovation & Research | 5% | 5% | 10% | 15% | 20% | 30% |
| Collaboration | 10% | 5% | 5% | 5% | 10% | 10% |
KRA Weightage Distribution (Management Track)
| KRA | Eng Manager | Sr Eng Manager | Director | VP | CTO |
|---|---|---|---|---|---|
| People Management | 40% | 35% | 30% | 25% | 15% |
| Technical Strategy | 15% | 20% | 25% | 30% | 40% |
| Delivery & Execution | 25% | 20% | 15% | 10% | 5% |
| Org Building | 10% | 15% | 20% | 25% | 30% |
| Stakeholder Management | 10% | 10% | 10% | 10% | 10% |
IC Track Competencies
L1: Junior Software Engineer
Code & Delivery (70%)
- Write clean, tested code in 1-2 languages
- Fix bugs with guidance
- Complete defined tasks on time
- Basic debugging skills
- Code review participation
- Unit test coverage
- Documentation for code
System Design (10%)
- Understand component architecture
- Basic design patterns
- API consumption
- Database query basics
- Performance awareness
- Security fundamentals
Collaboration (10%)
- Effective communication
- Team standup participation
- Pair programming
- Knowledge seeking
- Feedback receptiveness
Technical Leadership (5%)
- Code standard adherence
- Best practice adoption
- Tool proficiency
- Learning initiative
Innovation & Research (5%)
- New technology exploration
- Hackathon participation
- Tech blog reading
- Conference attendance
L2: Software Engineer
Code & Delivery (60%)
- Multiple language proficiency
- Independent feature delivery
- Code quality ownership
- Performance optimization
- Test strategy design
- Deployment automation
- On-call rotation
System Design (20%)
- Component architecture design
- API design and documentation
- Database schema design
- Caching strategies
- Asynchronous processing
- Microservices basics
Technical Leadership (10%)
- Code review leadership
- Technical mentoring
- Best practice enforcement
- Tool selection
- Technical documentation
Collaboration (5%)
- Cross-team coordination
- Requirements clarification
- Technical communication
- Stakeholder updates
Innovation & Research (5%)
- Proof of concept development
- New framework evaluation
- Performance experiments
- Open source contribution
L3: Senior Software Engineer
Code & Delivery (45%)
- Expert in multiple languages
- Complex feature ownership
- Technical debt management
- Performance architecture
- Security implementation
- DevOps practices
- Incident leadership
System Design (25%)
- System architecture ownership
- Distributed systems design
- Scalability planning
- Data architecture
- Integration patterns
- Platform thinking
Technical Leadership (15%)
- Technical roadmap input
- Team technical standards
- Architecture reviews
- Knowledge sharing
- Cross-team influence
Innovation & Research (10%)
- Technical innovation
- Patent contributions
- Conference speaking
- Blog writing
- Tool development
Collaboration (5%)
- Product partnership
- Technical strategy alignment
- External team influence
- Customer engagement
L4: Staff Software Engineer
System Design (30%)
- Multi-system architecture
- Platform strategy
- Technical vision
- Complexity management
- Scale challenges
- Reliability architecture
Code & Delivery (30%)
- Critical system ownership
- Org-wide standards
- Technical excellence
- Performance leadership
- Security architecture
- Operational excellence
Technical Leadership (20%)
- Org technical direction
- Principal engineer mentoring
- Technical culture
- Decision frameworks
- Review processes
Innovation & Research (15%)
- Research initiatives
- Industry contributions
- Patent portfolio
- Academic partnerships
- Open source leadership
Collaboration (5%)
- Executive communication
- Cross-org influence
- External partnerships
- Industry networking
L5: Principal Engineer
Technical Leadership (25%)
- Company technical strategy
- Architecture governance
- Technical culture evolution
- Industry influence
- Standards creation
System Design (25%)
- Enterprise architecture
- Technology roadmap
- Platform evolution
- Innovation integration
- Future architecture
Innovation & Research (20%)
- Research direction
- Emerging tech evaluation
- Industry collaboration
- Thought leadership
- Patent strategy
Code & Delivery (20%)
- Reference implementations
- Critical interventions
- Quality frameworks
- Excellence standards
- Tool strategies
Collaboration (10%)
- C-suite advisory
- Board technical updates
- Partner relationships
- Industry representation
L6: Distinguished Engineer
Technical Leadership (30%)
- Industry leadership
- Standard creation
- Technical brand
- Global influence
- Ecosystem building
Innovation & Research (30%)
- Industry research
- Future technology
- Disruptive innovation
- Academic leadership
- IP creation
System Design (20%)
- Industry architecture
- Next-gen systems
- Paradigm shifts
- Global platforms
- Reference architectures
Code & Delivery (10%)
- Industry benchmarks
- Reference platforms
- Quality paradigms
- Tool innovation
- Method creation
Collaboration (10%)
- Industry boards
- Standards bodies
- Academic advisory
- VC advisory
- Government advisory
Management Track Competencies
L3-M: Engineering Manager
People Management (40%)
- Team of 5-8 engineers
- 1:1s and career development
- Performance reviews
- Hiring and onboarding
- Team health metrics
- Conflict resolution
- Growth planning
Delivery & Execution (25%)
- Sprint planning
- Velocity optimization
- Quality metrics
- Release management
- Technical debt balance
- Incident management
Technical Strategy (15%)
- Team technical direction
- Architecture participation
- Tool selection
- Process improvement
- Innovation time
Org Building (10%)
- Team culture
- Knowledge sharing
- Onboarding programs
- Team rituals
- External visibility
Stakeholder Management (10%)
- Product partnership
- Cross-team coordination
- Status communication
- Escalation handling
L4-M: Senior Engineering Manager
People Management (35%)
- Multiple teams (15-25)
- Manager management
- Org design
- Talent planning
- Performance calibration
- Culture at scale
Technical Strategy (20%)
- Multi-team architecture
- Technical roadmap
- Platform decisions
- Build vs buy
- Innovation programs
Delivery & Execution (20%)
- Program management
- Cross-team delivery
- Dependency management
- Risk mitigation
- Operational excellence
Org Building (15%)
- Hiring strategy
- Diversity programs
- Learning culture
- Engineering brand
- University relations
Stakeholder Management (10%)
- Executive updates
- Customer engagement
- Vendor management
- Cross-BU alignment
L5-M: Director of Engineering
Technical Strategy (25%)
- Division technical vision
- Architecture evolution
- Technology investments
- Innovation portfolio
- Technical partnerships
People Management (30%)
- Large org (50-200)
- Leadership development
- Succession planning
- Org transformation
- Performance culture
Org Building (20%)
- Engineering excellence
- Talent ecosystem
- Culture evolution
- External brand
- Industry presence
Delivery & Execution (15%)
- Portfolio delivery
- Strategic initiatives
- Transformation programs
- Quality frameworks
- Efficiency metrics
Stakeholder Management (10%)
- C-suite partnership
- Board readiness
- Customer advisory
- Partner ecosystem
L6-M: VP of Engineering
Technical Strategy (30%)
- Company tech strategy
- Digital transformation
- Platform strategy
- Innovation agenda
- M&A technical assessment
Org Building (25%)
- Engineering culture
- Talent strategy
- Industry leadership
- Academic partnerships
- Ecosystem development
People Management (25%)
- Multi-site leadership
- Executive development
- Cultural alignment
- Change leadership
- Strategic hiring
Stakeholder Management (10%)
- CEO partnership
- Board engagement
- Investor relations
- Customer executives
- Industry influence
Delivery & Execution (10%)
- Company initiatives
- Transformation success
- Operational metrics
- Strategic outcomes
L7: CTO
Technical Strategy (40%)
- Company technology vision
- Industry disruption
- Technology moats
- Innovation ecosystem
- Future readiness
Org Building (30%)
- Technology culture
- Industry talent
- University relations
- Startup ecosystem
- Standards bodies
People Management (15%)
- Executive team
- Succession planning
- Leadership legacy
- Cultural impact
- Talent magnetism
Stakeholder Management (10%)
- Board leadership
- Investor influence
- Customer vision
- Partner strategy
- Government relations
Delivery & Execution (5%)
- Strategic success
- Transformation impact
- Industry benchmarks
- Competitive advantage
Key Transitions
Engineer to Senior (L2 → L3)
New Skills Required:
- System thinking
- Technical leadership
- Architecture design
- Influence without authority
- Strategic mindset
Common Pitfalls:
- Code focus over systems
- Limited influence radius
- Avoiding ambiguity
- Single solution thinking
Senior to Staff (L3 → L4)
New Skills Required:
- Organizational impact
- Technical strategy
- Complex tradeoffs
- Political navigation
- External visibility
Common Pitfalls:
- Team-only thinking
- Technical ivory tower
- Limited business view
- Communication gaps
IC to Manager (L3 → L3-M)
New Skills Required:
- People management
- Delivery through others
- Context switching
- Emotional intelligence
- Administrative tasks
Common Pitfalls:
- Coding withdrawal
- Micromanagement
- Conflict avoidance
- Time management
Manager to Director (L4-M → L5-M)
New Skills Required:
- Strategic thinking
- Organizational design
- Executive presence
- Business partnership
- Change leadership
Common Pitfalls:
- Tactical focus
- Limited delegation
- Narrow perspective
- Risk aversion
Technical Competency Matrix
Languages & Frameworks
L1-L2: 1-2 languages, 1 framework, basic tools L3-L4: 3-4 languages, multiple frameworks, advanced tools L5-L6: Polyglot, framework creation, tool innovation
System Complexity
L1-L2: Single service, component level L3-L4: Distributed systems, platform level L5-L6: Enterprise systems, industry level
Impact Scope
L1-L2: Team impact, feature success L3-L4: Org impact, product success L5-L6: Company impact, industry influence
Assessment Criteria
Technical Excellence
- L1-L2: Code quality, delivery speed, bug rates
- L3-L4: Architecture quality, system reliability, team productivity
- L5-L6: Technical innovation, industry impact, thought leadership
Leadership Impact
- Managers: Team performance, retention, delivery success
- Directors: Org capability, cultural health, strategic success
- Executives: Company differentiation, industry influence, talent magnetism
Innovation Metrics
- L1-L2: Learning velocity, tool adoption, improvement ideas
- L3-L4: Technical innovations, process improvements, patents
- L5-L6: Industry contributions, standard creation, paradigm shifts