Leading 100+ Engineers Through High-Stress Sprints: My Wild Hacktoberfest & HNG Story

Description and use

Leading a 50‑100 engineer distributed team through a 14‑day sprint resulted in a deployed web app and 150+ GitHub contributions, achieved via clear documentation, CI/CD automation, and asynchronous workflow.

Problem

Managing a distributed cohort of 50‑100 interns with varied schedules, connectivity, and skill gaps while delivering a functional web app and 100+ GitHub contributions in a 14‑day sprint.

Outcome

Delivered a functional web app, 150+ contributions, and 50 real‑user tests within 14 days while leading a distributed team of up to 100 interns.

Workflow

• 1. Volunteered as Team Lead and Technical Lead. 2. Established asynchronous clarity: documented workflows, issue templates, and PR guidelines. 3. Configured GitHub Actions for CI/CD and automated contributor list generation. 4. Coordinated sprint tasks across distributed team members. 5. Reviewed first‑time PRs and provided feedback. 6. Deployed the web app and conducted live testing with 50 users. 7. Celebrated deliverables by aligning sprint goals with Hacktoberfest requirements.

Evidence

Managing a massive team where contributors faced varying schedules, connectivity constraints, and limited availability across different regions meant workflow chaos was constant.

Source

Shipped & Battle-Tested: Took a functional web app from concept to deployment, testing it live with over 50 real users.

Source

100+ GitHub Contributions: Logged over a hundred contributions spanning direct commits, structured GitHub issue creation, and pull request reviews.

Source

Built and configured GitHub Workflows (CI/CD / Actions) to automate background tasks, including automatically updating and generating the contributor list/page for the repository.

Source