Full job descriptionHireful are looking for a Senior Software Engineer to take our new platform, ClearHR from scoping to a working product: backend, frontend, and the architecture decisions in between. You’ll work directly with our CTO, on the same stack as our already successful & fully established ATS platform.
Engagement: Freelance contractor. You invoice us monthly + VAT. We are roughly looking at a monthly budget of 5,000 + VAT.
Location: Fully remote. Spain strongly preferred, given our CTO and dev team are based there (Jaen), but we’ll consider any European time zone within + 0 to 2 hours. Or the UK of course!
Commitment & term: Full time, with an initial engagement of 3 months. We have an expectation this runs to 6 months and potentially beyond though.
Cadence: One hour a week. With the CTO, covering architecture, technology and security.
First step: Phase 0 alignment, before any feature work starts.
What is ClearHR?
hireful are developing a HR case management platform designed for HR teams and managers to handle sensitive employee matters in a structured, policy-led and auditable way. We already have a detailed product specification and a working prototype that can be reviewed, challenged and rebuilt, rather than starting from scratch. For the first release, "done" means taking that existing concept through to a fully production-ready product: core workflows complete, secure multi-tenant architecture, appropriate permissions and audit trails, tested data handling, production infrastructure, monitoring, documentation, and enough quality assurance that it’s ready to onboard and support real customers safely.
The stack
Deliberately the same stack as our hireful ATS platform.
- NestJS + TypeScript
- Vue.js
- Prisma
- GraphQL - preferred
- PostgreSQL
GraphQL is our preference rather than a hard requirement. If you’d argue for something else on this product, we’d rather hear the argument in the interview than discover it six months in.
How the work is governed
Two stages. The first exists so that neither side discovers a mismatch three months into the build.
Phase 0: first 2-3 weeks — agree how it gets built
Before feature work starts, you deliver:
- A proposed architecture, with the trade-offs written down
- The data model
- The security model: authentication, authorisation, tenant isolation, secret handling, data retention
- CI running, with tests
- One vertical slice working end to end, front to back
Gate: the CTO signs this off before the build continues.
Build: ongoing — ship, review, document.
- One hour a week with the CTO on architecture, technology choices and security
- Decisions are recorded, so we don’t relitigate them from memory later
- Tests ship with the code, not after it
- Security review before anything touching auth, data access or secrets goes live
You own the delivery. The weekly hour is a review, not a status meeting.
What you need
- NestJS + Typescript expertise in production. Modules, dependency injection, testing.
- Vue.js (Vue 3) with the Composition API. Component design and state management you can justify.
- GraphQL schema design. Including an opinion on when not to reach for it.
- Prisma and relational data modelling. Migrations, indexes, and a sense of what a query actually costs.
- Security as a working habit. Authentication and authorisation, tenant isolation, the OWASP Top 10, secret handling, validation at the trust boundary. We’ll go into this in the interview, and again every week.
- Architecture judgement. You can defend a decision and change it when the evidence says so.
- AI-assisted development with Claude Code. We use it daily and would expect you to. What matters isn’t that you can prompt it - it’s that you read what it produces, test it, and never ship code you haven’t understood.
If you’ve done this with an equivalent agentic CLI, tell us which and how.
How to apply & process
Apply now with your CV &/or LinkedIn profile, GitHub profile or any other means of getting touch.