Recruitment Relationship Management (RRM)

Alternative Text
by Dmitry Elisov
Oqtacore CTO
745

Table of content

alt

Problem

The company needed a very fast solution with software for the IT recruitment process. Current solutions that exist on the market are not specialized enough for IT, and do not account for programming languages, stack, software, years of experience.

The software needs to be developed immediately and turned into production in 2-3 weeks, and then it should be upgraded gradually to fit the needs of the company. After 3-4 months, the resulting product should have a clean rebuild with the same features, but better architecture and scalability.

Plan

Since we had just 2 weeks, we couldn’t spend a lot of time coming up with innovative design, building architecture or writing many-page specs.

2 weeks is just 10 working days, so the time was very limited.

Instead we came up with a plan: take some existing software as a starting point, select the most needed functionality from it, and enhance with IT-recruitment-specific features

Implementation

The stack for the project is .Net for backend and Angular for frontend.

We found the software that looks the most compelling to the Customer. It doesn’t have many needed features, but its overall design and structure seem suitable.

Taking the main ideas of the UI took about 4 work days, so we had some time left to implement the features the Customer needed: meeting calendar, technical screening results, candidate statuses.

 

Recruitment Relationship Management (RRM) window

 

Recruitment Relationship Management (RRM)

 

Result

In just 2 weeks we created the MVP of the product, that was moved to production stage and is used by one recruiter. The MVP is being updated by our team weekly based on feedback.

Rate this article
Please wait...