HireD

HireD

A decentralized, blockchain-powered Job portal app that connects job seekers and Companies without the involvement of any third parties.

Created on 18th April 2022

HireD

HireD

A decentralized, blockchain-powered Job portal app that connects job seekers and Companies without the involvement of any third parties.

The problem HireD solves

The problem it solves is the transparency issue between job applicants and companies by eliminating third parties in hiring processes. When a person applies for a job on one of these portals like LinkedIn, Indeed, etc, there is no transparency that the application is being submitted to that particular company. And even when it is, we don't know where our application stands in the queue. Also, in traditional job portal sites, there is an increased risk of data breach and user privacy is affected. We solve this problem by using the public Ethereum blockchain as the medium between the two parties and ensuring true transparency and negligible chances of a data breach. Also, in the future, we plan on including technologies like IPFS, to reduce the gas fees in our dapp.
So now, people can use our platform to look for jobs being posted in real-time directly by the companies on the chain, and also companies can get connected with the applicants directly without the involvement of any middlemen. We also plan on employing a digital asset-based verification of skills. Using this, people will no longer be able to fake their candidature and skills for getting shortlisted for jobs. We can do this by representing any skill or course certificate or even a degree as digital assets on the blockchain. Because of this, the skills and qualifications of a particular individual will always be authentic and associated with their ids.

Challenges we ran into

There were a lot of bugs and hurdles while building the project.

  1. It was difficult to integrate the Truffle environment having both ReactJS and Ethereum Smart contracts and I had to look into a lot of youtube videos and see documentation to get the correct implementation.
    2)Different implementations of Truffle had the .abi files of the contract at different places and I had to select the correct implementation to get my project working.
    3)I was getting memory leaks when running the app and it took me nearly 4-5 hrs to debug it. It was because I was using useEffect() and window.addEventListener() together and this was causing memory leaks.
    4)It was difficult to integrate all async() functions and web3 components and it took me some time to understand what was happening. Also, I passed a lot of props in the Route components and I had to console.log() at each event to check if everything worked well together.
    5)Handling Redux states and Metamask states together was a bit difficult

Discussion

Builders also viewed

See more projects on Devfolio