Snap-a-thon
Supported by
Participate individually or as a team to build snap-ins integrating various APIs, creating algorithms for generative content, and utilizing AI technologies to enhance digital engagement.
Hackathon Themes and Tracks
We have 3 tracks for the hackathon. Participants can pick up any one out of the 3 problem statements, and build a snap-in that satisfies the use-case.
🤝 From Code to Collaboration - Unify Developer Tools with DevRev
📊 Seamless Insights, Better Outcomes - Integrate Customer Intelligence with DevRev for Deeper Churn Insights.
🏢 Solution Templates for Businesses - Building Reusable, Industry-Focused Templates to Accelerate Adoption of DevRev
Hackathon Schedule
4th Feb, 2025
Registrations Start
Mon • 17 Feb 2025
Hackathon starts
7 PM - 9 PM IST: Session - What is DevRev (Join here)
Tue • 18 Feb 2025
7 PM - 9 PM IST: Session - How to build a snap-in
Wed • 19 Feb 2025
4 PM - 6 PM IST: Office hours + Session on snap-in development
8 PM - 9 PM IST: Office hours
9 PM - 10 PM IST: Session - Session by Replit
Thu • 20 Feb 2025
4 PM - 6 PM IST: Office hours + Session on snap-in development
8 PM - 9 PM IST: Office hours
11:59 PM IST: Deadline for proposal submissions
Fri • 21 Feb 2025
8 PM IST: Proposal result announcement
8 PM - 12 PM IST: Office hours
Sat • 22 Feb 2025
2 AM - 4 AM IST: Activity 1
11 AM - 12 PM IST: Session by DevRev Leaders
4 PM - 7 PM IST: Activity 2
Sun • 23 Feb 2025
2 AM - 4 AM IST: Activity 3
11 AM - 12 PM IST: Activity 4
9:30 PM IST: Soft deadline to start submissions
9:30 - 12:00 PM IST: Office hours for teams to submit their solutions.
Tue • 25 Feb 2025
Winner announcement
Prizes
Top 3
300
Rank 4-8
200
Rank 9, 10
100
Additional Prizes for high-quality, production-ready snap-ins
Base Compensation: $50 per snap-in (Prize money)
1 month of Replit Core to each participant that submits a valid proposal
Furthermore, we will have the following prizes for continued involvement with DevRev:
Maintenance & Refinement Bounty for Year 1: $200 per snap-in, per year
Maintenance Bounty for Year 2: $100 per snap-in, per year
Point Scoring Mechanism
Join DevRev Community: 2 points
Create and deploy a snap-in: 5 points
Getting their draft proposal reviewed: 5 points
Attending sessions on 17th and 18th Feb: 10 points
Submitting the proposal: 10 points
Submission Requirements
To proceed to make your submission for the hackathon, you'll first need to make note of the following things:
You should be a part of a single-member or a multi-member team (Size: 1-3 members)
Only the Team Admin/Leader can make the submission for the team
Things to remember
The minimal requirements for submission are:
Public Github repo link
Link to a video demoing your project (max length: 5 mins)
Comprehensive documentation detailing the project architecture, setup instructions, and usage guidelines.
Judging Criteria
Technicality
The level of technical skill demonstrated in the development.
Does the solution involve advanced problem-solving, algorithms, or use of DevRev APIs in creative ways?
Originality
Originality and creativity of the solution.
How unique or out-of-the-box is the snap-in? Does it bring fresh ideas to the DevRev ecosystem?
Usefulness to Businesses
Practicality and ease of adoption by businesses.
Is the snap-in solving a real problem?
How intuitive and easy is it for businesses to start using the snap-in with minimal onboarding?
Integration Quality
Code quality and production readiness of the snap-in.
Does it meet high standards for maintainability, scalability, and reliability?
Read more about integration quality standards here.
Documentation (Detailed README)
A comprehensive README that explains - Installation and setup instructions, Usage guide with examples, Customization details and Limitations, if any.
The README should ensure users can understand and deploy the snap-in easily.
Video Submission
A short (2-5 minute) video showcasing:
The problem the snap-in solves,
Key features and functionalities,
and a quick walkthrough of the working solution.
Working Demo in a DevRev Demo Org
The snap-in should be functional in a demo org for evaluation.
The judges should be able to interact with and test the snap-in without issues.
Tips for participants
Focus on Reusability: Think about how your snap-in can help multiple businesses, not just one specific use case.
Think End-to-End: Aim to deliver a solution that’s not just functional but also easy to adopt, with no manual setup hurdles.
Polish Your Presentation: A clear, concise, and engaging video or demo can make a big difference.
Test Thoroughly: Ensure your snap-in is robust and works as expected in various scenarios.
Submissions • 0
FAQs
What’s the allowed team size?
Who should participate?
What are the expected deliverables?
Where can I learn more about DevRev's APIs and the snap-in framework?
Will we be provided access to any LLMs?
Have more questions?
© 2025
Peerlist Inc.
Want to host a hackathon?
Contact us