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 the School Home, Student\u2019s School, Home Inbox, Calendar and Attendance team.<\/p>\n
We want to build the home page for schools and the student school home inbox and attendance systems, such that the experience to use these features is intuitive for both students and teachers.<\/p>\n
This function is inspired by leading mailing and calendar interfaces offered by leading global services like Gmail and Outlook. It is the endeavour of this function to provide cutting edge and intuitive mail and calendar features such that accessing email and keeping track of meetings on the calendar is a seamless and easy experience.<\/p>\n
To ensure a high-quality seamless user experience for:<\/p>\n
The team will deliver:<\/p>\n
Building a more comprehensive school product will:<\/p>\n
| METRIC NAME<\/th>\n | UNIT<\/th>\n | FREQUENCY<\/th>\n<\/tr>\n |
|---|---|---|
| Count of Bugs in Features Released<\/td>\n | Count<\/td>\n | Daily<\/td>\n<\/tr>\n |
| elivery of Build as per the Timeline<\/td>\n | Actual Date of Delivery\/ Target Date of Delivery<\/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 |