This event is part of the Hack All February series (Week 3). You can participate solo or with a team of up to 4 members. Teams can change per hackathon - you don't need to have the same team members for all hackathons in February. You can even go solo in some and team up in others.
The more Accomplish features you use, the better your chances. File management, document creation, browser automation, custom skills - use them all. Check out the resources section for ideas and setup guides.
You must build a new project during the hackathon. Simply modifying an existing codebase or app is not allowed - Frank never used the same fake check twice.
All design elements, code, and assets for your project must be created during the event. You may use third-party tools, frameworks, open-source libraries, public APIs, and publicly available assets (e.g., Creative Commons images, fonts, or music).
Teams can plan and discuss ideas in advance, but coding and design work should start only after the hackathon begins. Written notes, sketches, and diagrams are allowed before kickoff - think of it as casing the joint.
Focus on automating real day-to-day tasks using Accomplish. Projects must involve building software (hardware components are optional).
Teams may consist of 1–4 members.
While interviews don't guarantee a job, they provide a genuine chance to showcase your skills and access potential roles at Accomplish.ai.
Any intellectual property developed during the hackathon belongs to the team that created it. Teams are encouraged to agree internally on IP ownership, though this is not mandatory.
Please treat all participants with respect. Act kindly and professionally. Harassment, discrimination, or exclusionary behavior of any kind will not be tolerated. If you see something concerning, notify an organizer immediately.
Failure to follow these rules or the Code of Conduct may result in disqualification and a permanent ban from future events. Unlike Frank, there's no second act.
Submit Your Project
Ready to show off your automation? Only one person from a team needs to fill the submission form. Make sure you have your GitHub link, deployed link, and a YouTube demo (max 3 minutes) ready!