Selected work / Magnum

Magnum HR Agent

A production HR agent built for real recruiters, real vacancies, and the operational constraints of a large retail network.

WhatsApp chat between the Magnum HR agent and a candidate

Client

Magnum

Domain

HR · Retail

Channel

WhatsApp

Magnum

Conversational agent, admin panel, knowledge ingestion, eligibility logic, age logic, notification flows.

The work

The system helps recruiters screen candidates, answer internal questions, and route people to the right vacancy or branch. It connects to the workflows the HR team already uses.

What mattered

A pleasant chat flow was the easy part. The real work was eligibility, branch fit, multilingual behavior, and keeping the agent useful when the operating rules changed.

What shipped

We delivered the conversational layer, admin tooling, knowledge ingestion, notification flows, and the business logic needed to make the agent useful inside recruitment operations.

Case study

Magnum HR Agent

AI for mass hiring across a retail network with hundreds of stores. The agent picks up the candidate the moment they reply on HeadHunter and walks them through a short interview on WhatsApp. The real work is not the chat. It is matching the person to the closest store, dealing with addresses written in any form, and keeping all of it inside an HR process the team already runs.

Problem

Too many candidates, not enough recruiters.

HeadHunter brings in a steady flow of applicants. The HR team cannot reply to all of them in time, so part of the pipeline drops out before anyone even reads it. Candidates wait, get an offer somewhere else, and the role stays open. On top of that, every candidate has to be sent to a specific store. Doing this by hand for a network this size is slow and accidental — the right person ends up assigned to a store on the other side of the city.

Solution

The first hour of recruiting, automated end to end.

Applications land in Skills, the internal HR system. From there the agent takes over: it messages the candidate on WhatsApp through Infobip, runs a short intake, and proposes the nearest store with an open role. Recruiters only see candidates who are already triaged. The whole flow is built around the recruiter, not around the model. HR keeps a panel where they can edit vacancies, salaries and store data without engineering.

Technical work

A geocoder we had to build because the address field is anything but an address.

People write where they live in whatever form feels natural: a district name, a village, a microrayon, half an address, sometimes slang. A plain string search does not work. So we built a small geocoding layer on top of Yandex Maps that turns any of that into coordinates and matches the candidate against the nearest store. We started on 2GIS and moved away — the API was expensive once we hit real volume. Store coordinates are cached locally so the same point is not re-geocoded twice. The WhatsApp side runs through Infobip with webhook-driven dialog state on our backend.

Hiring at the scale where every reply has to be near-instant?

We help retail and operations teams put the first hour of recruiting on rails: an agent in the chat, an admin panel for HR, and the routing logic that puts each candidate in front of the right role.

Brief (optional)