IWD dev team ladder

This job ladder exposes all roles inside IWD dev team, and define the goals, expectations and responsibilities of each role. To climb this ladder you will know what to do: Constant progression, being involved and meeting your individual objectives.

However, some implicit expectations are not specified in the roles:

• Being involved into code reviews
• Communicating, seeking help when stuck
• Being a "team player"

Track

Individual Contributor (IC)	Manager
Engineer I
Engineer II
Senior Engineer I
Senior Engineer II
Lead Engineer
	Engineer Director
	CTO/CPO

Individual Contributor

Engineer I

• Entry-level experience requirement: ~0–2 years
• Report: Lead Engineer
• Goals:
  • Work on features, with guidance
  • Manage bugs & hotfixes
  • Write tests, with guidance
  • Participate to review teammates work
  • Focus on growing as an engineer developer
  • Learn one aspect of the technical stack
  • Learn to deliver on-time

Engineer II

• Entry-level experience requirement: ~2–4 years
• Report: Lead Engineer
• Goals:
  • Work on features, with minimal guidance
  • Write tests, with minimal guidance
  • Review & Approve teammates work
  • Master one aspect of his project technical stack
  • Deliver on-time
  • Learn domain / business skills

Senior Engineer I

• Entry-level experience requirement: ~4–7 years
• Report: Lead Engineer
• Goals:
  • Work on epics, with minimal guidance
  • Work on features, without guidance
  • Write tests, without guidance
  • Master his project technical stack
  • Expert in one technology
  • Expert in one large area of the codebase
  • Mentor Engineer I
  • Focus on developing domain / business skills

Senior Engineer II

• Entry-level experience requirement: ~5–10 years
• Report: Lead Engineer
• Goals:
  • Work on epics, without guidance
  • Expert in more than one technology
  • Expert in many areas of the codebase
  • Mentor Engineer II & Senior Engineer I
  • Take initiatives to find and qualify structural issues
  • Manage technical backlog with Lead Engineer
  • Know, Define, Challenge, Evangelize best practices, processes and documentation
  • Expert in domain / business skills

Lead Engineer

• Entry-level experience requirement: ~10+ years
• Report: Engineering Director
• Goals:
  • Lead a Squad team (see definition above)
    • Supervise project's development, deadlines, rollout & support
    • Provide guidance to transversal subjects
    • Manage technical backlog
    • Report Squad/project status to Engineering Director
    • Involved in hiring process
    • Mentor Senior Engineer I & II
    • Listen and guide debates to help the squad reaching a consensus
    • Product Owner main contact
  • Technical stack owner
    • Technological watch
    • Challenge his squad proposals
    • Identify risks & justify choices
  • Master in domain / business skills

Manager

Engineering Director

• Entry-level experience requirement: ~10+ years
• Report: CTO/CPO
• Goals:
  • Work closely with the CTO to make the company’s vision actionable
  • Manage Engineer team
  • Plan & Manage recruitment alongside business goals
  • Have a global vision of products technical solution / OPS
  • Define & Organize development workflow processes, culture
  • Help teams to remove bottlenecks, improve velocity, resolve conflicts
  • Ensure operational support organisation across products
  • Manage & report budget

CTO/CPO

• Entry-level experience requirement: ~10+ years
• Report: CEO
• Goals:
  • Work closely with the Engineering Director to make the company’s vision actionable
  • Manage Product team & Engineering Director
  • Define Product strategy
  • Roadmap definition
  • Organize and manage high priority projects
  • Steering group member

Nota Bene

• In IC track, each role includes previous role responsibilities.
• Number of years of experience are indication only: skills and professional maturity are taken into account
• Squad team - A Squad team is an autonomous group of individual contributors, lead by a Product Owner and a Lead Engineer, working on business project.