Throughout both phases
Code review, interview prep, and real feedback from someone in the industry.
Code review, portfolio polish, and interview prep from someone in the industry.
Biweekly 30-45 minute sessions alternating with career coaching. Your mentor helps you get the most out of your internship placement, reviews your code and architecture decisions, and prepares you for technical interviews, including take-homes, system design, and coding challenges.
Common challenges
- Code works but you don't know if it meets professional engineering standards
- No experience with the kind of code review that happens at real companies
- Technical interviews feel disconnected from the work you've been doing
- GitHub profile shows projects but doesn't clearly communicate engineering quality
How this track helps
- Code review from a working engineer who sees real production codebases every day
- Technical interview prep tied to your target stack and role level
- Architecture and design feedback that improves your actual internship work
- A GitHub that shows thoughtful, reviewable engineering, not just shipped code
What a mentorship session looks like
Sessions are 30-45 minutes, alternating with career coaching every other week. Each session starts with your current work: what you shipped, what you're stuck on, what's coming up. Your mentor reviews real code and gives real feedback. Not textbook answers.
- Code review on your actual internship PRs and recent commits
- Architecture discussion: 'why did you structure it this way?'
- Technical interview dry runs modeled on real take-home formats
- Stack-specific feedback from a mentor working in your target area
Mentorship Session
David R. (Mentor) · Week 9
Reviewing
Token expiry should be configurable via env var, not hardcoded
Why are you storing refresh tokens in localStorage? Walk me through that decision.
Middleware separation is clean. This is exactly the right abstraction.
Next session: System design intro · Week 11
Interview prep grounded in real work
By the startup phase, your technical mentor shifts almost entirely to interview readiness. You're not starting from scratch. You're drawing on months of real internship experience and applying it to how companies evaluate candidates.
- Timed take-home assessments reviewed with detailed written feedback
- System design sessions at your target level, junior or mid
- LeetCode and algorithmic prep structured by pattern and frequency, not volume
- Mock technical screens with feedback on communication, not just correctness
Technical Interview Prep
Marcus T. · Startup phase
Recent Take-Home
Build a rate-limited API endpoint
Completed in 3.5 hrs · Submitted for review
Mentor note: "Clean abstraction. Add tests for the edge case where the window resets mid-request."
DSA Patterns
What you get out of it
Concrete outcomes you take with you when this track is complete.
Ready to start the Technical Mentorship track?
Apply now and show us what you can build. The admissions project is how we get to know you.
Frequently asked questions
Common questions about the Technical Mentorship track.
- What's the mentor's background?
- Mentors are working software engineers at companies ranging from funded startups to larger tech organizations. We match based on stack familiarity and your target role type.
- What if the mentor and I aren't a good fit?
- Tell us. Mentor fit matters to the quality of the work. We take this seriously and will work to find a better match if needed.
- How much LeetCode prep is there?
- As much as is realistic and efficient. We don't believe grinding 500 problems is the right approach. We focus on patterns, communication, and fundamentals that compound.
- Do mentors help with specific technologies?
- Within reason. Mentors are generalists-first. If you're targeting a very specific stack, we'll try to match you with someone who has that background.