Key facts
| Sector | Recruitment / job platform |
|---|---|
| Type | Listings platform with public API |
| Market | United Kingdom |
| What ruxox delivered | Product design, listings engine, search & filtering, calculators, alerts, public API, deployment |
| Status | Live in production |
The brief
Generalist job boards treat a site carpenter and a band 6 nurse the same way they treat a marketing manager, and both audiences know it. Listings hide the salary, filters are built for office roles, and the surrounding content is generic. The brief for BOQQS was a platform built around two sectors specifically — construction and healthcare — where every listing shows what the job pays, and where the tools around the listings are the ones those workers actually use.
What we built
At the centre is a listings engine with, at the time of writing, over seven hundred live UK roles. The product decisions around it are what make it work for the audience:
| Feature | Why it matters for these sectors |
|---|---|
| Salary on every listing | Trades and NHS staff price their time; a listing without pay is noise |
| Multi-facet filtering | Sector, role, region, contract type and pay band combine without page reloads |
| Sector calculators | NHS take-home pay, contractor day-rate, and CIS tax for construction subcontractors |
| Salary guides | Benchmark pay by role so candidates know what to ask for |
| Daily job alerts | New matches delivered rather than searched for |
| Public Jobs API | Developers and partners can pull listings programmatically |
The calculators are not decoration. An NHS take-home calculator and a CIS tax calculator answer the question a candidate has immediately after seeing a salary — what does that mean for me? — and they bring in visitors who then discover the listings.
How it is built
The listings are served from an API that we also exposed publicly. That single decision shaped the architecture: the same endpoints the site uses to render search results are documented for external developers, which forced clean resource design, sensible pagination and rate limiting from the start rather than as a retrofit. It also gives the platform a distribution channel that a closed job board does not have.
Filtering runs against structured fields rather than free text, which is why combinations stay fast and why salary can be a first-class filter rather than something parsed out of a description. Alerts are a scheduled job over the same query model a user builds in the interface.
What this shows
BOQQS is a case for specialising. A niche board with the right filters, honest pay data and sector-specific calculators serves its audience better than a general board ever will, and the public API turns a website into a platform. We delivered the full build end to end — product design, front end, API, data model and deployment — and it runs in production today.
Where this fits
This is a custom software development engagement, and a build of this scope sits in our Platform Build tier — see straightforward pricing for what each tier includes and the fixed-price bands. Every engagement starts with a written scope that names the riskiest part of the build, delivered within 48 hours of your brief.