This is Copy of Master_Readme.md file.
Below is the list that defines which file is for which role:
- Readme_Backend_Leader_Architect.md - This file is for the role: Backend Developer + Leader + Architect
- Readme_Frontend_Dev.md - This file is for the role: Frontend Developer
- Readme_Devops_Fullstack.md - This file is for the role: Fullstack Developer + DevOps
- Readme_Generalist.md - This is for the role: Generalist Developer
Please make sure you are submitting the correct file for the role you are applying for. If you are applying for multiple roles, please submit the corresponding files. Note that we will not provide reenumeration for multiple submissions. And only completed submissions will be considered for the evaluation and reenumeration as discussed.
Dear Candidate,
First of all, congratulations and thank you for accepting this challenge. Please read this document to its entirety before starting any project.
You are among a select few who have been given this opportunity, and we are truly excited to see what you will build.
We understand that the scope of any of above project within the given time frame is demanding. However, we want to clarify that this is not because we do not value your time or effort; rather, it is because we are looking for someone extraordinary—someone who thrives under pressure, thinks critically, and delivers well-thought-out solutions even in challenging circumstances.
This project is not just about technical skills; it is a reflection of qualities like determination, problem-solving, time management, and the ability to persevere. These are the attributes we believe are essential for success in the role we are hiring for.
We want to assure you that we are flexible with the architecture you choose to implement(for applicable roles) as long as you follow the MVC architecture (optinal, for backend tasks, if it makes you slow but come up with reasoning why you opt for something else). For frontend, we do want you to use NextJS.
To make it easier, you can start by cloning one of the following boilerplate repositories:
- Clone this repository: Node.js/Express/Next.js Boilerplate
- Clone this repository: Flask MVC Boilerplate
-
For backend roles, while we would prefer the Node.js/Express/Next.js setup, we are open to you using Flask if you believe the implementation would be better suited for the project. If you choose Flask, provide reasoning for your decision—it will help us understand your thought process.
-
Additionally, if you need parts of the Next.js/Node.js boilerplate while working with Flask, feel free to clone both repositories and utilize whatever is necessary.
-
For Frontend roles, we would prefer you to use Next.js.
-
For DevOps roles, we would want you to make use of:
- Docker
- Nginx
- Github Actions for CI/CD
- Any Ubuntu based server for deployment
- Let's Encrypt for SSL
- PM2 for process management or any other process manager
- Any other tools you think are necessary
You can use any of these VPS provider to get free VPS to get started:
Rest assured, this challenge is not just a test; it’s an introduction to the kind of work culture you can expect here—a culture like no other in Nepal. We are building something exceptional, a workplace that fosters innovation, collaboration, and growth at a level rarely seen before. If you manage to pull this off, you will not just have the opportunity to join a team—you will become part of a transformative journey, one where your contributions will have real impact and where you will thrive in an environment designed to bring out the best in you.
We are rooting for your success, and we can’t wait to see your solution!
As part of this project, we kindly request you to self-report the time you spend on each task. This approach relies on honesty and transparency, which are qualities we highly value and will consider during the evaluation process and the interview.
We understand that different people work at different paces, and this is not about how fast you complete the project. Instead, this is about:
- Understanding your approach to time management.
- Seeing how you prioritize tasks within the given timeframe.
- Getting insight into your problem-solving process.
Please maintain a simple log that includes the following:
- Date: The day you worked on the project.
- Time Spent: How many hours you worked (approximately).
- Task Description: A brief description of what you worked on during that time.
| Date | Time Spent (hrs) | Task Description |
|---|---|---|
| 2024-11-28 | 3 | Implemented Ticket Locking |
| 2024-11-29 | 4 | Integrated Stripe Checkout |
| 2024-11-29 | 2 | Implemented Context API etc |
- Honesty is key: We trust you to report your time accurately. This will be considered during your evaluation and interview.
- It's not about speed: We are looking for thoughtful implementation and prioritization, not rushing through tasks just for the sake of completion.
- Doesn't mean we don't value fast work: While we appreciate thoughtful work, we also value efficiency. If you can complete the project quickly without compromising quality, that's a plus.
- Document thoroughly: The quality of your self-reporting reflects on your ability to work transparently and methodically.
- You will have a total of 1–3 days (calendar days) to complete the project from the time you receive this email.
- For example:
- Email Sent: Thursday, November 28
- Submission Deadline: Sunday, December 1, 11:59 PM (Nepal Time Zone)
We believe this timeline provides:
- Sufficient Time: To research, implement, test, and document the project.
- A Realistic Challenge: To showcase your ability to work under time constraints while delivering quality results.
We understand unexpected situations can arise. If you believe you need an extension, please communicate this to us as soon as possible. We may extend the deadline by up to 2 additional days, depending on the circumstances.
- Contact us at [email protected] to request an extension. Please provide a valid reason for the extension request and the details of yours:
- Your name in the application
- Role you applied for
- Email address
- Phone number
- Include your time log as part of the final project submission, either:
- In the project
README.md. - As a separate file named
TimeLog.md.
- In the project
- Be prepared to discuss your time log and decisions during the interview.
Thank you for your hard work and honesty!
Best of luck! You’ve got this.
Warm regards,
Cloudquish Team
Cloudquish LLC
Project Deliverables
Apart from mentioned deliverables in the respective Readme files, below are the deliverables we are expecting from you:
- Make sure to have below details on top of the readme.md file
- Your Name (same name as in application submission)
- Your Email
- Your Phone Number
- Role you applied for (you can find this in the top of this readme file)
- Your Address
- Time log (in the format mentioned above in Readme.md or TimeLog.md)
- Your Github Profile
- Your LinkedIn Profile
- Your Resume (If updated)
- Any other links you want to share (Optional)
- Fully functional system as per the requirements in each Readme file.
- Note that you can just push it to the github repo that you cloned from github classroom and we will be able to see it. No need to submit it anywhere else.
How to start the project?
- Clone the repository that you have been given access to.
- Read the Readme file of the role you are applying for.
- Start working on the project.
- Push the code to the repository.
- Make sure to have the time log in the Readme.md or TimeLog.md file.
- Make sure to have all the deliverables mentioned above and in the respective Readme files.
- We will review the code and get back to you for the next steps.
- Done