A Husky’s Job – Recruitment & Workforce Management Platform

A Husky's Job case study — Built the frontend for recruitment and workforce management: pipeline, shifts and records

Client:

A Husky's Job GmbH

Date:

2022

Duration:

2 months
A Husky’s Job – Recruitment & Workforce Management Platform
I designed and built the frontend of the A Husky’s Job workforce management platform, the backoffice recruiters and admins live in all day. Short engagement, so the architecture had to be right the first time.
A Husky's Job candidate pipeline — Candidates moving through each hiring stageA Husky's Job shift planning — Weekly shift plan across clients and sites

About the client

A Husky’s Job builds hiring and workforce tools for companies that need structure around recruitment: pipelines, coordination, and the admin work that surrounds actually placing people.

Project Overview

A Husky’s Job needed one place to run recruitment and workforce admin instead of several. Candidate management, hiring pipelines, and the operational reporting around them.This is internal tooling, which changes what good means. Nobody is being persuaded by it. People open it at 9am and are still in it at 5pm, so clarity and predictability mattered more than anything else, and the layout had to stay consistent enough that muscle memory works.The frontend architecture came first: component structure, layout system, how data moves through a screen. That work is invisible when it’s done right and expensive when it isn’t.The engagement was short. The point was to leave behind a frontend the next developer could extend without unpicking it first.

The Challenge

Designing a scalable frontend architecture on a short timeline is mostly about which decisions you refuse to defer. Get the component boundaries and the data flow wrong early and every later feature pays for it.Being the outside team adds its own constraint. Scope had to be explicit and the handover had to stand on its own, because I wasn't going to be there when the next feature landed.

My Contribution

I led the frontend: architecture, component structure, layout system, and the UI direction the rest of the build followed.The heavier interactive pieces were tables and complex form controls, while Tailwind CSS handled the layout. Using established components for the data-dense parts was a deliberate trade. Building those from scratch would have eaten the timeline for no real gain.I also did the technical oversight, which in practice meant keeping the reusable patterns actually reusable instead of letting each new screen invent its own.

Technology Stack

  • Vue.js, Tailwind CSS, frontend-only architecture, backoffice systems, recruitment and workforce management platforms
Tags
Categories

Read More

Tell me about your project and get a price, timeline and project scope by email — no call needed.
Like what you see? Let’s work together

    How it works
    1. Tell me about your project below.
    2. I'll email you a few quick questions (about 3 minutes).
    3. You get a price, timeline and project scope by email — no call.
    A link helps me scope your project faster.

    Complete the short questionnaire to receive your indicative price, timeline and scope by email.

    This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.