Inside a Session
We start wherever the student is. Sometimes that's a calculus problem due tomorrow. Sometimes it's a question they've been carrying for weeks. I listen first.
Then we work the problem together, out loud, so they hear how an engineer's mind moves through complexity. Not just the answer — the thinking. The pauses. The wrong turns that teach you more than the right ones.
From the solution, we extract a model — a reusable mental framework the student owns. Then a few short reps. Not busywork. Just enough to make it stick. And at the end, one minute of reflection: what clicked, what didn't, what they want to carry forward.
Some days we're putting out fires. Some days we're building something new. And always, underneath everything, we're working on the person.
After the Session
The session ends. The work product doesn't. Every family receives a written summary of what we tackled, where the student stands, and what comes next — drawn from the full session transcript with an AI-assisted review system I built and review myself, so the details carry into the next meeting.
Students get something rarer: a worked-solutions packet. Every problem we solved together, typeset to publication quality — clean notation they can actually study from, not photos of a whiteboard. Explore a real worked guide — the opening pages of a real 34-page exam-review guide. Only the name has been removed; the family received the complete guide.
And each semester, we sit down as a family: progress, goals, and whatever questions you're carrying. If something cannot wait that long, ask and we will find a time to talk. That access is for context and partnership decisions, not on-demand homework help or daily reminders.
One real summary, sent the same night — names changed, dates removed
Hi Rachel and Tom,
A quick recap of tonight's session.
Focus of the session
We worked through the first 15 problems of the Unit 10 review packet together ahead of tomorrow's test. I also sent Sam the full worked-solution packet so he can review the remaining problems tonight if he'd like.
Topics included:
- repeating decimals as geometric series
- sigma notation and arithmetic-series sums
- interval-of-convergence problems
- explicit formulas for alternating and fractional sequences
- the lottery/perpetuity problem
- the Taylor series for ex
- the Test for Divergence
- finite and infinite geometric sums
What went well
- Sam showed strong number sense throughout the session. On one sigma-notation problem, he bypassed the standard algebra and came up with his own mental shortcut immediately — fast and correct.
- On several sequence problems, he independently identified the underlying structure before I prompted, including spotting when rewriting a middle term revealed the hidden pattern.
- He also caught a setup trap right away on a shifted-index summation problem, which is exactly the kind of thing these review packets are designed to test.
- The strongest conceptual moment came during a divergence-test problem. He kept pressing on why a certain expression approaches a constant instead of zero, and once we connected it to cancelling leading terms in rational expressions, it clicked cleanly for him.
Looking ahead
- Wednesday — Unit 10 test
- Thursday, and Tuesday next week — pivot into final-exam prep
- The following Wednesday — possible final-exam exemption interview
- Thursday — becomes optional if the exemption is granted
- Friday — final exam, if needed
Overall, a strong review session. Sam was engaged, asking good questions, and showing real growth in the pattern-recognition side of the unit.
Warmly,
Matt
The packet he mentions is the same one linked above.
Three Modes, One Mentor
When a grade is slipping, we stabilize. Problem talk-alouds, a structured weekly plan the student owns, reusable models that replace the nightly scramble. The goal is a clearer plan, stronger understanding, and more consistent execution.
When the fire is out, curiosity leads. Mini-courses on how CPUs actually work. Startup sprints. Logic labs. Enrichment is not a separate handoff or add-on; it emerges naturally when a curious student works with a practicing engineer.
Across all three modes, we build metacognition and self-direction. The student learns to debug their own reasoning the way an engineer debugs a system: watch it run, find where it goes sideways, and adjust the pattern rather than only correcting the answer. Those habits can outlast any single class.
See how that adapts for students who need AP and honors STEM tutoring or for twice-exceptional and gifted students whose school performance does not reflect their ability.
The Commitment
I keep this practice deliberately small so I can prepare for and review each student's work personally.
Engagements are month to month, with no contracts and no minimum term. Meaningful change still needs runway, but the arrangement stays flexible and the work has to remain useful to the student and family.
Sessions are weekly or twice-weekly, 50 minutes. The student owns their plan — my role is mentor, not manager. Parents receive a written summary after every session, a typeset packet of every problem we worked, and a semester review on progress and goals. If something can't wait for the semester mark, ask and we will find a time to talk.
With 24 hours' notice, I make a best effort to reschedule within the same week. Limited Sunday overflow helps, but a replacement time cannot be guaranteed. Read the practical FAQ for holiday, privacy, and service-boundary details.