Web DevelopmentMobile DevelopmentArtificial IntelligenceMachine LearningData Science
Event Type
in person
165
Participants
14
Est. Projects
Organizers
Alex Johnson
alex@example.org
Jamie Rivera
jamie@example.org
Bug2Build – Event Overview:
Bug2Build is a high-intensity, team-based coding competition.
It focuses on real-world debugging, problem-solving speed, and team collaboration.
The competition simulates real software development environments.
Participants are tested on debugging, communication, and collaborative development under strict time constraints.
Event Location:
Address:CWC3+HRX, Saswad Road, Near Bopdev GhatKJEI Trinity Campus, Yewalewadi RoadSurvey No. 25 & 27, Kondhwa AnnexSaswad–Bopdev–Pune RoadKondhwa, Pune, Maharashtra – 411048
Guidance & Onboarding:
A dedicated guidance session will be conducted after successful registration.
The session will explain the competition flow, rules, and evaluation criteria.
Technology & Project Selection:
Projects and programs will be assigned based on team expertise.
After registration, teams will receive a form to specify their preferred programming language.
The focus is not on the technologies you know, but on how effectively you debug and collaborate as a team.
Event Objective:
Bug2Build aims to evaluate:
Debugging proficiency on real-world codebases
Logical thinking and analytical skills
Team collaboration and communication
Ability to work under pressure and manage time
Team Composition:
Team size: 2 to 4 members
Participation is strictly team-based
Team members cannot be changed after registration
The same team must participate in all rounds
Competition Structure:
The competition consists of three rounds, each testing different aspects of software engineering.
Round 1: Bug Fixing Challenge (Non-Elimination)
Duration: 45 minutes
Objective: Identify and fix critical bugs in a given codebase
Format:
Each team receives a GitHub repository with 3 major bugs
Bugs may include logical errors, runtime or compilation issues, and broken or incomplete functionality
Teams must submit a working solution within the given time
Evaluation Criteria:
Correct identification of bugs
Successful fixes
Code stability and correctness
Partial fixes may receive partial credit
Note:
No elimination in this round
Top-performing teams gain a score advantage
Round 2: Rapid-Fire Debugging (Elimination Round)
Duration: 30 minutes
Objective: Solve multiple debugging problems quickly and accurately
Format:
Teams receive 10 independent mini bug-fixing problems
Problems can be solved in any order
Emphasis on speed, precision, and understanding
Evaluation Criteria:
Number of correctly solved issues
Accuracy of fixes
Time efficiency
Only shortlisted teams advance to the final round.
Round 3: Code Relay (Final Round)
Duration: 1 hour
Objective: Build a complete solution using a relay-style collaborative coding format
Format:
The project is divided into 2 checkpoints
Each checkpoint is handled by a different team member
Code is passed sequentially between members
Rules:
Members can work only on their assigned checkpoint
Skipping checkpoints is not allowed
Final submission must integrate all checkpoints into a working solution
Evaluation Criteria:
Completion of all checkpoints
Code integration and functionality
Quality of handoffs
Team coordination and logical flow
Judging Parameters (Overall):
Functional correctness
Code quality and clarity
Problem-solving approach
Team collaboration
Time management
Rules & Regulations:
Strict adherence to time limits
Plagiarism, unfair means, or external help is prohibited
Internet usage allowed only if permitted by organizers
Submissions must be made via the designated platform
Organizer decisions are final and binding
Disqualification Criteria:
Sharing solutions with other teams
Using unauthorized tools or resources
Violating round-specific rules
Misconduct or disruption
Declaration:
By participating in Bug2Build, all participants agree to abide by the rules and regulations.
The organizing committee reserves the right to modify rules with prior notice.
Find Bugs. Build Better. Together.
If you want this made shorter, poster-ready, or registration-page friendly, just tell me.