Careers

Roles from employers a person has checked.

Verification is a person’s judgement about who is behind a posting — a fake employer here is not a spammer, it is a CV-harvesting attack. Applications are made inside PCI World with recorded consent, and that consent stays the applicant’s to withdraw.

Careers

Job board

/world/careers

The public board. Only verified employers appear on it, and a closed job leaves the list the moment it closes.

Enforced by the real server

Only verified employers appear
A closed job leaves this list the moment it closes
Applying always needs a Passport account

Senior Planning Engineer

Northwind Infrastructure · Manchester, UK · £65,000 – £78,000 Verified employer
Cost Control Lead

Northwind Infrastructure · Remote (UK) · £58,000 – £70,000 Verified employer
Project Controls Manager

Halden Energy · Aberdeen, UK · £82,000 – £95,000 Verified employer
Planner (Rail)

Meridian Delivery Partners · Birmingham, UK · £48,000 – £56,000 Verified employer

What this screen calls

Endpoint	Status
`GET /world/careers` (server-rendered page)	Built
`GET /world-sitemap.xml` (live jobs only)	Built

Careers

A job page

/world/careers/northwind/senior-planning-engineer

A crawlable job page. Structured data is a claim made to a search engine, so it is computed when the page is drawn rather than left behind by a job that has since closed.

Enforced by the real server

Carries JobPosting structured data only while it is open
Once closed: page stays readable, markup disappears, leaves the sitemap
No external apply link — ever

Careers / Northwind Infrastructure

Senior Planning Engineer

Northwind Infrastructure Verified employer

Manchester, UK · Full time · £65,000 – £78,000 · Closes 14 August

Own the integrated programme for a live rail package: baseline maintenance, critical path analysis, and the monthly forecast that the client actually reads.

What you’ll be asked when you apply

Describe a schedule recovery you personally owned.

Apply

Your application, your answers and your CV are sent to this employer and to nobody else.

Applying twice to one role is impossible by design.

What this screen calls

Endpoint	Status
`GET /world/careers/{employer}/{slug}` (server-rendered)	Built
`POST /api/world/careers/postings/{id}/apply`	Built

Careers

Employer portal

/world-app/ → Employer portal

The employer’s side. Note the second organisation: it can write postings all day and the publish control refuses, in words, with the reason.

Enforced by the real server

An unverified employer can draft everything and publish nothing
One employer can never see another’s applicants
Suspending an employer cuts its access mid-session, not at next login

Your organisations

Northwind Infrastructure state: verified · your role: owner

Halden Energy state: pending verification · your role: owner

Postings — Northwind Infrastructure

Role	State	Applicants
Senior Planning Engineer	Published	7
Cost Control Lead	Published	3
Contracts Engineer	Draft	—

Postings — Halden Energy Pending verification

Role	State	Action
Project Controls Manager	Draft

Applicants — Senior Planning Engineer

Applicant	Submitted	CV	State
A. Mensah	2 days ago	Download	Shortlisted
J. Whitfield	3 days ago	Download	Submitted
R. Okonkwo	4 days ago	Unavailable	Consent withdrawn

Every CV download is logged — including refused ones, because a run of refusals is what probing looks like.

What this screen calls

Endpoint	Status
`GET/POST /api/world/careers/employers`	Built
`GET/POST /api/world/careers/employers/{id}/postings`	Built
`POST /api/world/careers/postings/{id}/publish`	Built
`GET /api/world/careers/postings/{id}/applications`	Built
`GET /api/world/careers/applications/{id}/cv`	Built
`POST /api/world/careers/applications/{id}/decision`	Built

Careers

My applications

/world-app/ → My job applications

The applicant’s own view. The design decision worth seeing: withdrawing consent does not delete the record that consent existed, because “was there consent the day they read this?” has to stay answerable afterwards.

Enforced by the real server

Withdrawing consent stops the employer immediately
The consent record survives withdrawal
Withdrawal is not erasure — and says so

Senior Planning Engineer

Northwind Infrastructure · submitted 3 days ago · Shortlisted

CV attached: a-mensah-cv.pdf

Consent granted 3 days ago under policy v1 — active

Planner (Rail)

Meridian Delivery Partners · submitted 3 weeks ago · Not progressing

Consent granted 3 weeks ago under policy v1 — withdrawn 2 days ago. The record is kept.

What this screen calls

Endpoint	Status
`GET /api/world/careers/my/applications`	Built
`POST /api/world/careers/applications/{id}/withdraw`	Built
`POST /api/world/careers/applications/{id}/consent/withdraw`	Built

This page is a drawing, not the product. Nothing here is stored, sent or checked — the buttons show what the real screens say, not what a server decided. The rules in each amber register are enforced by the actual system; this drawing of them cannot enforce anything.