About

Saranda Coding Contest

Code, Complete, Conquer

Powered by Saranda Tech Community, this contest is meant to guide students on their first steps towards Competitive Programming.
If required we may also use this contest's results as a base to select students in forming teams in the Margazhi Fest's events.
Together, let's bring 🔥SARANDA ON TOP🔥 this Margazhi

Prizes

All the valid winners of the contest will be mentioned in you Social Media handles.
Winner of this contest will be given priority in case we need to form teams in any Tech events in the upcoming Margazhi'26

Rules

The creator of this contest is solely responsible for setting and communicating the eligibility requirements associated with prizes awarded to participants, as well as for procurement and distribution of all prizes. The contest creator holds HackerRank harmless from and against any and all claims, losses, damages, costs, awards, settlements, orders, or fines.
Code directly from our platform, which supports over 30 languages. Learn more here.

Rules and Regulations to be followed during the contest

To ensure a fair and competitive environment, all participants must strictly adhere to the following regulations. Failure to comply will result in immediate disqualification.

note: Please fill registration form sent via announcements before entering the contest. Without this, the praticipation will not be considered valid.

Mandatory Virtual Presence

Check-in: All participants must join the provided Google Meet link with with their Student ID at least 10 minutes before the contest start time for a mandatory briefing and identity verification.
Attendance: You must remain in the Google Meet room for the entire duration of the contest. Leaving the meet before the official "End of War" announcement will lead to an automatic disqualification.
Meet Link: will be shared directly via a Google Calendar invite.

Screen & Audio Monitoring

Screen Sharing: Participants are required to share their entire screen (not just a window or tab) on Google Meet for the duration of the competition.
Microphone Status: Mics must remain on Mute at all times to prevent background noise from disturbing other contestants, unless addressed directly by a proctor.
Camera Policy: Front-facing cameras must remain ON, ensuring the participant's face is clearly visible within the frame.

Code Integrity & Anti-Cheat

Zero Tolerance: Any form of cheating, plagiarism, or pre-written code injection is strictly prohibited.
Code Sharing: Sharing your code, logic, or hints with other participants (or receiving them) will result in an immediate Permanent Ban from the current competition.
Plagiarism Check: All submitted solutions will be processed through an automated plagiarism detection engine (MOSS) post-contest.
LLM or other AI tools: usage to generate code is strictly prohibited.

Technical Constraints

Authorized Tools: You may use any standard IDE (VS Code, IntelliJ, CLion, etc.) or web-based editors.
Internet Usage: Accessing documentation (cppreference, Java Docs, Python Docs) is permitted. However, accessing forums (StackOverflow, GeeksforGeeks), AI tools (ChatGPT, Claude, Copilot etc.), or communication platforms (Discord, Telegram,WhatsApp etc.) is strictly forbidden.
Single Device: Only one laptop/PC is allowed per participant. The use of secondary monitors, tablets, or smartphones is prohibited.

Scoring

Scoring System & Leaderboard Logic

Point Distribution

Each problem in the contest is assigned points based on it's difficulty level ranging from 200 to 1800

Submission Policy

Best Effort (Standard Challenges): If you submit multiple solutions for the same challenge, the system will automatically record your Highest Score achieved across all attempts.
Game Challenges (Last Submission): In specific "Game-style" or "Interactive" challenges, the score will reflect your Last Code Submission only. Ensure your final submission is your most stable version.
Penalties: For every wrong submission there's a penalty of 5 minutes except in the case of a compilation failure during the submission evaluations.

Tie-Breaking & Ranking

Participants are ranked primarily by their Total Score. In the event of a tie where two or more participants have the same score, the following tie-breaking criteria will be applied in order:

Last Submission Timestamp: The tie will be broken by the Total Time Taken to submit the last solution that resulted in your highest score.
Efficiency Factor: If the submission times are identical, the participant with the fewer number of total incorrect submissions (penalties) will be ranked higher.
Code Execution Time: As a final resort, the average execution time (CPU time) of the successful submissions will be compared.

Submission Status Guide

Status	Meaning
AC (Accepted)	Your code passed all test cases perfectly.
WA (Wrong Answer)	The output produced by your code does not match the expected result.
TLE (Time Limit Exceeded)	Your algorithm is not efficient enough for the given constraints.
RE (Runtime Error)	Your code crashed (e.g., Segmentation fault, Division by zero).
CE (Compilation Error)	The code failed to compile on our judge's environment.

Pro-Tip: Focus on accuracy first. A single "Accepted" solution is often worth more than multiple "Partial" solutions in the final standings.

Saranda Coding Contest - Jan'26

Let's bring 🔥SARANDA ON TOP🔥 this Margazhi

to

Starts in