Hiring, kept in order.

For an energy company, we built a hosted hiring app: job posts, applications, stage tracking and candidate email in one place, with every decision logged.

skarowApplicant tracking system[DEMO COMPANY] / JobsAdd candidate[INITIALS]

[REQ-0000] · [TEAM] · [EMPLOYMENT TYPE]

[JOB TITLE]

Hiring manager [FIRST LAST]

Applied

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

Screen

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

Interview

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

Offer

[CANDIDATE NAME]

[CURRENT ROLE] · [SOURCE]

Applied [YYYY-MM-DD] · [INITIALS]

Demo data: one job's pipeline with Applied, Screen, Interview and Offer columns of placeholder candidates.

The problem

Hiring by inbox and spreadsheet loses candidates and leaves no record of who decided what.

What we built

A hosted hiring app with job posts, applications, stage tracking and candidate email, with every decision logged.

One board per job

Five stages by default, renamed to match how the team hires. Move a candidate and the change is logged with who did it and when.

  1. Applied01
  2. Screen02
  3. Interview03
  4. Offer04
  5. Hired05

Job posts

Written once, a post goes on the careers page and a shareable link, and every application lands on the job’s board.

[JOB TITLE]

[TEAM] · [EMPLOYMENT TYPE] · [REQ-0000]

[ROLE SUMMARY. Two or three plain sentences about the work and the team.]

Apply
Demo job post with placeholder fields

Candidate email

Templates for invites, updates and rejections, sent from the hiring team’s own address. Every message is kept on the candidate’s record.

What we delivered

Data and hosting

Candidate data is personal data. We treat it that way.

Hosting
Hosted and run by Skarow, in-region. [TBC]
Protection
Encrypted in transit and at rest. Access by role, per company. [TBC]
Candidate data
Export any time. Candidates deleted on request or after [N] months. [TBC]
Paperwork
Data processing agreement and a security summary. [TBC]

Status

  • Stage

    Pilot[TBC]

    Built for an energy company.

  • Hosting

    In-region

    Hosted and run by Skarow; candidate data stays in-region. [TBC]

  • Delivered as

    Hosted web app

    Job posts, pipeline, candidate email and a decision log.

Start a project

Running a process on inboxes and spreadsheets? Tell us what it is and who does it today.

or [hello@skarow.com]