Why the First 30 Days Matter More Than the Interview
Getting hired as a tutor at Refonte Learning is a serious process, but it is not the finish line. It is the starting line. The interviews, the code review, the mock session, the reference checks: all of that tells us whether a candidate can plausibly teach. The first 30 days on the platform tell us whether they actually will, at the standard our learners expect, week after week, cohort after cohort.
This article is the child piece to our pillar on how Refonte selects tutors, mentors and trainers. The pillar covers selection. This one covers what happens the day a new tutor signs the contract and gets their credentials, up to the end of their first calendar month. It is deliberately concrete. If you are a tutor candidate reading this to prepare, you will finish with a realistic picture of your ramp. If you are a learner curious about who is on the other side of your Zoom screen, you will finish knowing the training that person went through before they were allowed to sit across from you.
The reason the first 30 days matter so much is that tutoring at scale is a craft with a long tail of small skills. Screen sharing without wasting three minutes. Interrupting a stuck learner without demoralising them. Setting a project milestone that is ambitious but not overwhelming. Writing async feedback that a learner will read twice, not skim. These skills do not show up in a single interview. They show up when you have run twelve sessions and reviewed sixty pull requests and started to see patterns.
Our onboarding is designed to accelerate that pattern recognition. We do not throw new tutors into a full teaching load in week one. We do not leave them to figure out the platform alone. And we do not evaluate them only on learner surveys, which are lagging indicators. Instead, we run a structured 30-day plan with three phases: platform and pedagogy foundations, shadowing and co-teaching, then supervised solo delivery. Each phase has explicit deliverables, an assigned mentor, and a checkpoint at the end.
By day 30, a new Refonte tutor has typically observed at least four live sessions run by senior peers, co-taught two sessions, delivered three to five solo sessions under review, written written feedback on ten to fifteen learner submissions, and completed a portfolio of small pedagogical exercises. They have also had at least three one-on-one debriefs with their onboarding mentor. Only then are they cleared for a full independent teaching load.
The rest of this article walks through that month in detail, week by week and system by system, so both sides of the tutor-learner relationship know exactly what to expect.
Day Zero: Credentials, Contracts, and the Welcome Packet
Before a new tutor delivers a single minute of instruction, we spend the first working day on administration and orientation. This is not glamorous, but it is where a lot of onboarding programmes silently fail. If a tutor is still fighting with SSO on day seven, they are not focused on their learners.
On day zero, the new tutor receives a welcome packet that includes their signed contract, their tax and invoicing setup instructions (Refonte works with tutors across many jurisdictions, so this varies), their identity verification confirmation, and the security briefing. Refonte Learning takes learner data seriously; every tutor signs a data handling addendum that spells out what learner information they can access, how long they can retain artefacts, and what happens if a device is lost. This is not boilerplate. Tutors read it, ask questions, and sign explicitly.
The technical setup follows. Tutors get access to:
- The Refonte learning platform tutor console, where they see their assigned learners, cohorts, and calendar.
- The internal knowledge base, which contains curriculum notes, session playbooks, rubric guides, and past incident write-ups.
- The communication stack: Slack for tutor-to-tutor conversations, the messaging layer inside the platform for tutor-to-learner communication, and email for anything formal.
- The video conferencing tooling and its recording settings, which are pre-configured to comply with our recording and consent policy.
- The code review environment, which for engineering tracks is GitHub-based with our reviewer bot installed, and for data tracks includes access to shared notebooks and sandboxed cloud environments.
The new tutor is asked to log into every one of these on day zero and confirm access. A dedicated operations contact is on standby to unblock any credential issue within the same working day. This sounds trivial, but a friction-free first login is a real signal of respect: we are asking tutors to bring their full attention to teaching, so we do not want them to spend it hunting for passwords.
Day zero closes with an introduction to the onboarding mentor. Every new tutor is paired with a senior tutor from the same track (AI, data engineering, cloud, devops, or software engineering). This mentor is not their manager. Their job is specifically to shepherd the new tutor through the first 30 days: answer questions, review their early work, sit in on sessions, and sign off on the final checkpoint. Mentors are chosen for teaching skill, patience, and clarity of feedback, not just technical seniority.
By the end of day zero, the new tutor has a working environment, a human contact, a written plan for the next four weeks, and a clear understanding of what they must produce by day 30. From here, the real work begins.
Week One: Curriculum Immersion and Pedagogy Foundations
Week one is deliberately learning-heavy and delivery-light. New tutors do not teach live sessions in week one. Instead, they spend the week immersing themselves in the curriculum they will teach, the pedagogical model Refonte uses, and the specific expectations for tutors on their track.
The curriculum immersion is structured. If a tutor is joining the AI track, for example, they receive the full syllabus, module by module, along with the source materials: notebooks, slide decks, project briefs, rubrics, and reference solutions. They are expected to work through the projects themselves, in the same way a learner would, and to submit their solutions to their onboarding mentor. This is not busywork. It surfaces two important things. First, it lets the new tutor experience the friction points learners will hit, which is invaluable for empathy. Second, it lets us verify, once more, that the tutor's technical depth matches the demands of the material. This is a natural extension of the Refonte tutor technical screening that happens during hiring, but now applied to the exact content they will teach.
Alongside curriculum work, week one includes a pedagogy module. Refonte has developed an internal teaching handbook that codifies our approach: project-first learning, deliberate scaffolding, explicit feedback loops, and time-boxed struggle. New tutors read the handbook, watch four to six recorded exemplar sessions from senior tutors, and complete a short written reflection on each. The reflections are read by the onboarding mentor, who uses them to spot early gaps.
Specific topics covered in the pedagogy module include:
- How to run a project-based session versus a concept explanation session, and how to switch between the two mid-session when a learner needs it.
- The Refonte feedback rubric for written code reviews, which prioritises clarity, correctness, and next-step guidance over exhaustive nitpicking.
- How to handle the three most common learner states: confident and moving fast, stuck but engaged, and disengaged. Each requires a different tutor response.
- Escalation paths for issues that go beyond teaching, such as suspected academic dishonesty, mental health concerns, or interpersonal conflict.
The week closes with a first checkpoint conversation between the new tutor and their mentor. The mentor reviews the tutor's completed project work, discusses the pedagogy reflections, and answers open questions. If the mentor has concerns, they raise them here, not later. It is easier to correct a misunderstanding about our feedback style in week one than in week four.
By the end of week one, the new tutor has internalised the curriculum they will teach, understands the pedagogical model Refonte expects, and has produced tangible artefacts (project submissions, reflections) that their mentor has reviewed. They are now ready to see the model in action.
Week Two: Shadowing Live Sessions
Week two is about observation. New tutors do not lead sessions yet, but they attend live sessions run by senior tutors. This is the shadowing phase, and it is one of the most valuable parts of onboarding.
Each new tutor is scheduled to shadow at least four live sessions during week two, spread across different session types: a one-on-one project review, a small-group problem-solving session, a live coding walkthrough, and a cohort kickoff or checkpoint session. The variety matters. A tutor who has only ever seen one-on-ones will freeze the first time they run a group of six. A tutor who has only seen kickoffs will not know how to handle the messy middle of a project.
Before each shadow, the new tutor reviews the session brief: which learners are attending, where they are in the curriculum, what the session goal is, and what the tutor plans to cover. This context is essential; without it, shadowing becomes passive viewing. During the session, the shadow observes silently unless invited to contribute. They take structured notes using a template that asks specific questions: How did the tutor open the session? How did they handle the first learner question? What did they do when a learner got stuck? How did they close?
After each shadowed session, there is a 20 to 30 minute debrief between the senior tutor and the shadow. The senior tutor walks through their choices: why they interrupted at a particular moment, why they let a silence run, why they suggested a specific next step. This is where the tacit knowledge of teaching gets transferred. Reading about pedagogy is useful; hearing an experienced tutor explain, in the specific context of a session that just happened, why they made a call, is transformative.
A subtle but important part of week two is exposure to failure modes. New tutors are deliberately scheduled to shadow at least one session where something went sideways: a learner arrived unprepared, a live demo broke, a group dynamic soured. We do not stage these; we simply do not filter them out of the shadowing schedule. Watching a senior tutor recover from a broken Kubernetes demo, or gently redirect a learner who is monopolising a group session, teaches more than any handbook chapter.
By the end of week two, the new tutor has watched senior peers run real sessions across multiple formats, debriefed each one, and started to see the patterns underneath the surface. They have also usually identified their own likely blind spots, which they discuss with their mentor. Some new tutors realise they will struggle with silence, others that they tend to over-explain, others that they are uncomfortable with correction. Naming these tendencies early is half the battle.
Week Three: Co-Teaching and First Solo Attempts
Week three is where the new tutor starts to deliver. But they do not start alone. The first two live sessions a new tutor runs are co-taught with their onboarding mentor or another senior peer.
Co-teaching at Refonte is structured, not improvised. Before the session, the new tutor and the co-teacher agree on the split: who opens, who runs which section, who handles which learner if the group breaks out. The new tutor is usually given the middle sections first, where the learners are already warmed up and the session structure is established. The senior tutor handles the opening (which sets tone) and the close (which sets homework and next steps). This lets the new tutor concentrate on the teaching itself, not the choreography.
During the session, the co-teacher intervenes only if necessary. If the new tutor is handling a question well, the co-teacher stays silent, even if they would have answered slightly differently. If the new tutor is drifting into a rabbit hole or missing a learner's confusion, the co-teacher steps in gently, models the redirect, and then hands back. Learners are told at the start that they have two tutors in the session; this is framed as extra support, not as evaluation, and in practice learners appreciate it.
After each co-taught session, there is an extended debrief, usually 45 to 60 minutes. This is where the real coaching happens. The senior tutor gives specific, actionable feedback on the new tutor's delivery: the moment they should have paused, the explanation that could have been half as long, the learner they missed. Written notes from the debrief go into the tutor's onboarding record and are visible to their mentor. This is also where new tutors often realise how much they have absorbed from the pillar on what makes a good Refonte tutor, and where the abstract principles start to feel concrete.
By mid-week-three, most new tutors run their first solo session. This is a lower-stakes format, typically a one-on-one project review with a learner who is mid-cohort and progressing well. The session is recorded (with learner consent) and reviewed by the mentor afterwards. The new tutor writes a self-assessment before receiving the mentor's feedback; comparing the two is a powerful calibration exercise. Tutors who consistently self-assess much more harshly than their mentor need coaching on confidence; tutors who consistently self-assess much more generously need coaching on standards.
By the end of week three, the new tutor has typically co-taught two sessions and run one to two solo sessions under review. They have received detailed feedback on each and revised their approach. They are also starting to build direct relationships with a small number of learners, which will be their initial caseload when they graduate onboarding.
Week Four: Supervised Solo Delivery and Written Feedback at Scale
Week four moves the new tutor into a more realistic teaching load, still supervised but no longer co-taught. They run three to five solo sessions during the week, across the formats they have practised. Each session is followed by a shorter debrief with the mentor, usually 15 to 20 minutes, focused on one or two specific coaching points rather than a full review.
A major addition in week four is written feedback at scale. Live sessions are only part of a tutor's work at Refonte; a significant fraction of learner progress happens through written code reviews and project feedback delivered asynchronously. In week four, the new tutor takes on a queue of ten to fifteen learner submissions and delivers written feedback on each within the standard turnaround time (typically 48 hours).
The mentor reviews every one of these written reviews before they are sent to the learner. This is time-consuming for the mentor, but it is essential. Written feedback is where a tutor's habits get baked in. A tutor who develops the habit of vague praise ("nice work, keep it up") in week four will still be doing it a year later unless corrected immediately. Similarly, a tutor who over-corrects, marking every minor style issue with equal weight to a fundamental design flaw, will overwhelm learners.
The mentor's review focuses on three things:
- Accuracy: is the technical assessment correct? Did the tutor catch the real issues and not invent fake ones?
- Prioritisation: is the feedback ranked by importance? Learners should walk away knowing what matters most.
- Tone and clarity: is the feedback readable, respectful, and actionable? A learner should finish reading it and know exactly what to do next.
For tutors on the AI and data tracks, week four often includes their first exposure to reviewing project work tied to our flagship AI Engineering program. These projects are demanding, integrating model training, evaluation, deployment, and monitoring, and reviewing them well requires a tutor who can operate across the full stack. Mentors are particularly careful with feedback reviews on these submissions during onboarding, because they set the bar for the rest of the tutor's tenure.
Week four also introduces the new tutor to the operational rhythm of tutoring at Refonte: the weekly tutor stand-up in Slack, the monthly track-level review, the quarterly curriculum refresh discussions. Being a tutor is not just a series of sessions. It is participation in a community of practice that continuously improves the curriculum. New tutors are invited to observe these forums in week four, and to start contributing in month two.
By the end of week four, the new tutor has a realistic sample of teaching work under their belt: several solo sessions, a queue of reviewed written feedback, and observed participation in the wider tutor community.
The Day 30 Checkpoint: What Gets Reviewed and Who Signs Off
At the end of the first 30 days, every new tutor has a formal checkpoint. This is not a surprise assessment; the criteria are shared on day zero and refined throughout the month. The checkpoint is a structured review meeting between the new tutor, their onboarding mentor, and the track lead.
The review covers five dimensions:
- Session delivery. Did the tutor run their supervised sessions to standard? The mentor summarises the recorded sessions and the debrief notes. Specific evidence is cited, not vague impressions.
- Written feedback quality. A sample of five to eight written reviews from the tutor's queue is re-read together. Both strong and weak examples are discussed. The tutor is asked to critique their own work first.
- Learner signal. Any direct feedback from learners who have interacted with the new tutor is considered. This includes both formal survey data and informal messages. Because the sample is small, we treat this as directional, not definitive.
- Curriculum and platform fluency. Can the tutor navigate the curriculum without hesitation? Do they know where to find the rubrics, the reference solutions, the escalation paths? Fluency here reduces cognitive load during sessions, freeing attention for the learner.
- Professional conduct. Was the tutor punctual, prepared, and communicative? Did they show up to their debriefs with notes? Did they respond to Slack and email within our stated turnaround times?
The outcome of the checkpoint is one of three: full activation, extended onboarding, or exit. Full activation is the most common. The tutor is cleared for an independent teaching load, typically starting at 60 to 70 percent of full capacity and ramping up over the next month as they build momentum.
Extended onboarding is used when a tutor is clearly on track but not quite ready. Common reasons include a lighter-than-expected session count in month one (sometimes due to scheduling, not the tutor), or a specific skill gap that needs another two weeks of focused practice. Extended onboarding is not a failure; it is a calibration.
Exit is rare but real. If, after 30 days of structured support, a tutor's session delivery or written feedback is still below the bar we expect, we do not carry the problem forward. This is a tough call, but it is the fair one. Learners deserve consistent quality, and other tutors on the platform have earned that quality by clearing this bar themselves. This is the same standard-driven ethos that runs through the tutor application process, applied now to delivery rather than selection.
The checkpoint conversation is documented in writing. The tutor gets a copy. If there are specific development areas to work on over the next 60 days, they are written down as concrete goals with review dates.
The Mentor Side: What Onboarding Looks Like for Senior Tutors
A 30-day onboarding of this depth is only possible because senior Refonte tutors invest serious time in mentoring newcomers. It is worth being explicit about what that looks like from their side, because it explains why our tutor community stays healthy.
Senior tutors who take on an onboarding mentee are compensated for the mentoring time, not asked to do it as an add-on. Typical mentor time investment across the 30 days is 15 to 20 hours: two to three hours in week one (setup, curriculum review, pedagogy discussions), four to five hours in week two (shadowing debriefs), five to six hours in week three (co-teaching and debriefs), three to four hours in week four (session and written feedback reviews), and two hours for the day 30 checkpoint itself.
Mentors are selected based on demonstrated teaching quality (measured over multiple cohorts, not a single session), clarity of feedback (their debriefs are consistently rated as useful by previous mentees), and reliability. Not every senior tutor is a good mentor, and we do not force the role on anyone. Tutors opt in.
Mentors also feed information back into the platform. If a mentor observes that multiple new tutors are struggling with the same curriculum module, that module gets reviewed. If mentors notice a shared misunderstanding about our feedback style, the pedagogy handbook gets updated. Onboarding is a feedback loop, not just a training funnel.
This is one of the less visible reasons Refonte Learning maintains the standards it does: the people who trained the tutors you meet as a learner have themselves been trained, and they continue to shape how the next generation of tutors is trained. It is a community that improves itself, and the learner experiences described in our verified student experience writeups are downstream of exactly this kind of internal rigour.
Common Rough Patches in the First 30 Days
No onboarding is smooth. Even well-selected, well-prepared new tutors hit turbulence at some point in month one. Being explicit about the common patterns helps new tutors normalise them and helps mentors respond quickly.
The first common pattern is the week-two dip. After a productive week one, new tutors sometimes lose momentum in week two because shadowing feels passive. The fix is to give them a structured note-taking template and a specific observation focus for each shadowed session. Passive observation drifts; focused observation sticks.
The second pattern is over-preparation for the first solo session. New tutors often over-plan, arriving with pages of notes and rigid session outlines. The result is a session that ignores the learner in front of them and marches through the plan regardless. Mentors coach new tutors to prepare a spine, not a script: a clear session goal, three or four milestones, and permission to detour based on what the learner needs.
The third pattern is written feedback that is either too soft or too harsh. Tutors coming from academic backgrounds sometimes default to a professorial tone that lands as harsh online. Tutors coming from a mentoring or coaching background sometimes err toward encouragement without correction. Both are fixable with two or three cycles of mentor review, but only if the mentor is explicit about the pattern rather than just editing individual reviews.
The fourth pattern is learner-tutor mismatch. Occasionally a new tutor and one of their early-caseload learners simply do not click. The learner is not being unreasonable; the tutor is not being incompetent. It just is not the right pairing. Refonte has a lightweight reassignment process for exactly this case. New tutors are told about it on day zero so that when it happens, they do not interpret it as a verdict on their ability.
The fifth pattern, which we watch for carefully, is silent burnout. Some new tutors, especially those who came in with high expectations of themselves, will over-invest in week one and week two, then hit a wall in week three when live delivery starts. The mentor's job is to notice this early, in tone shifts during debriefs or slower response times in Slack, and to have an honest conversation about pacing. Sustainable teaching is a marathon.
None of these patterns are terminal. They are the normal wear of picking up a new craft. The onboarding structure exists precisely so that these patterns get noticed and addressed within a month, before they harden into habits.
What New Tutors Should Do Before Day One
If you have just been offered a tutoring role at Refonte and you are reading this before your start date, there is a small amount of preparation that pays off disproportionately.
First, actually work through one or two end-to-end projects from the track you will teach, if you have not already. Not the reference solution, your own solution. The friction you experience in doing so is the friction your learners will experience. You will refer back to those hours constantly in your first month.
Second, read the Refonte blog systematically, especially the tutor-facing posts. Reading about the tutor selection process, about the qualities that distinguish strong tutors, and about the technical screening will give you context for many of the norms you will encounter. It also lets you arrive with informed questions rather than generic ones.
Third, block out real time in your calendar for the first 30 days. This is not a job you can wedge into leftover evening hours in month one. Even if your steady-state tutoring load is part-time, the onboarding month is intense. Tutors who protect their time in month one ramp faster and hit steady state stronger.
Fourth, decide, honestly, why you are doing this. Refonte tutors come from many backgrounds: full-time engineers who tutor evenings, career transitioners consolidating their own knowledge by teaching, senior specialists who want to give back, researchers who want industry exposure. All of these are valid. But your motivation shapes how you should approach the role, how much you should take on, and what you should optimise for. Mentors will ask you about this in week one; having a clear answer helps.
Fifth, come with a growth mindset about your own teaching. Even if you have taught before, at university, in bootcamps, or informally, teaching at Refonte is likely to differ from what you have done. The pedagogical model is specific. The learner base is global and diverse. The feedback expectations are high. Assume you will learn a lot in month one, because you will.
If you are joining a technically demanding track, whether that is the AI Engineering program, one of our data engineering paths, or a cloud and devops track, make sure your hands-on skills are current. Rusty tools in a live session are painful; refresh them before day one.
Beyond Day 30: What Comes Next
The 30-day checkpoint is not the end of development. It is the transition from onboarding to ongoing practice. Tutors who clear the checkpoint enter a lighter but continuous cadence of support.
Every Refonte tutor has a quarterly review with their track lead. This review looks at session delivery quality, written feedback quality, learner outcomes, and the tutor's own development goals. It is a two-way conversation: tutors also flag friction points in the platform, the curriculum, or the operational model. Many curriculum improvements at Refonte Learning start as observations in these quarterly reviews.
Every tutor also participates in a peer feedback rotation. Twice a year, tutors review recorded sessions from peers on their track and provide structured feedback. This keeps everyone calibrated on what good looks like, prevents drift, and spreads new techniques across the tutor community. It is also how many tutors identify areas they want to improve in their own delivery.
Beyond that, senior tutors have paths into curriculum design, into mentoring new tutors themselves, and into track leadership. None of these are automatic; all are opt-in and earned through demonstrated work. But the paths are real, and many of our current track leads started as new tutors going through the same 30-day onboarding described in this article.
If you are considering applying to tutor at Refonte, the honest summary is this: the first 30 days are demanding, structured, and closely supported. You will not be thrown in the deep end. You will also not be able to coast. You will teach, be reviewed, get better, and by day 30 you will have a real body of work you are proud of, in front of learners whose outcomes you have already started to shape.
If that sounds like the kind of teaching environment you want to work in, the next step is to read how Refonte selects tutors, mentors and trainers and apply. Refonte Learning is continuously hiring across AI, data, cloud, devops, and software engineering tracks, and every applicant who clears selection goes through the onboarding described above.
The learners on the other side of your screen deserve tutors who took this month seriously. That is the entire point.