Welcome to the future of education!<\/p>\n
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.<\/p>\n
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.<\/p>\n
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<\/p>\n
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.<\/p>\n
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.<\/p>\n
Ensuring that the Product and content available on the platform meets the Embibe standards and is completely bug-free<\/p>\n
| METRIC NAME<\/th>\n | UNIT<\/th>\n | FREQUENCY<\/th>\n<\/tr>\n |
|---|---|---|
| Number of Bugs Identified<\/td>\n | Number<\/td>\n | Daily<\/td>\n<\/tr>\n |
| Number of Feature Corrections Identified<\/td>\n | Number<\/td>\n | Daily<\/td>\n<\/tr>\n |
| Number of Bugs Driven to Closure<\/td>\n | Number<\/td>\n | Daily<\/td>\n<\/tr>\n |
| Timeline Adherence to Features and Content Releases<\/td>\n | Date<\/td>\n | Weekly<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nL2 PROBLEMS OWNED<\/h4>\nWe 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:<\/p>\n
|