Frontend development and integration

RostJob is an HR platform where there are personal accounts for both applicants (with the ability to create resumes), as well as for employers and customers.

The project already existed on the market, but the site needed a complete redesign and functionality update. At the same time, the customer’s team was developing a new Ruby backend, and the task was to assemble a complete product as quickly as possible and bring it into production.

The main problem was not the design per se, but the resources and deadlines.:

• the backend team did not have time to implement the entire volume of the frontend part.
• the project required a quick launch
• the old website is morally and technically outdated
• there were not enough people with the necessary expertise for a complex front

In fact, the business needed a partner who would take over the entire customer side of the product and help bring the system to working order.

The task was not just to «match the design», but:

• launch a new product
• replace the old version of the website
• accelerate market entry (time-to-market)
• implement complex user scenarios
• prepare a platform for SEO promotion

It was:

• outdated version of the website
• disparate logic
• lack of new functionality
• dependence on the limited resources of the team

Become:

• modern frontend on Next.js
• more than 30 pages and modules
• personal accounts for two types of users
• full integration with the new backend
• ready-made SEO structure

We were responsible for:

• the implementation of the entire frontend
• API layer development
• integration with the customer’s backend
• adapting the design into a working product

The architecture of the backend was determined by the customer’s team, we worked in conjunction with their PM and developers.

In fact, it was not a «website», but a full-fledged product.:

• more than 30 pages and modules
• several large sections
• personal accounts
• the admin part
• two main user scenarios: the applicant and the employer

The key difficulties were purely engineering:

• integration with someone else’s Ruby backend
• lack of complete API documentation
• a raw API that had to be tested «by eye»
• constant changes in requirements
• lack of detailed technical specifications on the front

In fact, we were working in the following mode::

«Here are the endpoints for you, figure it out for yourself.»

The project was carried out in close cooperation with the customer’s team:

• we received the design from the third team
• connected to the backend in parallel
• we tested the API during the development process
• We made regular edits along the way
• adapted the front to the changing logic

It was a classic engineering project with high uncertainty.

The project worked due to technical expertise and flexibility:

• We didn’t expect a perfect TK.
• we quickly figured out someone else’s API
• adapted to changes in requirements
• We took over the entire frontend part.
• We worked as a product team, not just performers

The project was successfully launched:

• a new version of the platform has been released in production
• The product is still in use today
• all key user scenarios are implemented
• the platform is ready for SEO promotion
• The client was satisfied and continued cooperation.
• The project is being supported

Instead of a partially completed project, the client received:

• a fully operational HR platform
• modern frontend
• integration with a custom backend
• willingness to grow and SEO
• a product that is actually used by a business

This is a typical level case.:

«We know how to connect to other people’s systems and bring complex products to launch.»