Files
jobboard/roles.yaml
T
WolfandClaude Opus 5.5 bc60324fab Score roles per search agent, and run pull into extract, embed and score
embed stores one vector per open role; score rates every open role for
every enabled agent from require and prefer gates, fit against the
agent's intent, recency and company affinity, keeping gated rows with a
reason. Schema v3 adds vectors and the cached intent vector. The page
gets an agent order, the score on each row, and an Agents tab. Two
starter agents in roles.yaml are imported once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 12:14:21 +02:00

34 lines
1.2 KiB
YAML

# The default config. See config.example.yaml for what each key means.
database: roledesk.db
plugin_paths:
- plugins
workers:
llm: 4
http: 8
cpu: 1
extract:
enabled: false
model: claude-haiku-4-5-20251001
sources: {}
embed:
model: sentence-transformers/all-MiniLM-L6-v2
# Starter search agents, imported once into an empty table. Edit them on the
# page afterwards; this list is not read again.
agents:
- name: Berlin backend
intent: >-
Senior backend engineer. Python and Go services, PostgreSQL, event-driven
systems, APIs and data pipelines on Kubernetes in the cloud. Wants
ownership of production systems in a product company.
gates:
- {field: place, values: [Berlin], mode: require}
- {field: remote, values: [hybrid, remote], mode: prefer, weight: 0.2}
- name: Remote EU stretch
intent: >-
Staff or lead engineer role, fully remote from Europe. Platform and
infrastructure work, distributed systems, developer tooling, technical
leadership across teams.
gates:
- {field: remote, values: [remote], mode: require}
- {field: country, values: [DE, NL, AT, CH], mode: prefer, weight: 0.2}