Lessonly's positions


Manager Details:
• Positionsare simply the titles, which represent the expected reach (team, department, company, etc) each employee is expected to have at Lessonly.
These are critical to ensure consistent and therefore fair pay (each position should have a small salaray range in which everyone is paid within)
• Assignmentsare a collection of responsibilities needed for Lessonly teams. What outcomes and impacts your teammates can expect from you
• Abilitiesare the tools we value/recognize at Lessonly. They are the tools you need to complete those role responsiblities... HOW you do it
• Valuesare the aspirations we strive for at Lessonly

OurGruuv::Expect is built on the aspiration of equal pay for the same job.

Which is why we encourage companies to do away with arbitrary and unavoidably biased raises.

The better way is to have multiple levels within a single title and tie tight compensation ranges to these levels.

For instance, let's imagine that you have a growth framework where juniors are 1.*, mids are 2.*, seniors are 3.*, etc.
A 3.2 and a 3.3 within the domain of engineering would have the title of Senior Software Engineer. However, they would be paid differently becuase they've reached a different sub-level within the journey of being a senior.
This style of growth framework promotes actionable feedback based on the abilities Lessonly values.

  • More opportunity for recognition (and promotion)
    • ... and less ambiguity, burnout, and questioning "what do I have to do to be promoted/recognized"
  • More fairness and consistency.
    Possible because the system is designed to base recognized growth on a predefined and agreed-upon system of cumulative achievement (fair for specialists and generalists alike).
    • ... and less chance of bias or stress related to ensuring an equitable system for compensation-impacting recognition
  • More conversations about the things that matter (growth, performance, and the impact each teammate is having on each other and the mission)
    • ... and fewer "who likes whom" or "who is the best raise/compensation negotiator" games
Unstated expectations are resentments waiting to happen.

Therefore, OG strives forClear Expectationswhich leads to great habits, which leads to the team flow state, which leads to theLessonly Gruuv!

Lessonly / Product & Engineering

Senior Director, Product & Engineering
Inactive
(0 miles required)

    Lessonly / Product & Engineering / Engineering

    Software Engineering Manager - 3.4 - Full stack (Senior Software Engineering Manager)
    Inactive
    (0 miles required)

      Lessonly / Product & Engineering / Engineering / Development

      Product Software Engineer - 1.1 (Associate Software Engineer)
      Inactive
      (100 miles required)
        Product Software Engineer - 1.2 (Associate Software Engineer)
        Inactive
        (150 miles required)
          Product Software Engineer - 2.1 (Integrations track) (Software Integrations Engineer)
          Inactive
          (210 miles required)
            Product Software Engineer - 2.2 (Software Engineer)
            Inactive
            (0 miles required)
              Product Software Engineer - 2.3 (Software Engineer)
              Inactive
              (0 miles required)
                Product Software Engineer - 2.4 (Software Engineer)
                Inactive
                (0 miles required)
                  Product Software Engineer - 3.1 (Delivery track) (Senior Software Engineer)
                  Inactive
                  (0 miles required)
                    Product Software Engineer - 3.2 (Delivery track) (Senior Software Engineer)
                    Inactive
                    (0 miles required)
                      Product Software Engineer - 3.3 (Delivery track) (Senior Software Engineer)
                      Inactive
                      (0 miles required)
                        Product Software Engineer - 3.3 (Principal track) (Principal Software Engineer)
                        Inactive
                        (330 miles required)
                          Product Software Engineer - 3.4 (Delivery track) (Principal Software Engineer)
                          Inactive
                          (0 miles required)
                            Product Software Engineer - 3.4 (Hybrid track) (Principal Software Engineer)
                            Inactive
                            (0 miles required)

                              Lessonly / Product & Engineering / Engineering / Development / Tech Leadership

                              Product Software Engineer - 3.1 (Integrations track) (Senior Software Integrations Engineer)
                              Inactive
                              (310 miles required)