@OmkarCodes@FamAppByTrio preliminary things:
- not a "clone"
- not a .* management software
- USP shouldn't be UI or frontend
should have
- good data modeling
- using relational db, unless document actually required
- queue/caching if required
- broken into 2/3 parts, small services
Hiring Interns for @FamAppByTrio's backend team.
Should have built good projects and understand how backends work.
Skip if count of DSA problems is the best thing you've done.