stupidoodle/swissdevjobs-cli

---

Every posting on swissdevjobs.ch — and its five sister boards covering Germany, the UK, the US & Canada, the Netherlands, and France — is required to publish a salary range. That makes them the rare job boards where you can filter by pay before you click. Since v0.5 the tool also searches jobs.ch and jobup.ch — Switzerland’s two biggest boards, every industry, ~50,000 postings. It also searches MyCareersFuture, Singapore’s government job portal, scoped to its ~9,000 Information Technology postings. One search, nine boards, JSON-first so an LLM agent can drive it.

It also remembers what you’ve already applied to, across every board, so the same job never shows up twice.

$ sdj list --tech Kubernetes --remote --min-salary 90000 --sort salary
57 shown · 57 match filters · 5521 in feed · 3 hidden (already applied)
----------------------------------------------------------------------------------------
6a60ec82…  devitjobs-us    p=2026-07-22  Senior Maximo Systems Developer/Integrator  TEKsystems c/o Allegis Gr  Ottawa   USD 208'000–270'400  remote  API, Ansible, Bash, ESB, GIS, IBM
6a6cc9bd…  devitjobs-us    p=2026-07-31  Senior Solutions Architect                  TEKsystems c/o Allegis Gr  Calgary  USD 187'200–228'800  remote  AI, API, Architect, Cloud, Docker

Contents

• Why · Please be reasonable · Install · Boards · Configure · Commands
• How applying works · Filtering
• MCP server · Under the hood · Cloudflare
• Claude Code skill · Development

---

Why

---

Please be reasonable

This talks to somebody else’s website, built by a small team who chose to make salary transparency mandatory. Keep your request volume human. Don’t strip the caching. Don’t fire off applications to postings you haven’t read — that wastes a real recruiter’s afternoon and poisons the well for everyone using the board honestly.

Read swissdevjobs.ch’s terms before you automate anything on top of this.

---

Install

In Claude Code — two commands

/plugin marketplace add Stupidoodle/swissdevjobs-cli
/plugin install swissdevjobs@swissdevjobs

That’s it. Claude Code prompts for your name, email, and CV path, then starts the MCP server with uvx — nothing to install first, and no shell profile is touched. Ask it “find me senior Python roles in Zurich over 140k” and go.

Requires uv on your PATH (brew install uv, or curl -LsSf https://astral.sh/uv/install.sh | sh).

As a CLI

uv tool install git+https://github.com/Stupidoodle/swissdevjobs-cli

Installs two equivalent binaries: sdj and swissdevjobs. Python 3.9+.

---

Boards

Three platforms, nine boards, one tool. The devitjobs family shares one backend across six countries — identical API, identical apply flow — the JobCloud platform (jobs.ch, jobup.ch) covers every industry in Switzerland, and MyCareersFuture is Singapore’s government job portal, scoped to IT and publishing salary:

All boards are searched by default. A selector is a board id (just that one) or a country code (every board there) — --board, with --source and --country as accepted aliases:

sdj list --board jobsch                   # just jobs.ch
sdj list --board de --board uk            # just Germany + UK, this once
sdj config --boards ch,de                 # persist: all CH boards + Germany
sdj config --boards swissdevjobs          # persist: one board only
sdj config --boards all                   # back to everything

sdj boards (and the MCP tool list_boards) prints all of this as data — no need to memorize which board does what:

$ sdj boards
9 boards — select with --board , persist with `sdj config --boards`
----------------------------------------------------------------------------------------------------
swissdevjobs     ch   SwissDevJobs        CHF  enabled  it · salary · unfilterable: workload
germantechjobs   de   GermanTechJobs      EUR  enabled  it · salary · unfilterable: workload
devitjobs-uk     uk   DevITjobs UK        GBP  enabled  it · salary · unfilterable: workload
devitjobs-us     us   DevITjobs US/CA     USD  enabled  it · salary · unfilterable: workload
devitjobs-nl     nl   DevITjobs NL        EUR  enabled  it · salary · unfilterable: workload
devitjobs-fr     fr   DevITjobs FR        EUR  enabled  it · salary · unfilterable: workload
jobsch           ch   jobs.ch             CHF  enabled  all-industries · no-salary · search-driven · no-native-apply · unfilterable: salary, remote, visa, level, tech, language · categories: it
jobup            ch   jobup.ch            CHF  enabled  all-industries · no-salary · search-driven · no-native-apply · unfilterable: salary, remote, visa, level, tech, language · categories: it
mycareersfuture  sg   MyCareersFuture     SGD  enabled  it · salary · search-driven · no-native-apply · unfilterable: visa, level, workload

jobs.ch and jobup.ch are search-driven. Their ~50k-job inventory can’t be mirrored (the API serves up to 200 rows per page and stops paging at 100 pages), so they answer your query server-side, newest first — pass free text for real coverage, and --category it to stay in tech:

$ sdj list "pflegefachfrau" --board jobsch --limit 2      # any industry, server-side
2 shown · 100 match filters · 100 in feed
----------------------------------------------------------------------------------------
40b2f214…  jobsch  p=2026-08-25  Dauernachtwache - Dipl. Pflegefachperson HF / FH  Stiftung entero      Niederlenz  —
b5367506…  jobsch  p=2026-08-25  Dipl. Pflegefachfrau HF/FH mit Fachverantwortung  Spital Männedorf AG  Männedorf   —

$ sdj list "python" --board ch --category it              # CH tech across all three boards

They publish no salary data (rendered honestly as —) and have no native apply — every posting routes to the company’s own ATS, so direct-apply refuses with the real apply URL instead of pretending.

MyCareersFuture is search-driven too. Singapore’s government job portal (Workforce Singapore) carries ~9,000 active Information Technology postings and its API caps limit at 100 rows per page, so queries pass server-side, newest first. Unlike jobs.ch it does publish salary — monthly SGD on the wire, annualized by the adapter — and skills, so --tech and --remote filter normally there. --visa, --level, and --workload are unavailable by design: no sponsorship-eligibility field exists on the wire (Singapore’s employer applies for a specific work pass after the fact, so there is no “will they sponsor” flag to read); the board’s own position levels (“Professional”, “Middle Management”, “Fresh/entry level”, …) have no honest mapping onto the tool’s Junior/Regular/Senior/Principal/CLevel enum, so they stay in job.raw rather than being guessed at; and no workload-percentage field exists at all. There is no native apply either — applying happens on the posting page, through the portal’s own flow, so direct-apply refuses and hands back that page’s URL.

Native postings on every devitjobs board publish a salary range. Syndicated listings (marked isPartner by the boards — the majority outside Switzerland) sometimes carry no range or a single-point figure; the tool renders those honestly and refuses to native-apply to them, handing you the real ATS URL instead — their pages have no native apply form, so a native submission would silently vanish. The applied-jobs ledger is shared — apply to a role on one board and the same company+role is hidden on all of them.

Want a board outside the family? Open a board request.

---

Configure

Reading jobs needs no configuration at all. Applying needs to know who you are.

sdj config --init     # writes ~/.config/swissdevjobs-cli/.env (chmod 600)
sdj config            # show what's resolved, and from where

Then edit the file:

SDJ_NAME="Your Name"
SDJ_EMAIL="[email protected]"
SDJ_CV="/absolute/path/to/cv.pdf"

# Optional: which boards to search (default: all)
# Board ids and/or country codes: jobsch, jobup, swissdevjobs,
# germantechjobs, devitjobs-*, ch, de, uk, us, nl, fr
# SDJ_BOARDS=ch,de

Where settings come from

.env files are read stdlib-only — no python-dotenv dependency. Anything already exported in your shell always wins, so nothing on disk can silently shadow it.

flowchart TD
    A["1 · Command-line flag--name / --email / --cv"]
    B["2 · Real environmentSDJ_NAME=… sdj …"]
    C["3 · $SDJ_ENV_FILE"]
    D["4 · ./.envwalking up to /"]
    E["5 · ~/.config/swissdevjobs-cli/.env"]
    F["direct-apply refusesrun: sdj config --init"]

    A -->|"not set"| B
    B -->|"not set"| C
    C -->|"not set"| D
    D -->|"not set"| E
    E -->|"still not set"| F

    classDef win fill:#c7f0d8,stroke:#1a7f45,color:#0b3d22
    classDef mid fill:#dbe7ff,stroke:#2a5db0,color:#12233f
    classDef low fill:#f0f0f4,stroke:#8a8a99,color:#2a2a33
    classDef bad fill:#ffd6d6,stroke:#c0392b,color:#4a1210

    class A win
    class B mid
    class C,D,E low
    class F bad

Highest priority at the top. A project-local .env beats the global one, which is handy if you keep a separate identity per job search.

---

Commands

flowchart TD
    START(["sdj"]) --> DISCOVER["🔍 Discover"]
    START --> ACT["✉️ Act"]
    START --> TRACK["📊 Track"]

    DISCOVER --> L["listsearch and filter the feed"]
    DISCOVER --> S["showfull posting text"]
    DISCOVER --> T["techmost-wanted tech tags"]
    DISCOVER --> O["openposting in your browser"]

    ACT --> A["applyhow do I apply to this one?"]
    ACT --> DA["direct-applysubmit through the site's form"]
    ACT --> AU["authclear a Cloudflare challenge"]

    TRACK --> AP["applicationseverything you have sent"]
    TRACK --> ST["statscache and application counts"]
    TRACK --> CF["configresolved settings and paths"]

    classDef root fill:#8A63D2,stroke:#5b3fa0,color:#ffffff
    classDef group fill:#dbe7ff,stroke:#2a5db0,color:#12233f
    classDef leaf fill:#f5f6fa,stroke:#9aa0b5,color:#22262f

    class START root
    class DISCOVER,ACT,TRACK group
    class L,S,T,O,A,DA,AU,AP,ST,CF leaf

Every command takes --json.

---

How applying works

Three postings on the same board can need three completely different actions. sdj apply tells you which, and direct-apply refuses the cases it knows would vanish.

flowchart TD
    START(["sdj apply JOB_ID"]) --> Q1{"redirectJobUrl points attalent.com or jometer?"}

    Q1 -->|yes| AGG["🚫 aggregator_postingexit code 2"]
    Q1 -->|no| Q2{"candidateContactWay?"}

    Q2 -->|"Email, withan address"| DIRECT["✅ directthe site forwards it"]
    Q2 -->|"CompanyWebsite,no address"| CW["🚫 company_website_postingexit code 2"]

    AGG --> BROWSER["🌐 Go apply on the ATSRecruitee · Workday · GreenhouseLever · Personio · SmartRecruiters"]
    CW --> BROWSER

    DIRECT --> POST["POST /api/jobApplymultipart: name, email,motivation, CV PDF"]
    POST --> OK{"HTTP 200?"}
    OK -->|yes| MARK["💾 recorded in SQLitehidden from future list"]
    OK -->|no| ERR["❌ raised with the response body"]

    BROWSER -.->|"after you submit"| COMPLETE["sdj apply JOB_ID --complete browser"]
    COMPLETE --> MARK

    classDef start fill:#8A63D2,stroke:#5b3fa0,color:#ffffff
    classDef good fill:#c7f0d8,stroke:#1a7f45,color:#0b3d22
    classDef bad fill:#ffd6d6,stroke:#c0392b,color:#4a1210
    classDef work fill:#dbe7ff,stroke:#2a5db0,color:#12233f
    classDef store fill:#ffe9b8,stroke:#b07d1a,color:#4a3308

    class START start
    class DIRECT,OK good
    class AGG,CW,ERR bad
    class POST,BROWSER,COMPLETE work
    class MARK store

Why the refusals exist

POST /api/jobApply returns HTTP 200 even when nobody receives your application. That happens in two cases:

1. Aggregator syndication. The listing was pulled in from talent.com or jometer. swissdevjobs.ch has no forwarding address for it.
2. candidateContactWay == "CompanyWebsite". The site is only linking out to the company’s own ATS. emailAddressForApplications is null, so there is nothing to forward to.

A third case can’t even pretend: jobs.ch and jobup.ch have no native apply endpoint at all — every posting routes to the company’s own application flow, so direct-apply there always answers no_native_apply with the ATS URL.

In every case the CLI exits 2 and hands you the real apply URL rather than letting you believe you applied. --force overrides the first two if you disagree.

$ sdj direct-apply some-workday-job --json
{
  "error": "company_website_posting",
  "next_action": "use_chrome_mcp",
  "apply_url": "https://acme.wd3.myworkdayjobs.com/…",
  "message": "USE CHROME MCP: visit … and drive the ATS form. …"
}

Exit codes

---

Filtering

Every filter behaves the same on every board — or tells you it can’t. jobs.ch/jobup.ch publish no salary, workplace, visa, or experience-level data (their own site can’t filter on those either), so filtering on one of them excludes those boards visibly: the JSON envelope carries boards_excluded and a note, the table prints the note on stderr — never a silent empty result. --tech still works there: the terms are matched server-side as full-text query (multi-term queries AND together), and --contract/--workload filter server-side through the platform’s own taxonomy. sdj boards shows each board’s unavailable dimensions and contract aliases as data.

---

MCP server

In Claude Code, the plugin wires this up for you. For any other MCP client, point it at swissdevjobs-mcp:

// Claude Code: .mcp.json  ·  Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "swissdevjobs": {
      "command": "swissdevjobs-mcp",
      "env": {
        "SDJ_NAME": "Your Name",
        "SDJ_EMAIL": "[email protected]",
        "SDJ_CV": "/absolute/path/to/cv.pdf"
      }
    }
  }
}

No prior install needed if you have uv — swap the command for uvx and let it fetch:

{
  "command": "uvx",
  "args": ["--from", "git+https://github.com/Stupidoodle/swissdevjobs-cli", "swissdevjobs-mcp"]
}

Then just ask: “find me senior Python roles in Zurich over 140k” — or “remote roles in Germany or the UK paying over 80k, show me the top five.”

Tools

The read-only tools carry readOnlyHint, so a client can run them without interrupting you. search_jobs returns compact rows on purpose — full descriptions come from get_job, so a broad search doesn’t burn context.

The confirmation gate

An application cannot be unsent, so apply_to_job refuses to submit until it is called a second time with confirm: true. The first call returns exactly what would go out:

{
  "error": "confirmation_required",
  "would_submit": {
    "role": "Senior ML Engineer",
    "company": "Acme AG",
    "salary": "CHF 140'000–180'000",
    "applicant": { "name": "…", "email": "…" },
    "cv_path": "/…/cv.pdf",
    "motivation_preview": "Dear hiring team, …",
    "motivation_chars": 1180
  }
}

The assistant shows you that, you say yes, and only then does anything leave your machine. Duplicates and undeliverable postings are caught before the gate, so a repeat never turns into a second submission.

sequenceDiagram
    autonumber
    participant U as you
    participant M as assistant
    participant S as MCP server
    participant SDJ as swissdevjobs.ch

    U->>M: "apply to the Acme role"
    M->>S: apply_to_job(job_id, motivation, cv_path)
    S->>S: already applied? deliverable? CV exists?
    S-->>M: confirmation_required + would_submit
    M-->>U: role, salary, letter preview — send it?
    U->>M: yes
    M->>S: apply_to_job(…, confirm: true)
    S->>SDJ: POST /api/jobApply
    SDJ-->>S: 200
    S->>S: record it locally
    S-->>M: submitted
    M-->>U: applied, and hidden from future searches

---

Under the hood

flowchart TB
    subgraph EP["entrypoints"]
        CLI["cli.pyargparse commands"]
        MCP["mcp.pyJSON-RPC over stdio"]
    end
    subgraph SL["service_layer"]
        SEARCH["search"]
        APPLY["apply"]
        TRACK["tracking"]
    end
    subgraph AD["adapters"]
        REG["boards/registry9 boards by source"]
        DEVIT["boards/worldwide/devitjobsclient + ACL"]
        JC["boards/switzerland/jobcloudclient + ACL"]
        MCF["boards/singapore/mycareersfutureclient + ACL"]
        HTTP["http/clienturllib, cookies, CF detection"]
        PERS["persistencemappers, repos, SQLite UoW"]
    end
    subgraph DOM["domain"]
        MODEL["model: Job, Board,Salary, Application"]
        PORTS["ports: BoardPort,repositories, UoW"]
    end

    CLI --> SEARCH
    MCP --> SEARCH
    CLI --> APPLY
    MCP --> APPLY
    SEARCH --> PORTS
    APPLY --> PORTS
    TRACK --> PORTS
    DEVIT -.implements.-> PORTS
    JC -.implements.-> PORTS
    MCF -.implements.-> PORTS
    PERS -.implements.-> PORTS
    DEVIT --> HTTP
    JC --> HTTP
    MCF --> HTTP
    DEVIT --> MODEL
    JC --> MODEL
    MCF --> MODEL
    PERS --> SQL[("~/.cache/…/swissdevjobs.db")]
    HTTP --> NET(["9 boards, 8 countries"])

    classDef mod fill:#dbe7ff,stroke:#2a5db0,color:#12233f
    classDef ext fill:#ffe9b8,stroke:#b07d1a,color:#4a3308
    classDef store fill:#c7f0d8,stroke:#1a7f45,color:#0b3d22

    class CLI,MCP,SEARCH,APPLY,TRACK,REG,DEVIT,JC,MCF,HTTP,PERS,MODEL,PORTS mod
    class NET ext
    class SQL store

The layering is cosmic-python style — domain at the center, adapters around it, entrypoints on the edge — and it is enforced, not aspirational: import-linter contracts plus an ast-based architecture test fail the build on any inward-pointing violation. The domain layer imports nothing but the stdlib.

Request path

sequenceDiagram
    autonumber
    participant U as you
    participant CLI as sdj
    participant DB as SQLite
    participant CF as Cloudflare
    participant API as the board

    U->>CLI: sdj list --tech Python
    CLI->>DB: cached jobs younger than 10 min?
    alt cache is fresh
        DB-->>CLI: rows
        CLI-->>U: filtered table
    else stale or --refresh
        CLI->>CF: GET /api/jobsLight
        alt normal
            CF->>API: forward
            API-->>CF: JSON
            CF-->>CLI: JSON
            CLI->>DB: upsert + timestamp
            CLI-->>U: filtered table
        else challenge
            CF-->>CLI: "Just a moment…" / cf-mitigated
            CLI-->>U: opens browser, waits on stdin
            U->>CLI: pastes cf_clearance
            CLI->>CLI: store in cookie jar, retry once
        end
    end

Reverse-engineered API surface

No auth, no API key on the read endpoints. The same surface exists on every board of the family. Responses cached in SQLite per board — 10 min for the list, 1 h for detail.

The JobCloud platform (jobs.ch, jobup.ch) exposes a different, equally open surface — shared by both boards, each with its own category taxonomy:

The two halves live on different hosts: JobCloud retired /api/v1/public/search on 2026-08-28 (it answers 410 Gone on both boards) and moved search to the host its own frontend calls. The detail endpoint beside it still serves.

Search-driven boards always ask the server; their SQLite rows exist so show and apply can resolve what a past search surfaced.

The database

erDiagram
    JOBS {
        text _id PK "MongoDB ObjectId"
        text source "which board (unique with job_url)"
        text job_url "slug"
        text company
        text name "role title"
        int  annual_salary_from
        int  annual_salary_to
        text candidate_contact_way "Email | CompanyWebsite"
        text email_address "null when external"
        text redirect_url "the ATS link"
        text light_json "full normalized feed row"
        text detail_json "full detail payload"
        text light_fetched_at
        text detail_fetched_at
    }
    APPLICATIONS {
        int  id PK
        text job_id FK "unique — this is the dedup key"
        text company
        text role
        text method "direct | email | browser | linkedin"
        text status "submitted"
        text applied_at
        text notes
    }
    JOBS ||--o| APPLICATIONS : "applied to"

Deduplication runs on job_id first, then falls back to (company, role) so an application you made through LinkedIn — or on a different board — still suppresses the same role everywhere. Cache freshness and slug uniqueness are per board (UNIQUE(source, job_url)).

---

Cloudflare

The six devitjobs boards sit behind Cloudflare (jobs.ch/jobup.ch run AWS WAF instead, which has not challenged API traffic so far). Ordinary use sails through; bursts and datacenter IPs can trip a managed challenge.

There is no automated solver here, by design. A headless client can’t run the JS challenge, and shipping something that tried would be both fragile and rude. Instead the CLI hands the problem to a real human in a real browser:

1. The command blocks and prints the URL.
2. Your default browser opens it.
3. You clear the challenge, then copy cf_clearance from DevTools → Application → Cookies (on the challenged board’s domain).
4. Paste it back. It’s stored in a Netscape cookie jar at ~/.config/swissdevjobs-cli/cookies.txt and the original request retries.

Run sdj auth up front before scripting a batch of calls.

---

Claude Code skill

The plugin already bundles a skill that teaches the whole search → shortlist → apply loop, including the confirmation handshake. Install that and you’re done.

skill/SKILL.md is the standalone version, for driving the CLI without the plugin:

mkdir -p ~/.claude/skills/swissdevjobs
cp skill/SKILL.md ~/.claude/skills/swissdevjobs/

Either way the rules are the same: stop before every irreversible submit and ask, never type national ID or bank details into a form, hand CAPTCHAs back to you.

---

Layout

src/swissdevjobs_cli/
  bootstrap.py       Composition root — the only place layers get wired
  domain/
    model/           One dataclass per file: Job, JobDetail, Board, Salary, …
    ports/           One Protocol per file: BoardPort, repositories, UnitOfWork
  adapters/
    http/            urllib transport, cookie jar, Cloudflare detection
    boards/
      registry.py    Every board, keyed by source; selectors resolve country or board id
      worldwide/devitjobs/   Client + anti-corruption layer for the 6-board family
      switzerland/jobcloud/  Client + ACL for jobs.ch + jobup.ch (search-driven)
      singapore/mycareersfuture/  Client + ACL for MyCareersFuture (search-driven)
    persistence/     Schema, imperative mappers, repositories, SQLite UnitOfWork
    envfile.py       Stdlib .env loading with shell-wins precedence
  service_layer/     Use cases: search, apply, tracking, config
  dto/               The frozen entrypoint-facing shapes (plain dataclasses)
  entrypoints/       cli.py (argparse) and mcp.py (JSON-RPC 2.0 over stdio)
skill/SKILL.md       Standalone Claude Code skill
plugin/              Claude Code plugin: manifest, .mcp.json, bundled skill
.claude-plugin/      Marketplace manifest, so the repo installs itself
tests/               230 offline tests mirroring src — fakes per port, no mocks,
                     ast architecture checks, 90% coverage gate; opt-in live lane

---

Development

make install    # uv sync
make check      # ruff + ty + import-linter + 250 tests with a 90% coverage gate
make test-live  # optional: read-only smoke against all eight real boards

CI runs the same gate on Python 3.9 and 3.14, and starts the MCP server to verify it still completes a handshake. Architecture rules and contributor ground rules live in CLAUDE.md and CONTRIBUTING.md.

---

License

MIT — see LICENSE. Not affiliated with, endorsed by, or connected to swissdevjobs.ch.