Skip to main content [Tab]
AM
Asib Mahmud
Community • Teamwork • Leadership

The Polaroid Wall & Timeline

Beyond individual commits: leading student workshops, 48-hour hackathon sprints with interdisciplinary teams, and building developer culture at university.

[PHOTO PLACEHOLDER]

Photo of university computer club workshop with students collaborating around screens

2023 – 2025
“Campus lab workshop — debugging OpenCV setup [2024]”
Technical Community2023 – 2025

●[ROLE / INITIATIVE: Technical Club Leadership & Workshop Convener]

●[UNIVERSITY / COMMUNITY NAME: University Computer Society / Software Club] • ●[e.g. Lead Technical Organizer / Vice President]

Community isn't about lecturing from a stage; it's about making sure junior students don't get stuck on Git merge conflicts or environment setups alone at 2 AM. I organized recurring technical sessions covering web development fundamentals and machine learning basics, focusing on live coding rather than slides.

Key Milestones:
  • ✔●Conducted [NUMBER: 6+] technical workshops on modern web stacks and Python
  • ✔●Mentored [NUMBER: 40+] junior engineering students through their first web projects
  • ✔●Coordinated campus hackathon logistics for over [NUMBER: 150+] student participants
[PHOTO PLACEHOLDER]

Team huddled around laptops and a whiteboard diagram during a hackathon sprint

2024
“Final sprint pitch at 4 AM — team whiteboard architecture [2024]”
Teamwork & Hackathons2024

●[HACKATHON / PROJECT SPRINT: 48-Hour Rapid Prototyping Challenge]

●[EVENT: National / Regional Hackathon or Innovation Challenge] • ●[e.g. Lead Frontend & System Integrator]

Hackathons are the ultimate test of engineering communication. When the clock is ticking down and caffeine is running low, you learn how to make rapid technical compromises, decouple client and server dependencies, and pitch a cohesive prototype to a non-technical panel.

Key Milestones:
  • ✔Built and deployed the functional web interface within the 48-hour deadline
  • ✔Integrated live sensor inputs with an interactive real-time dashboard
  • ✔Collaborated across a 4-person team of designers, backend engineers, and domain researchers
[PHOTO PLACEHOLDER]

Project demonstration desk with testing hardware and presentation board

2024 – 2025
“Senior capstone demonstration day — presenting edge vision rig [2025]”
University Co-Curricular2024 – 2025

●[CO-CURRICULAR: Software Project Exhibition & Peer Review]

●[DEPARTMENT: Department of Software Engineering / Faculty of IT] • ●[e.g. Capstone Project Presenter & Peer Reviewer]

Software engineering coursework is at its best when tested against adversarial peer reviews. Participating in departmental exhibitions required explaining architectural tradeoffs to visiting software architects and defending database schema choices against harsh performance benchmarks.

Key Milestones:
  • ✔Presented software architecture and threat modeling to faculty review panels
  • ✔Collaborated in agile team sprints adhering to strict Git branching and pull request reviews
  • ✔Evaluated junior year team deliverables on code modularity and test coverage
[PHOTO PLACEHOLDER]

Informal developer meetup around a shared table with coffee and laptops

2023 – Present
“Open source Saturday meetup — writing our first pull requests”
Mentorship & Workshops2023 – Present

●[MENTORSHIP: Git Fundamentals & Open-Source Onboarding]

●[COMMUNITY: Local Developer Circle / Student Tech Community] • ●[e.g. Open-Source Guide & Code Reviewer]

Many talented students hesitate to contribute to open source simply because making a public pull request feels intimidating. I created interactive walkthroughs breaking down issues, branch management, and writing respectful, constructive pull request descriptions.

Key Milestones:
  • ✔Created beginner-friendly walkthroughs for GitHub workflows and markdown docs
  • ✔Reviewed dozens of initial pull requests with actionable, encouraging feedback
  • ✔Advocated for accessibility and semantic HTML in student-led repositories
Team Dynamics

Software engineering is a team sport.

Leading workshops and collaborating in high-pressure hackathons taught me how to communicate technical decisions clearly, listen without ego, and ensure every teammate feels equipped to do their best work.