Casavo's logo

Tech Ladder

Our technical ladder is divided into 4 verticals, covering what are the expectations of every individual contributor according to their seniority, which is specified as:

Below is a definition of every vertical followed by the expectations of every level on each of the vertical. Every level contains a non-exhaustive list of examples to better clarify what's intended in practice to check-off that particular expectation.

image description
  • Scope of influence
  • Building
  • Executing
  • Leadership
scope

Scope of influence

How much impact the work you do has on Casavo as a whole. As you progress, the work you do has a bigger and bigger positive effect on the company

  • Building →

Junior Software Engineer

image description

Scope of influence

Individual tasks within a project

  • Learning and being actively developed by others

  • Tests new code thoroughly, locally, and check in production everything is working once shipped

  • Real life examples →

Software Engineer

image description

Scope of influence

A project overall within a tribe / product area. You work directly in parallel with your peers

  • Self-sufficient in primary area of work, contributing to the project as a whole

  • Owns small-to-medium features from technical design through completion

  • Works in parallel with peers, building a stronger team through effective collaboration

  • Real life examples →

Senior Software Engineer

image description

Scope of influence

A larger project overall within a tribe / product area. You work in parallel with peers and often take a leading role on features or refactors

  • Self-sufficient in at least one large area of the codebase with a high-level understanding of other components

  • Contributes to the foundational good of their domain and engineering overall, defining (and refining) patterns and canonical examples, plus paying down tech debt

  • Proactively develops a stronger team

  • Mentors more junior members by helping them pursuing their commitments, and helping them grow in their career

  • Real life examples →

Lead Software Engineer

image description

Scope of influence

Whole team/Multiple teams

  • Gives guidance & unblocks others at minimum on their team

  • Acts as a resource to unblock and enable the whole team

  • Sought out by others as a mentor and provider of architectural guidance and kind coaching

  • Routinely and consistently pushes the team forward

  • Leads discussions in a respectful manner, unblocking the team by avoiding toxic behaviours

  • Real life examples →

Staff Software Engineer

image description

Scope of influence

Multiple teams/projects. Multiple product areas

  • Acts as a resource to unblock and enable teams across various areas and products

  • Exhibits excellent judgment regarding decisions across teams

  • Routinely and consistently pushes multiple teams forward

  • Real life examples →