Moving a Recruitment Website Platform to a Modern Architecture

RecruiterWEB is a UK-based SaaS website platform for recruitment agencies. To keep the platform competitive and make development more efficient, we worked together to move it from a monolith to a new architecture with a separate frontend and backend, automated delivery and a modern technology stack. We also built a team able to deliver client websites on this architecture.

Executive Summary

A new architecture, with a separate frontend and backend, was designed for the websites RecruiterWEB builds for recruitment agencies. It was implemented in a base recruitment website that client sites are built from. An automated delivery pipeline carries changes from development to production. The existing functionality, including the admin, was carried over unchanged.

‍

The new base simplifies work on client projects: a client template site launches in about 40% less time, and bespoke sites and new features are built faster. The first production website was ready in about five months, and 150+ client websites have been built on it since.

WEBSITES ON THE NEW ARCHITECTURE
150+
FROM START TO FIRST PRODUCTION WEBSITE
~5 months
LESS TIME TO LAUNCH A CLIENT TEMPLATE SITE
~40%
SPECIALISTS IN THE TEAM
7

The Challenge

Delivering alongside a live business

The project ran next to a live business. The people working on it were shared with other projects and business tasks, and could give the project only part of their time. The work had to be planned around them while everyday business tasks kept going.

Reproducing a working platform without breaking what users know

Moving the frontend into a separate application changed the architecture of the system. The platform that people work with had to stay the same. The admin side holds a large body of functionality that users depend on, and it had to keep working as before. The new website also had to match the existing one feature for feature.

A base project that client sites inherit

The first website was meant to become the base for client projects. Sites built on it would inherit its quality, so a defect in the template could repeat across future projects.

‍

A delivery team new to the technology stack

The delivery team was experienced in the previous stack but not in the technologies of the new architecture. It had to be trained in them while the platform was being built.

‍

The Solution & Engineering Approach

Delivered Scope

Architecture and technology selection

The frontend and backend are separate applications. Most day-to-day work on client sites is frontend work, so frontend developers deliver it without going into the backend, and backend changes stay rare and are handled separately. The frontend runs on Next.js, with rendering set per page type for SEO and speed. Architecture decisions are recorded with their reasons.

‍

Recruitment website on the new architecture

A full recruitment website on the new architecture, matching the existing one feature for feature. The admin side works as before, so users kept their familiar workflows. The frontend and backend are developed and deployed independently.

‍

Team upskilling

Developers new to the stack were trained on a defined plan. They now deliver client projects on it independently.

‍

Delivery pipeline

A CI/CD pipeline runs across four environments, from development to production, with automated builds and containerized deployments.

‍

Technical Architecture

Technology stack

Next.js, React, TypeScript, React-Bootstrap, SCSS, Java, Spring, PostgreSQL.

‍

Delivery Methodology & Governance

Engagement model

A cross-functional project team drawn from existing projects. People joined only at the stages where they were needed.

‍

Team & roles

A project manager, an architect, a technical lead, two developers and a QA engineer, with a DevOps engineer for infrastructure setup.

‍

Agile delivery approach

Scrum adapted to the needs of the project: two-week sprints with the standard ceremonies and continuous improvement through retrospectives. Work is demonstrated at the end of each sprint and accepted stage by stage, against the agreed deliverables.

‍

Key Business Outcomes

150+ client sites built on the new base

The new architecture became the standard for RecruiterWEB: new projects are built on it, and 150+ client websites have been delivered so far.

‍

A team that delivers on a modern stack

Developers experienced in the previous stack now deliver client projects on the modern one. The stack is widely used on the market, which also widens the pool of developers we can bring into the team.

‍

Faster, cheaper launches and development

Launching a client template site now takes about 40% less time, and bespoke sites and new features are built faster too. The gain comes from two sources: a stack with a large ecosystem of ready-made components, and delivery processes with automated builds and releases.

‍

Team capacity focused on the frontend, where most of the work is

Frontend developers now deliver client work without going into the backend. Frontend tasks make up the bulk of everyday work, while backend changes are rare and handled separately. The team can therefore consist mostly of frontend developers.

‍

Have a similar challenge?

Tell us what you are trying to solve. We will come back with a clear view of the options, the effort involved and the result to expect.

‍

Contact Us

Contact Us

TESTIMONIAL

Client Testimonial

"Having worked in IT for 25 years and running my own technology company for the past 14 years I can say that the team at Genix Solutions is by far and away the best I have ever worked with."

Darren Revell,

RECRUITERWEB

Owner

Uploading...
fileuploaded.jpg
Upload failed. Max size for files is 10 MB.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.