QUALITY ASSURANCE AND PRODUCT MANAGEMENT

Welcome to the future of education!

At Embibe, we have just one mission – to truly personalise education. Because every child deserves it. This has led us to embark on this noblest of journeys to deliver life and learning outcomes for every student! Rooted in consumer behavior, we are leveraging AI to deliver personalised achievement journeys for every student.

Embibe has traversed a long journey from a data-centric product to an AI platform. On this journey, we have realised that the most powerful teams are: 1. Vision Led in understanding student context and obsessed with success; 2. Self-Organising in defining their own agenda; 3. Intellectually Fierce and Globally Conscious in their choices, and 4. Consistently Excellent in their execution.

After exploring a deeply functional organisational structure in engineering, we are now evolving towards a problem-solving team structure that manifests at the platform and backend level as an agile team supporting a unified front-end and augmented by a strong Architect + Principal Engineer + Advisory Group for technical mentoring. This document outlines the problem statement and other aspects of Quality Assurance and Product Management

THE PROBLEM STATEMENT

We want to build a strong Quality Assurance and Product Management team that ensures any changes suggested to the product have to be Logged, Disambiguated, Designed, Implemented, Validated and Documented by the respective L1 and L2 teams. This team will be responsible for being a pipeline for aggregating all changes coming from multiple forums to maintain a daily burn-down chart of these changes as well as building highly automated QA tools.

THE INSPIRATION

This function is inspired by leading global technology giants like Google, Facebook and Apple which typically ship code to the end-user, which is flawless and tested to perfection. It is the endeavor of this function to reach this goal of ensuring a six-sigma error rate in code and features shipped to end-users.

THE OBJECTIVES

  • To ensure a ny changes suggested to the product are:
  • Logged
  • Disambiguated
  • Designed
  • Implemented
  • Validated and Documented by Respective L1 and L2 Teams
  • To be a pipeline for aggregating all changes coming from multiple forums to maintain a daily burndown chart of these changes
  • To ensure product clarifications
  • To verify APIs scale with acceptable latency for Total Available Market for that feature
  • To verify API contracts for permutation of input variables as per the implementation note
  • To verify end-to-end customer journeys with exhaustive functional checks to ensure features are delivered as intended
  • To verify paint time and frontend build quality using lighthouse
  • To ensure pixel perfection as per design
  • To ensure adherence to Embibe’s MVP accessibility goals for each launch
  • To ensure that Embibe’s MVP accessibility standards evolve along with new market trends and devices
  • To verify events pipelines
  • To verify application logs, new relic traces and PagerDuty alerts

PRODUCT MANIFESTATION OF YOUR EFFORT

Ensuring that the Product and content available on the platform meets the Embibe standards and is completely bug-free

BUSINESS MANIFESTATION OF YOUR EFFORT

  • Release of M ore Stable and Planned Builds
  • Improved User Experience and NPS
  • Increased Client Retention

METRICS YOU WILL OWN AND LIVE BY

METRIC NAME UNIT FREQUENCY
Number of Bugs Identified Number Daily
Number of Feature Corrections Identified Number Daily
Number of Bugs Driven to Closure Number Daily
Timeline Adherence to Features and Content Releases Date Weekly

L2 PROBLEMS OWNED

We believe in building an organisation at the intersection of domain modelling and problem intuition. While the L1 teams give us the flexibility to have a multi-faceted view of the problem and cluster similar problems together, the L2 structure ensures independent and focused problem-solving. The following L2 teams have been suggested for the L1 problem stated above:

  • Change Control : To be a pipeline for aggregating all changes coming from multiple forums to maintain a daily burndown chart of these changes. This team is also responsible for product clarifications.
  • API Functional and Performance Testing : To test the functionality and performance of all APIs built at Embibe
  • Integration Testing and Paint Time : To test the end-to-end customer journeys with exhaustive functional checks to ensure features are delivered as intended and verify paint time and frontend build quality using lighthouse
  • Accessibility Checks and Pixel Perfection : To ensure that Embibe’s minimum viable product has acceptable accessibility checks and is pixel-perfect in terms of the user interface
  • Instrumentation Verification : To verify event pipelines, application logs, new relic traces and pager duty alerts

L1 SKILLS REQUIRED

  • Experience in Manuals and Automated Testing
  • Test Case Writing
  • TestNG/Junit
  • Java
  • SQL and MongoDB
  • Strong Analytical and Problem Solving Skills
  • UI Testing
  • Knowledge of Segment.io, GTM
  • Knowledge of GA/Heap Analytics
  • Good Written Skills in English
  • Previous Experience in Technical Documentation
  • Performance Testing Using Locust

IP DEVELOPED SO FAR

  1. QA Toll Gates
  2. 10 Commandments

To Join the Tribe, send us an email on [email protected]