Inspiration
Recently I was in conversation with a friend who works in UX. He was finding it difficult to land a job. He was narrating horror stories about how much time was being invested in interview processes and in completing sample projects, to not even hear back from the hiring teams. It almost felt like he was doing free work in the guise of recruitment for a lot of these companies. It seemed unfair to me that such skilled and qualified candidates have to go through such pain to work for someone else!
Typically all the solutions in the recruitment space are heavily focused on making the process easier for employers. I wanted to build something that focuses heavily on the job applicants and tries to make the process easier for them!
What it does
Jobby lets you land your dream job faster.
In Microeconomics, the study of matching markets tries to understand markets where all the actors in the market are trying to establish mutually beneficial relationships. Examples of this include, the world of dating. Or matching prospective students with schools. Or our example, where job applicants and employers are trying to find each other in the labor market.
In all these examples, you have to search and find as much information as possible about the other party before finding a match that is the best choice for you.
Two things that will help you be successful in this task are:
- The amount of information that you have about all the market participants
- The speed with which you can process all this information
Jobby helps you with both of these, by sourcing in-depth data from various sources about companies, jobs, and the labor market and by bringing them onto a single platform. The data helps applicants really narrow down the companies and jobs that are a match for them, and also helps them identify the right times to apply for various roles. This is then combined with a powerful tracking tool to help applicants manage their job applications more efficiently without them having to build trackers from scratch.
Increased adoption of the platform also leads to the creation of newer data sets (metrics on recruitment cycle timelines and duration) that can provide even further insights into the recruitment process and also cause a change in behavior from employers.
How we built it
Jobby was built on a hosted Oracle Database. The application front-end was built using Oracle APEX.
Challenges we ran into
The language used to build the app was PL/SQL. There were no SDKs available for PL/SQL. This was a challenge for authentication.
This was the very first time that I am using any AWS service. I came to know about the project a bit late after it was started and hence within the limited time I had to ramp up my understanding of the AWS ecosystem and then the specific service and then build a product using these services.
Accomplishments that we're proud of
I managed to build a custom signature process for signing AWS API calls in PL/SQL using the Version 4 signature process. I plan to publish details of the same and open source the code so that others using PL/SQL to build backend services can leverage AWS Data Exchange APIs.
Additionally, I am currently in the process of relocating to a new country. For the past two weeks, I was in the middle of a cross-country road trip as part of this move. Being able to make a submission on time despite this brings a huge smile to my face! :)
What we learned
Got hands-on exposure to the AWS ecosystem. Absolutely chuffed to see the level of documentation out there for AWS services. Excited to try and include more AWS services in future projects.
What's next for Jobby
Based on feedback received so far, there is good potential for user adoption if this is launched to the market. The immediate next steps would be to continue building towards an MVP and launch it to test the market.
Built With
- amazon-web-services
- javascript
- oracle
- oracle-apex
- plsql
- sql


Log in or sign up for Devpost to join the conversation.