Are you ready to prove your Full-Stack Development prowess?
HackerEarth presents FullStack Forge: Code, Build, Innovate—a battle for supremacy in the world of web development!
This hackathon is designed for developers to push their limits, create innovative full-stack applications, and compete against the best in the industry. Whether you're a seasoned developer or a rising star, this is your chance to showcase your ability to architect, develop, and deploy scalable web applications.
What You Need?
- A Laptop: Your weapon of choice for the hackathon.
- A Calm Mind: Stay focused, innovate, and overcome coding challenges.
- Internet Connection: You'll need to be connected to submit your project.
Why Participate?
- Compete with top full-stack developers worldwide.
- Showcase your problem-solving and coding skills.
- Win exciting rewards and gain industry recognition.
- Build a project that could kickstart your next big opportunity.
Are you ready to take on the challenge? Join now and let your code define the future!
Project Scope & Requirements
Participants must develop an original project that solves a real-world problem and meets the following essential requirements:
- The project must belong to a relevant domain such as e-commerce, healthcare, finance, education, social networking, etc.
- It should be a complex, full-fledged working application, not a simple CRUD-based system.
- The solution should demonstrate innovation, scalability, maintainability, and industry relevance.
- The project should be structured using modular, reusable, and optimized code.
- Minimum 5000 lines of code across the project.
- At least 10 distinct source code files must be written by the candidate.
- Each functionality must be covered with appropriate test cases.
- Candidates must provide clear project setup and execution instructions.
- The code must adhere to industry coding standards and best practices.
Allowed Technology Stack
- Backend: Any backend technology
- Frontend: Any frontend framework
- Full Stack: Any full-stack combination
- Database: Any database solution
- Additional: Authentication, Authorization, Caching, API Documentation
Project Structure Guidelines
All project submissions must be structured and include:
Min. Mandatory Requirement
- Number of files: Min. 20
- Lines of Code: Min. 3000
- Number of test cases: Min. 70
- Project should be provided with:
- Clear problem statement
- Solution approach
- Supporting documentations wherever required
Source Code
- Located inside src/
- Should follow proper modularization and separation of concerns
Test Files
- Located inside tests/
- Should include unit and integration tests
Configuration & Setup Instructions
- README.md must include:
- Project description
- Installation steps
- Setup commands
- Execution instructions
- How to run tests
Documentation (if applicable)
- Located inside docs/
- API Documentation (Swagger/Postman Collections)
Testing Guidelines
Each project must include test cases to ensure functionality, correctness, and efficiency.
- Unit Tests: Covers individual components/functions (Mandatory).
- Integration Tests: Validates interactions between modules (Mandatory).
- Performance Tests: Assesses scalability & response time (Optional).
- Security Tests: Ensures authentication & authorization integrity (Optional).
Test Case Structure:
- Input: Description of input values.
- Expected Output: Predicted result from the function/module.
- Actual Output: The actual result produced.
- Status: Pass/Fail.
Participants may use any preferred testing framework for backend and frontend.
