Explore Lessonly's Assignments

Choose Organization Growth Framework
Exploring Lessonly's growth framework
Choose Starting Position
Starting with the position: Product Quality Engineer - 3.2 (aka Senior Product Quality Engineer) (Check out Product Quality Engineer - 3.2)
Choose Assignments
Now it is time for you to build your unique job description! Simply go through and add a checkmark next to all of the Assignments you'd want to take on.
Click to copy the URL to share this exploration

Showing only relevant Assignments

  • Lessonly

     Assignments:
    --None--

    • Product & Engineering

       Assignments:
      --None--

      • Engineering

         Assignments:
        --None--

        • Product Quality

           Assignments:

          Our goal is NOT to test quality in, but instead to help the team build quality in from the start. Moving QA thinking farther left is our prime directive.

          Full Description

          Success looks like

          • Very few priority-1 and priority-2 defect escapees found in production.
          • You'll be successful at this role if the quality control process is one of collaboration and not tension between tester and coder.
          • You'll be successful at this role if the team learns how to build quality in from the start, a bit more every day.
          • We have this role because it is essential to ensuring a high-quality experience for our users. The goal is NOT zero bugs... the goal is balancing speed with risk management.

          Details

          • Measures like the number of remediations, number of written bugs, number of stories tested are all important, but none of them alone tell the story of the value of this role.
            • If there are no remediations happening, that means the engineers are perfect, or we aren't looking deep/wide enough, or maybe we've found a point where we are writing up shippable priority-3, 4, or 5 bugs but they do not need to block the stories. Alone it doesn't tell the story, but it is an indicator
            • If there are no bugs written, this could mean either the engineers are perfect, or our calibration of what constitutes a bug is off, or if remediations are through the roof maybe we have over-calibrated to what should constitute shippable. Alone it doesn't tell the story, but it is an indicator
            • If the number of stories tested is low... well, you should chat with your manager... not sure what this could mean other than bad things 🤔
          Requirements
          Examples
          An observation relating to  Quality control tester  has not been publicly recognized yet.
  • Explore Options
    At this step you'll be able to choose different positions or roles that will take you down different paths along your journey. It'll give you an idea of what areas to focus on next and if you do focus on them, what it may take to get to where you are going