Skip to content

Intern Onboarding — Week 1 (Kwilo AI, Staging)

Goal: by Friday the intern understands what Kwilo is, who uses it, and has walked every major flow herself on staging — as a learner, a trainer, an admin, and a creator. She is not building anything this week. She is using the product like a real user and reporting what she sees.

Format: self-guided. One theme per day, log in with the role for that day, run the checklist, write an end-of-day note. Mentor reads the note and replies before next morning.

What Kwilo is (read first, 15 min)

Kwilo AI is an end-to-end AI platform for learning. One system covers the whole loop: plan → create → teach → assess → proctor → personalise. Two primary customers:

  • Higher education — engineering / degree colleges, universities. Structured as Org → School → Program → Branch → Semester → Subject.
  • Corporate L&D — training and upskilling teams.
  • K-12 (Karnataka board, CBSE, classes 8–10) is secondary/legacy.

Roles in the system: Platform Admin → Org Admin → School Admin → Trainer (Teacher) / Learner (Student) / Parent, plus External Educator (marketplace creator).

The differentiators to watch for as you explore: AI content generation grounded in the institution's own syllabus (RAG), a Socratic AI tutor that guides instead of dumping answers, on-device exam proctoring (camera analysis runs in the browser, no video uploaded), and a marketplace where educators sell content.

Day 0 — Access setup (do before Day 1; ~30 min, with mentor)

⚠️ Staging is gated by Cloudflare Access. The page won't load until the intern's email is allowed in (one-time-code login). Sort this before anything else.

  • [ ] Mentor: add the intern's Gmail (or any email she uses) as a bypass/allowed identity in Cloudflare Access (Zero Trust team kwilo). A @kwilo.ai address is not required — a Gmail works.
  • [ ] Intern: open https://app-staging.kwilo.ai, enter that email, get the one-time code, confirm you reach the Kwilo login screen (not a Cloudflare block page).
  • [ ] Use a Chrome profile dedicated to this, camera working (needed for proctoring on Day 3).
  • [ ] Bookmark the URLs and save the account list below.

Staging URLs

Surface URL
Marketing site https://staging.kwilo.ai
Product app https://app-staging.kwilo.ai
API (reference only) https://api-staging.kwilo.ai/api/v1

Staging logins (org: Bangalore Test Academy / BTA Engineering College)

Role Username Password
Learner (Student) student_arjun Student@2026
Trainer (Teacher) teacher_anita Teacher@2026
Trainer (faculty) jayasheela j4zl9VayJ0
School Admin sa_btaec SchoolAdmin@2026
Org Admin oa_bta001_b6it uQVdm3JsqbcY
Platform Admin platformadmin Admin@Staging2026
Parent parent_reddy Parent@2026

Login with username (not email). Role is auto-detected — no role picker. Parent Venkat Reddy is linked to learner Arjun Reddy.

Ground rules

  • Staging only. Never log into production. This data is safe to poke; prod is not.
  • You're here to find and report, not to fix. Screenshot anything confusing or broken.
  • It's fine to create test content, run quizzes, send chats — that's the point.
  • Stuck >20 min? Note it and move on. Don't burn a day on one screen.

Day 1 — The learner experience

Log in as: student_arjun Goal: experience Kwilo the way a student does, end to end.

  • [ ] Land on the dashboard. What does a learner see first? Is it obvious what to do?
  • [ ] Open the AI tutor / Kwilo Intelligence chat. Ask a real question from any subject. Try the different modes (Explain, Practice, Doubts, Revise, Exam prep). Notice: does it give answers, or guide you to them?
  • [ ] Switch tutor language to Hindi or Kannada and ask again. Does it actually respond in that language?
  • [ ] Browse Courses / Library. Open a course, open a lesson.
  • [ ] Find an assignment or quiz, attempt it, submit it.
  • [ ] Note anything that felt confusing, slow, delightful, or broken.

EOD deliverable: fill the feedback template (bottom). Focus today: "As a brand-new student, where did I get lost?"

Day 2 — The trainer / content-creation experience

Log in as: teacher_anita (and jayasheela if you want a second view) Goal: see how a trainer builds teaching material with AI.

  • [ ] Explore the trainer home / dashboard. What's the trainer's main job here?
  • [ ] Use AI content creation: generate a lesson, a set of slides, a quiz, and a worksheet. Try a real topic.
  • [ ] Look at the Knowledge Base — how does a trainer upload their own syllabus/material so the AI stays on-scope?
  • [ ] Open the trainer-side AI chat modes (lesson plan, question bank, teaching ideas, feedback). Generate a lesson plan.
  • [ ] Create or edit an assignment and assign it to learners.
  • [ ] Note: how long did generation take? Was the output usable? Anything wrong or off-curriculum?

EOD deliverable: feedback template. Focus: "Would a busy trainer save time here, or fight the tool?"

Day 3 — Assessment, AI grading & proctoring

Log in as: teacher_anita, then student_arjun Goal: see how exams are run, graded, and kept honest.

  • [ ] As trainer: set up an assessment with a rubric. Include at least one written/long answer.
  • [ ] As trainer: enable proctoring on a quiz (check the proctoring settings panel).
  • [ ] As learner: take the proctored quiz. Allow the camera. Try the things a cheater would (switch tabs, look away, open a second window) and watch what the system flags.
  • [ ] As trainer: open AI evaluation — review the AI score, the rubric breakdown, and the proctoring/integrity report. Try overriding a score.
  • [ ] (If visible) look at the mobile answer-sheet scan / physical exam autofill flow in the docs or UI.
  • [ ] Note: did proctoring catch what you expected? Was the AI grade reasonable? Was the integrity report clear?

EOD deliverable: feedback template. Focus: "Would a college trust this enough to run a real online exam?"

Day 4 — Admin, analytics & marketplace

Log in as: sa_btaec → oa_bta001_b6it → platformadmin Goal: see how the institution is managed and measured, and how the marketplace works.

  • [ ] As School Admin: explore user management, academic structure (programs, branches, semesters, subjects), how trainers/learners get created.
  • [ ] As Org Admin: look at the org hierarchy and settings — one level up.
  • [ ] As Platform Admin: open Insights / analytics — engagement, mastery heatmaps, the trainer quadrant. What story does the data tell?
  • [ ] Explore the Marketplace — browse courses/quizzes for sale, filters, pricing, creator view. (External educator / creator flow.)
  • [ ] Note: is it clear who can do what at each admin level? Are the analytics actually useful or just charts?

EOD deliverable: feedback template. Focus: "If I ran this college, would these screens help me make a decision?"

Day 5 — Consumer (B2C) side + wrap-up

Goal: see the public/consumer funnel, then synthesize the week.

  • [ ] Open the marketing site (https://staging.kwilo.ai) as a logged-out visitor. Is the pitch clear in 10 seconds?
  • [ ] Walk the B2C signup / freemium flow — sign up as a fresh consumer learner, hit a paywall/quota, see the pricing page.
  • [ ] Compare the B2C consumer experience to the B2B institutional one from Day 1.
  • [ ] Synthesis (the main task today): write a one-page summary —
  • Top 3 things that impressed you
  • Top 5 things that confused or frustrated you (ranked by how badly)
  • 3 ideas you'd suggest if you were on the team
  • The single biggest "huh?" moment of the week
  • [ ] Optional: a 10-min verbal walkthrough with the mentor.

EOD deliverable: the one-page synthesis + final feedback template.

End-of-day feedback template (copy this every day)

Date / Day:
Role(s) I logged in as:

1. What I explored today (bullets):

2. What worked well / felt good:

3. What confused me (with screenshots):

4. Bugs or broken things (with steps to reproduce + screenshots):

5. Questions for the mentor:

6. Ideas / "why isn't it like X?":

7. Time spent vs. expected:

Mentor: reply to each EOD note the same evening or next morning — answer questions, confirm bugs, and point to the next day. The confusion points are gold: they're how a real new user would feel. Capture good ones as issues.

Success criteria (end of week)

  • Intern can explain, in her own words, what Kwilo does and who each role is for.
  • She has logged in as every role and completed each day's checklist.
  • A running list of confusion points + bugs exists (these feed the product backlog).
  • One-page synthesis delivered on Day 5.

Credentials mirror docs/operating/test-credentials.md. If a login fails, that file is the source of truth — it may have rotated.