The problem Job Fynd solves

Our college uses bizotic for conducting workflows related to job placements. This application recreates the application with a better user experience and resolves bugs that have been observed within the existing solution.
Problem faced in bizotic

• Duplicate accounts: Students could duplicate accounts. To resolve this issue, we can only allow emails supplied by the college.
• Vendor lock-in: Bizotic is a generic solution used by many colleges. Job-fynd was created custom to our college-specific needs. Anyone can contribute to it since it's open-source.

Challenges I ran into

During the entire project duration, I had to try out various technologies before integrating them into the app and sometimes remove the existing technology and recreate it with something better.

• API routes: I started using next.js built-in API routes initially. Later realized that I was repeating the same logic in every route. I switched to next-connect where I added middlewares to do the repetitive logic. I later switched to tRPC, which also has middleware and type-safe APIs.
• Data visualization: I tried almost every library out there that could go well with the requirements. I used re-charts, which got the job done quickly. I later switched to vis-x , which is a low-level library. Despite being time-consuming to get done, it is very lightweight compared to re-charts.