Recruitment Careers Portal & Job Board

We build a proper Frappe application (its own module, installed on your bench alongside ERPNext) that turns your ERPNext instance into the system of record behind a professional careers website. The public side is a set of branded Frappe web pages and portal templates — a careers landing page, filterable job listings, and individual job detail pages — rendered server-side so they are fully crawlable and carry per-role JobPosting schema.org structured data, clean canonical URLs, meta titles/descriptions, and Open Graph tags. Each public listing is driven directly by your Job Opening records, so publishing or closing a role in ERPNext instantly updates the site; no second CMS to maintain.

On the application side, the one-click apply form posts through a whitelisted Frappe method (@frappe.whitelist(allow_guest=True)) that validates input, handles the resume file upload into the Frappe File store attached to the record, and creates a Job Applicant linked to the correct Job Opening — the exact document your recruiters already work from. We wire the workflow with hooks.py doc events and, where needed, server scripts and scheduler events: acknowledgement emails to the candidate on submit, notifications to the hiring team, and optional status-change emails as recruiters move the applicant through your recruitment stages. Candidates get a lightweight status-tracking view (via a secure token or portal login) so they can see where their application stands without contacting HR. Everything respects Frappe's permission model — public guest access is scoped to exactly the read/create operations needed, and everything else stays behind your existing role profiles.

Because this is build-to-order, we start from your brand, your role taxonomy, and your existing ERPNext configuration rather than shipping a rigid template. After a short scoping call we confirm the exact scope in writing, then design, build, and test on a staging copy of your site. Typical delivery is 2 to 4 weeks from confirmed scope, depending on branding depth and how many workflow/notification rules you need. We install on your Frappe/ERPNext v15 or v16 bench, run UAT with you on staging, and only then go live — with a rollback plan, a git repository handover, and a post-go-live support window so you are never left holding unfamiliar code.