Built the hiring and seafarer career workspaces
Built hiring and seafarer career workspaces; the recorded
implementation snapshot contains 151 stored functions across 48
tables for vacancies, applications, certificates, rank progression
and sea time.
2025

Situation. The commercial argument for a maritime professional
network is hiring: companies need crew and officers, and seafarers
need berths. Both halves already existed on the platform in the
wrong shape — companies were in the directory, professionals had
profiles, and there was nothing connecting a vacancy to the person
qualified to fill it. Qualification is the hard part, because in
this industry it is certificates, ranks and documented sea time
rather than a job title.

Task. Vacancies, applications and verifiable seafarer credentials
had to be modelled properly rather than as free text on a profile.

Action. These counts describe the recorded implementation snapshot,
not the current repository or a current release declaration. Two
domains got built. The hiring side runs to 32 tables and 118
functions covering vacancies, applications, shortlisting and the
employer's view of its candidates. The career workspace carries 16
tables and 33 functions holding certificates, rank progression and
sea time, with document upload and a reviewer queue so a credential
is checked rather than claimed. Modelling progression as a graph
rather than a list is what makes the matching useful — a rank is
reachable from another rank given certain certificates and enough
recorded time at sea, and that structure is what lets a vacancy be
matched against a career rather than against a keyword. The snapshot
describes the career workspace as feature‑flagged and incompletely
released, and the hiring side as live; it does not establish the
present deployment state.

Result. A vacancy can be matched against documented qualifications
instead of a self‑described job title, which is the whole difference
between a job board and a hiring tool in this industry. Verification
is the bottleneck, deliberately — a reviewer queue does not scale
the way an automated check would, and an automated check would
certify people who should not be certified.

Categories:
1Backend Engineering	/categories/backend/	software.engineer.company	70
1Full‑Stack Development	/categories/full-stack/	software.engineer.company	70
1Databases	/categories/databases/	software.engineer.company	70
1PostgreSQL	/categories/postgresql/	software.engineer.company	70
1Data Governance	/categories/data-governance/	software.engineer.company	70
1Product & Requirements	/categories/product/	software.engineer.company	70

Services:
1Backend & API Development	/services/backend-development/	software.engineer.company	70
1Full‑Stack Product Development	/services/full-stack-development/	software.engineer.company	70
1Database Design & Modeling	/services/database-design/	software.engineer.company	70
1Product Strategy & Requirements	/services/product-strategy/	software.engineer.company	70

hThis page on the web	URL:https://software.engineer.company/portfolio/built-the-hiring-and-seafarer-career-workspaces/	software.engineer.company	70
