Scrocle

Jobs Engine · 2026

Rank public listings against a profile

Laboratoryscrocle.cloud/demo/jobs-engineIndependent engineer

Jobs Engine interface

A hiring workflow begins with a profile and a large set of listings. Someone must score each one, discard irrelevant results, and record the shortlist, which is slow and error-prone when done by hand.

The constraint

This demo does not scrape LinkedIn, Indeed, or Upwork. It does not call a language model. It does not write to Google Sheets. Listings are a captured sample from Himalayas, Jobicy, and Remotive public feeds.

Built with

  • Python
  • FastAPI

How it works

Profile in. Score the fixture. Rank. Excel out. No apply calls.

  1. Title / skills / location
  2. Keyword rubric
  3. Ranked cards
  1. Himalayas / Jobicy / Remotive sample
  2. Excel download
Profile in. Score the fixture. Rank. Excel out. No apply calls.

The calls that shaped it

Each decision with the pressure that forced it and the price it keeps costing.

  1. Show the score parts

    Skills, title, and location are separate bars. If FastAPI is missing, you can see it. A single magic number would hide that.

  2. Fixture, not a live scrape

    Public APIs fail and mix in junk. A frozen set means the page always has rows. Production would refresh the same feeds on a schedule.

Open a preset. The list re-ranks, the score parts show why each row scored, and you can download the same rows as Excel. A production build would refresh the public feeds and write the sheet on a schedule. This is the matching and the shortlist without the marking exercise.

Where it stands

Demo. Live at scrocle.cloud/demo/jobs-engine. Profile in, ranked sheet out, on a captured sample of public listings.

What was handed over

  1. How to run the FastAPI demo locally
  2. That matching is keyword overlap, not a model
  3. What a production refresh and Google Sheet would add

Open the live demo

Next project Hidden Leaves Booking stays and tours