JobSpark

JobSpark
The one stop platform to find all junior level jobs
Choose your industry
View all junior level jobs in one page
Application architecture

Inspiration

Fresh grads and university students always find it difficult to find jobs since they have no experience. There are many jobs available that do not require any experience. However, these jobs are scattered across all kinds of different job portals. Since fresh grads will likely have to apply to many of these jobs to even get an interview, manually going to all these job portals to search can be troublesome.

What it does

JobSpark intends to be that spark to kick start your career! JobSpark It gathers all kinds of jobs that require no experience from more than 10 different job platforms (more to be added soon) from various industries. It then displays all of it in a single page for you to easily apply to each one.

How we built it

The client facing frontend was built in React with Bootstrap. Everytime a user clicks on an industry to view the jobs page, the client will make a request to the backend server built with Node.js and Express. The job listings are retrieved from a MongoDB database. We get the actual job listings from various job portal APIs. We aggregate them for the user.

To ensure that we do not overload these APIs for jobs, we cached these job postings in our MongoDB database. This is done by a Python CRON worker that run a CRON schedule once a day and collect the various job postings from the different APIs. It then caches them in the database. Our backend server will run a custom filtering algorithm to filter jobs and only get jobs which do not require any experience. The jobs are also filtered according the industry requested by the user. These jobs are then returned to the client.

Application architecture:

Challenges we ran into

Ran into many incompatibility issues as well styling issues. But we were able to fix them and finish the project.

Accomplishments that we're proud of

The application's design and user interface turned out to be quite visually appealing. Even we were surprised! Also, the architecture that we came up with to prevent from overloading the APIs were also innovative and unique. We went with a slightly more complicated architecture than sticking to a basic architecture that would not have been extensible.