MLH Fellowship - Software Engineering Track

Grades

Open to high school students and early-career developers; no specific grade level restriction mentioned, but intermediate to advanced coding proficiency required

Age

No explicit age requirement stated; appears to focus on coding ability rather than age

Citizenship

Open to international applicants; US residents may receive tax documents; international students studying in US may need to consult their university regarding CPT/OPT compliance; note: currently NOT available in APAC region due to employer hiring focus

Prerequisites

Proficiency in at least one programming language (intermediate to advanced); experience working on multiple projects using that language; ability to solve real-world practical problems; proficiency with Git, GitHub, and GitLab; English communication ability; reliable A/V setup for remote participation; commitment to 20 hours per week (~15 hours project work, 5 hours mentoring/learning)

Steps

1. Complete application form with essay responses about your background and motivation
2. Submit code sample (GitHub project) demonstrating your skills
3. Participate in technical interview with MLH mentor where they discuss your code and coding experience
4. Provide required documentation and sign participation agreement
5. Attend orientation if accepted and matched to a project

Materials Needed

• Resume or CV highlighting relevant experience
• Code sample (GitHub project showing practical problem-solving)
• Essay responses (critical component—essays reviewed first; bare-bones responses may disqualify application before code review)
• Documentation/verification of eligibility
• Ability to pass technical interview
• Valid A/V setup (camera and microphone for remote work)

Timeline

Applications processed on rolling basis with multiple batches per year; applications close a few weeks before each batch begins; once accepted, may take 1-2 weeks to be matched to a project (timing depends on when final project details finalized with sponsors); program runs 12 consecutive weeks with Monday-Friday scheduling

Cost

FREE to apply; no application fee; participants receive educational stipend to offset costs during select programs; US residents may receive tax documentation for stipend

What Judges Look For

• Strong, personal essay responses that tell a unique story—specifically: how you fell in love with coding, hackathons, or the CS community (not just generic 'I need a job' responses)
• Code quality and problem-solving ability demonstrated in submitted GitHub projects
• Technical proficiency in at least one primary programming language (JavaScript/TypeScript, Python, or C/C++/C# most common, but any language acceptable)
• Experience with Git, GitHub/GitLab collaboration workflows
• Ability to articulate your coding interests and passion during technical interview
• Timezone and weekly availability match for pod assignment
• Growth trajectory and continuous learning demonstrated through portfolio

Scoring

Not explicitly detailed, but application essays are first screening layer—weak essays may prevent code sample review; code sample then evaluated for clarity of problem-solving approach, code quality, and alignment with available projects; technical interview assesses live coding ability, communication, and learning potential; final review considers holistic fit for matching to specific projects and pod cohort

Common Mistakes

• Submitting generic, bare-bones essay responses without personal narrative or unique story
• Not explaining WHY you're passionate about coding beyond resume-building or job seeking
• Submitting code samples that don't reflect your best current skills or that you can't explain well
• Not demonstrating familiarity with Git/GitHub workflows in submitted projects
• Failing to show growth or learning trajectory in portfolio
• Poor communication during technical interview (not explaining your thought process)
• Overstating or misrepresenting coding experience level
• Not researching the program or showing genuine interest in learning from mentors

Acceptance Rate

Highly competitive (exact rate not disclosed); MLH notes 'overwhelming demand from students' and significantly more applicants than available projects

Applicants

Not officially published; described as receiving 'overwhelming demand' suggesting hundreds to thousands annually

Winners / Selected

500+ program graduates total across all cohorts; typical cohort size appears to include multiple pods (10 fellows per pod), suggesting 50-200+ per batch depending on available projects from sponsors

• CRITICAL: Invest significant time in essay responses; admissions team reviews essays FIRST before considering code sample, so weak writing can result in immediate rejection
• Tell a compelling personal story about why you love coding—what drew you in, what problem did you solve that excited you, what inspired you about the CS community
• Choose a code sample you can confidently explain and defend during technical interview; be prepared to walk through your thought process and design decisions
• Ensure your GitHub profile and submitted project demonstrate familiarity with professional Git workflows (meaningful commit messages, pull request practices, clean code)
• Include diverse coding experience in portfolio—show you've worked on multiple projects and problem types to demonstrate adaptability
• Before applying, strengthen your weaker areas: if unfamiliar with Git/GitHub, spend 2-4 weeks contributing to open-source projects or learning collaboration workflows
• Be honest about your experience level during essay and interview—MLH matches fellows by skill level to appropriate projects, so overstating helps no one
• Apply early in the batch cycle if possible—rolling basis means later applications face more competition for remaining spots
• Research the specific projects/companies you might work with (if available) and mention specific interests in your essays
• Prepare for technical interview by reviewing your code sample, practicing verbal explanations of coding concepts, and studying data structures/algorithms at your level
• Highlight any previous experience with pair programming, code reviews, or collaborative development
• If rejected, reapply to future batches while continuing to build your portfolio—admissions team sees history of applications and appreciates demonstrated growth
• Attend MLH hackathons and community events before applying to show genuine engagement with the MLH community and tech ecosystem
• Consider completing online courses in your target language before applying (e.g., Codecademy, freeCodeCamp, LeetCode) to strengthen fundamentals

How to Prepare

• Month 1-2 Before Application: Choose your primary programming language (if not already decided) and deepen proficiency through coding projects; start contributing to open-source projects to gain Git/GitHub experience
• Month 1 Before: Build or improve your code sample project—should be a complete, non-trivial project you're proud to present (tool, game, app, library, etc.); ensure code is well-commented and follows best practices
• 2-3 Weeks Before: Write and revise essay responses multiple times—have someone review them for clarity and emotional resonance; focus on storytelling, not just technical details
• 1-2 Weeks Before: Prepare for technical interview by reviewing your code sample, practicing explaining your thought process, studying algorithms/data structures relevant to your language
• Week Before: Test your A/V setup thoroughly; review the FAQ; prepare 2-3 questions to ask mentors during interview; research MLH and the program philosophy
• Day Before: Get good sleep; review your essays one more time; have your code sample link ready

Resources

• Official: fellowship.mlh.io, fellowship.mlh.io/faq, MLH Fellowship Info Sessions (YouTube/archive)
• Coding Projects: GitHub (explore trending projects), LeetCode, HackerRank, Codewars for skill building
• Learning Platforms: Codecademy, freeCodeCamp (Python, JavaScript courses), edX, Coursera
• Open Source: Good first issue sites, GitHub's beginner-friendly projects, Awesome for Beginners (GitHub repo)
• Git/GitHub: Official Git documentation, GitHub Learning Lab, Atlassian Git tutorials
• Interview Prep: LeetCode (coding interview preparation), Cracking the Coding Interview (book), AlgoExpert
• Writing: Have mentors/teachers review essays; use Grammarly for grammar check
• Community: MLH Discord (discord.mlh.io), r/learnprogramming (Reddit), r/cscareerquestions
• Portfolio: Personal GitHub profile, personal website/blog showcasing projects

Time Needed

6-12 weeks of consistent preparation recommended for someone with intermediate coding skills; if starting from beginner level, 3-6 months of learning before applying; ongoing (ideally 5-10 hours per week building projects and learning); essay writing/revision: 15-20 hours total; technical interview prep: 20-30 hours

Typical successful applicants have: 1-3+ years of coding experience in at least one language (often self-taught through courses, hackathons, or personal projects); comfortable with Git/GitHub; demonstrated passion for learning through side projects, hackathons, or open-source contributions; ability to articulate their technical interests and learning goals clearly; from diverse backgrounds including non-CS majors (50% of fellows), underrepresented communities (50%), and 30+ countries; age range varies but skews toward older high school students (juniors/seniors) and college freshmen/sophomores; not necessarily top computer science students, but students with genuine interest and growth mindset; many have attended MLH hackathons prior to applying; frequently describe themselves as self-motivated learners who build projects outside of formal education

Strong positive impact on college applications and career prospects: 1) Demonstrates real-world professional experience (not just school projects or tutoring), which top colleges value significantly; 2) Proves ability to work on actual production code and collaborate with professionals, differentiating student from peers; 3) Provides concrete accomplishments to discuss in college essays and interviews; 4) MLH Fellowship carries prestige due to selectivity and partnership with major tech companies; 5) Fellowship completion strengthens software engineering internship prospects at top companies (shows proven track record); 6) Stipend and remote nature make it accessible to more students than traditional Bay Area internships, potentially broadening diversity of participants; 7) Code samples and projects from fellowship can be featured prominently on portfolio; 8) Mentorship and professional references from MLH engineers are valuable for future applications; 9) Network of fellow cohort members can lead to future collaborations and career opportunities; 10) Admissions officers recognize MLH as legitimate organization (runs 2,000+ hackathons annually, established community). Note: Fellowship is classified as educational program rather than traditional paid internship, but provides similar or greater learning value—colleges view this favorably as evidence of initiative and self-directed learning.

• Simons Summer Research Program — Tier 2, summer program
• Elite Contest Coaching for Canada's Top Math Students — Tier 2, competition
• Canadian Computing Competition (CCC) — Tier 2, competition
• Dr. Charis Eng Monell Science Apprenticeship Program — Tier 2, summer program
• WOOT (Worldwide Online Olympiad Training) — Tier 2, enrichment