Files
jobboard/docs/open.md
T

5.4 KiB

Open

What is left after the phone rework of 2026-09-25, for whoever picks the repo up next, in the order it bites.

  • The checkout moved. CLAUDE.md, README.md, desk/README.md and the refresh commands assume ../boilerplate and ../news beside the checkout. Keep them beside it in the sandbox or change the paths. .venv holds absolute paths, so uv sync --all-extras again after the move.

  • The boilerplate moved on. Since roledesk's last refresh (77052a8, the schedules fix) it has 4573f6d (the kit: the layout patterns every app built for itself, as classes) and 1679e88 (deploy from a WSL checkout, the sandbox setup). Refresh deploy/ and pipeline/ with git archive, and see whether app/static/app.css should use the kit's classes instead of its own copies of the same rules.

  • Restart the server. A server started before the rework runs the old code; on start the database migrates to schema v4 (vote, summary, article text on roles).

  • The live database has two agents, "Berlin backend" and "Remote EU stretch", so Ranking edits the first and the Roles order menu lists both by name. Delete one with the CLI for a plain Best match.

  • Summarising is off until the switch under Runs (default summarise.enabled: false) is used, and needs a model backend, as extract does. The Summarise button on a read page works either way once a backend is configured.

  • Fit does not read seniority. With three prompts on the live data of 2026-09-29 an individual contributor's posting ranks beside a head's on the same subject. Switch extract on so seniority fills, then add a prefer gate on it, and vote.

  • Nine Teamtailor seed companies have no board, because their careers_url is the marketing site: Templafy, Queue-it, Telenor, Polestar, IQM, TeamViewer, Tractive, Starship, Factorial.

  • Votes do not train fit. A vote only moves the rank at read time. Feeding votes into the prompt vectors is worth doing once there are a few hundred.

  • 76 companies are read by hand, on the Watchlist with a careers link opened on 2026-09-29: 35 unread, 10 robots, 9 Teamtailor ones without a career host, 8 group, 7 blocked, 4 gone, 3 key. The remaining readers are planned in docs/plan-hosts-wave-2.md.

  • The hosts added on 2026-09-29 were read from this machine only. Every Workday tenant is behind Cloudflare; read one Workday and one SuccessFactors board from the deployed server before relying on them.

  • An unknown SmartRecruiters or Gem id answers an empty listing, not 404, so a mistyped slug reads as a complete board with no roles and would close a company's roles. set_board reads the board first, which catches a typo only when the person notices "0 roles".

  • Crawl-delay is not honoured. Booking.com's robots.txt asks for 5 seconds; the shared reader waits PAGE_DELAY, 0.5. A read of its board is two requests.

  • Eightfold returns 10 roles a page and MAX_PAGES is 100, so Infineon (1,289 roles) and Microsoft (about 2,300) would never be read complete and are not attached. The endpoint takes a location filter; a target has nowhere to state one.

  • A SuccessFactors site on a company's own domain is not discovered from its own pages, which link only the back end and the image CDN. It needs the rule Teamtailor has in discover.py: a page with the markers means the page's host is the board, checked by reading /search/. Until then such a board is set by hand.

  • HR Manager's portal disallows reading in robots.txt, its feed host has no robots.txt. The module checks the feed's host, so a board would be read. Seaborg, the one company on it, is not attached until the owner decides whether the feed counts as allowed.

  • Six new hosts' dates are not trusted (Eightfold, Jibe, Gem, Deel, HiBob, HR Manager; Pinpoint states none), so their backlog counts as posted when first seen. Check each date on a live board and add the host to TRUSTED_POSTED_HOSTS.

  • SmartRecruiters and Workable roles have no text. Their lists carry none and their modules have no detail, so 7,391 open roles (Bosch, Wise, Ubisoft, Delivery Hero) are ranked on the title alone. Both hosts have a per-posting endpoint; a detail in each module fills the text 200 roles per board per pull.

  • A posting fetched by hand feeds the reader only. "Fetch the posting" stores article_text, which summarise reads and embed and extract do not.

  • A list's teaser is not stored. Phenom's and Oracle's lists carry a short description, which is dropped so that it cannot replace the full text; until the role's page is read the role has no text at all.

  • A starred company's roles crowd the top of Best first. With the companies weight at 0.2 a favourite's roles gain about 0.13; after starring Databricks it held 33 of the top 60 rows. Lower the weight on the agent's card, or star fewer companies.

  • The owner's agent passes any role in Sweden and Germany. Its any group holds country DK, SE, DE, which is why SAP in Garching ranks. For Denmark, remote and Skåne only, the group is country DK, remote remote and place region:skane.

  • ★ means two things on the Roles tab. On a row it saves the role, in the company strip it marks the company a favourite.

  • Place suggestions take about 110 ms, most of it splitting 5,600 place lines into towns on every request. Caching the towns per distinct line would cut it.

  • company_key keeps ø, so "Orsted" and "Ørsted" are two companies. Folding it changes the primary key of companies.