SkillBridge: Connecting Freelance Tutors with Students Seeking Personalized Learning

SkillBridge is a two-sided marketplace connecting freelance tutors with students who need personalized learning support. I joined as the founding product designer when the company was just an idea on paper, with no existing product or users. My role was to design the entire platform from scratch, including tutor onboarding, student search and booking, session management, and payment flows. Working with a founding team of 2 engineers and a CEO, I spent 6 months designing and launching the MVP that would validate whether people actually wanted this service. The challenge was building something simple enough to ship quickly but complete enough to test real marketplace dynamics.

Students struggling with specific subjects had limited options beyond expensive tutoring centers or unreliable Facebook groups. Parents wanted qualified tutors but had no way to verify credentials or read reviews. Meanwhile, talented teachers and subject experts wanted to tutor on the side but lacked a platform to find students. Existing solutions like Craigslist felt sketchy, and traditional tutoring agencies took 50% commission. The market needed a trusted platform that made it easy for students to find the right tutor and for tutors to build a sustainable side income, but nobody had built it yet.

• Marketplaces need both supply and demand to work, but we had neither. Tutors wouldn't join without students, and students wouldn't sign up without tutors. I had to design an experience that could attract early adopters on both sides simultaneously, knowing the platform would feel empty at first. The chicken-and-egg problem meant every design decision had to consider cold start dynamics.

• Parents needed to trust strangers with their kids' education and safety. Without an established brand or reviews, we had zero credibility. I needed to design trust signals into the platform from day one, but couldn't rely on social proof that didn't exist yet. Background checks and verification badges felt corporate, while casual profiles felt risky.

• Every feature we added increased development time and delayed launch. The team wanted to build messaging, video calls, scheduling, payments, and reviews all at once. I had to ruthlessly prioritize what was truly essential for the MVP while designing a system that could scale later. Cutting features felt risky, but building everything would take a year.

• Students needed different things depending on their situation. High schoolers wanted SAT prep, college students needed help with specific courses, and adult learners sought professional skills. Designing one search and matching experience that worked for all these use cases without becoming bloated was incredibly difficult. Too specific and we'd exclude users, too generic and nobody would find what they needed.

• I designed a tutor-first onboarding that made signing up feel like building a professional profile, not filling out a form. Tutors could showcase their expertise through subject tags, teaching philosophy, and availability calendar. The profile creation flow took 8 minutes but felt purposeful. We launched with a waitlist that let tutors join first, then invited students once we had 50 tutors. This sequenced approach solved the cold start problem.

• Instead of complex verification systems, I designed transparent tutor profiles that showed education credentials, teaching experience, and response time. Tutors could upload degree certificates and teaching licenses, which we manually reviewed. A simple "Verified Credentials" badge appeared after approval. For the MVP, we required video intro clips where tutors explained their teaching style, giving parents a gut check before booking.

• I mapped out the entire user journey and identified the absolute minimum viable flow: search tutors, view profiles, send inquiry, book session, pay. Everything else (messaging, video calls, automated scheduling) got pushed to post-launch. For MVP, students contacted tutors via email, scheduled sessions manually, and paid through Stripe checkout. It wasn't elegant, but it validated demand in 6 months instead of 18.

• I designed a flexible search system with three entry points: browse by subject, search by keyword, or filter by student level. Tutors tagged themselves with specific subjects and student types during onboarding. The search results showed tutor specialties upfront, so a calculus tutor wouldn't appear for SAT prep searches. This let us serve diverse needs without building separate experiences for each use case.