Auto Generation Of Tests
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 the Learning Outcomes & Recommendations Team.
Every student is different. They have different strengths, weaknesses, needs and even learning goals. We want to build the most personalised user journeys for students such that they can improve their learning outcomes with minimum time spent on the platform.
This function is inspired by leading global technology companies which operate at the intersection of content discovery and personalisation. The leaders in the space include:
It is the endeavour of this team to emulate the best practices of these global players into the content discovery and suggestions for users to spend time on learning, practice and testing aspects of the platform to enhance their speed of learning and knowledge assimilation.
METRIC NAME | UNIT | FREQUENCY |
---|---|---|
Discovery | Count of Clicks to Appropriate Comment |
Weekly |
Engagement | Minutes | Weekly |
Retention | Percentage | Weekly |
Bounce Rate on Intervention | Percentage | Daily |
Number of Tests Generated | Count | Daily |
Percentage of Tests Live Over Generated by the Algorithm | Percentage | Daily |
Test Quality Score | Score | Daily |
Latency of the Content Packaging API | Milliseconds | Daily |
Doubts Resolved | Count | Daily |
Questions Asked | Count | Daily |
Number of Content Types | Count | Daily |
Content Type-wise Engagement | Percentage | Daily |
Dropoff Rate of Content | Percentage | Daily |
Number of Videos | Number | Daily |
Engagement on Auto-generated Videos | Percentage | Weekly |
Completion Rate of Videos | Percentage | Daily |
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:
To Join the Tribe, send us an email on [email protected]