Should a recruitment agency in Japan build a custom job portal or use SaaS?
Use SaaS if your process is standard and your team can live within the tool's fields and screens. Commission job portal development services when foreign-worker eligibility, employer collaboration or data ownership sits at the centre of your business and the tools keep getting in the way.
Agencies placing foreign talent often reach that point quickly. They need to know, for every candidate, the current residence status, when it expires, the Japanese level, which skills tests have been passed and in which field, and whether documents are complete. Many general tools handle this through free-text notes, which cannot be filtered reliably. Staff end up keeping a parallel spreadsheet, and the spreadsheet becomes the real system.
A custom portal turns those facts into structured fields that drive search, alerts and matching. The trade-off is a build cost up front and responsibility for hosting and maintenance, instead of a monthly fee that grows with seats or listings.
- Choose SaaS: standard process, small team, need to start this month
- Choose custom: eligibility data drives placements, clients need their own dashboard
- Choose custom: you want candidate data in your own account and region
- Revisit yearly: compare total SaaS fees with build and hosting costs
Who uses the result of job portal development services, and what does each need?
Four groups, each with its own screens. Designing for all four from the start avoids a portal that works for staff but confuses candidates, or one clients never log into.
Candidates
Sign up on a phone, often from abroad, in a language they read well; build a profile; upload residence card, certificates and test results; apply; see where each application stands.
Employer clients
Post or request roles, review shortlisted profiles in Japanese, record interview feedback and see what is happening without phoning the agency.
Agency staff
Screen applicants, move them through the pipeline, track document expiry, manage interviews and record placements and follow-up.
Partner agencies abroad
Where you work with sending organisations or overseas partners, a restricted login to submit candidates and see their progress.
Direct employers hiring foreign staff without an agency need a smaller version: candidates, hiring managers and HR. The same eligibility fields still matter.
How do visa-status and JLPT filters work in a job portal?
Each candidate profile stores residence status, expiry date, Japanese level and skills test results as structured fields, and staff or employer clients filter on them the same way they filter on location or experience. The portal flags expiring documents automatically.
The Japanese-Language Proficiency Test has five levels, N1 to N5, with N1 the most difficult, and is held in Japan twice a year, in July and December, according to the JLPT's official site. Store the level and the date the result was issued, and let candidates upload the certificate. Some candidates hold other Japanese tests; the field list should reflect what your clients accept.
For Specified Skilled Worker candidates, the Immigration Services Agency explains that Specified Skilled Worker status generally requires a skills test for the field plus Japanese ability equivalent to JLPT N4 or the JFT-Basic test, with alternative routes for some applicants. A portal can record which field test was passed and when, so staff can match candidates to roles in that field. Whether a candidate is actually eligible is a decision for your licensed staff and the authorities, not the software.
- Residence status from a list your staff maintain
- Residence card expiry date with automatic reminders
- JLPT or JFT level with issue date and certificate upload
- Skills test field and pass date
- Current location: in Japan or abroad
- Availability date and preferred prefectures
What should candidate and employer dashboards show in job portal development services?
The candidate dashboard should answer “What do I need to do next?” and the employer dashboard “Who should I look at, and what is happening with them?” Anything more is secondary.
For candidates, that means profile completeness with the missing items listed, application statuses in plain words, interview dates, and any document requests from staff. Notifications by email, and optionally by LINE or a mobile app, bring them back when something changes. The interface must work on a low-cost phone on mobile data, because many candidates will never use a laptop.
For employer clients, the dashboard shows open roles, shortlisted candidates with the details the agency chooses to share, interview scheduling and a simple way to give feedback. Agencies usually control exactly which candidate fields a client can see; we build that as a permission setting per client, so private data such as full addresses stays with the agency.
How do matching and applicant tracking work in custom job portal development?
Matching narrows the candidate list for a role using hard rules first (status, level, field, location, availability) and softer scoring second (experience, preferences, past feedback). Applicant tracking then records every step from application to placement, so nothing depends on memory.
We usually start with transparent rules that your staff can read and adjust: “show candidates with N3 or above, a care skills test, available within two months, willing to work in Aichi”. Once there is enough history, AI-assisted ranking can suggest candidates your staff might miss, with the reason shown next to each suggestion. People make the final decision; the system saves them from scrolling.
The tracking pipeline is configured to your stages, not a generic template. A foreign-worker placement often includes steps such as document collection, employer interview, offer, application support and arrival, and your staff should see at a glance who is stuck where. Automation from US$600 can add reminders and draft messages at each stage.
- Stages defined by your process, editable by admins
- Hard filters before soft scoring, always explainable
- Activity history per candidate and per role
- Bulk actions for staff: move, message, request documents
- Exports for your spreadsheets and reports
Who holds the placement licence when an agency commissions job portal development services?
The agency does. Software does not carry a licence and does not take over legal duties; your company remains the one providing employment placement, dealing with clients and candidates, and meeting its obligations. The portal is a tool your licensed business uses.
There is a related rule worth checking with your adviser. The Ministry of Health, Labour and Welfare explains that since October 2022, under the revised Employment Security Act, businesses that provide recruitment information and collect jobseekers' personal information must notify the ministry, keep job information accurate, handle personal information properly, deal with complaints and submit an annual business report. Whether that applies to your portal alongside your existing licence is a question for your adviser, not for us.
What we do is build features that make those duties easier to meet: dates on every job posting, one-click closing of filled roles, a complaints contact form that logs each case, consent records and data export for reports. We do not give employment-law or immigration advice.
How should job portal development services handle candidate data under APPI?
Collect only what placement needs, protect it with access control and encryption, record consent, and set retention rules. The Act on the Protection of Personal Information places these duties on your business; the build provides the technical measures, and your adviser confirms the policy.
Two parts of APPI come up often in recruitment. Article 23 requires security control measures for personal data, which in practice means role-based access, encryption and logs. Article 28 requires prior consent, subject to exceptions, before providing personal data to a third party in a foreign country, which matters when you share candidate profiles with partner agencies abroad or employers' overseas offices. Your consent screens and privacy notice should cover those flows as your adviser directs.
On the technical side, we host in your own cloud account in the region you choose, keep uploaded documents in private storage, restrict fields by role and by client, log every view of a candidate record and allow bulk deletion when retention ends. We develop and test with dummy data; after launch, our maintenance access to live candidate data is limited to what you approve.
Why does a job portal in Japan need a bilingual interface?
Because the two sides of the market read different languages. Employer clients and many agency staff work in Japanese; candidates often read English, or their own language, far better than Japanese. A portal in only one language loses one side.
We build the interface with every label, button, email and error message stored as translatable text, so adding Vietnamese, Indonesian, Burmese or another language later is a translation task, not a rebuild. Job descriptions are harder: an employer may post in Japanese only. Options include a staff-written English summary, a translation field the agency fills, or machine translation clearly labelled as such for candidates' convenience.
Our team writes English and does not translate Japanese copy. You supply or approve Japanese and other language text, and a fluent reader should check each language before launch. Structurally, public job pages in each language get their own URLs with hreflang so each can be found by search.
Can job listings from a custom portal appear in Google's job search?
Yes, if job pages carry correct structured data and stay up to date. Google's job posting documentation lists Japan among the regions where the job search experience is available and requires properties such as title, description, date posted, hiring organisation and job location.
The same documentation recommends the Indexing API over sitemaps for job posting URLs, because it prompts Google to crawl new or removed jobs sooner. We add both: JobPosting markup generated from each listing's fields, and automatic Indexing API calls when a job opens or closes. Closed jobs must drop the markup or return a removed status, or Google may show stale listings.
Agencies that do not name the end employer publicly need to handle the hiring organisation field carefully; we follow whatever your policy is and check it against Google's guidelines. Nobody can guarantee jobs will appear or rank, but correct markup is the entry ticket.
How much do job portal development services cost?
With our team, a custom job portal starts at US$900 and a first release typically takes six to twelve weeks. A public recruitment agency website without logins starts at US$150. A candidate mobile app starts at US$600, and matching or screening automation starts at US$600.
The cost moves with user types, workflow depth and integrations. Candidates plus agency staff is the simplest shape. Adding employer client logins, partner agency logins, document expiry alerts, interview scheduling, messaging and reporting adds to the build. Integrations with your accounting or payroll tools depend on what those tools allow, and we read their documentation before quoting.
Compare against SaaS honestly: add up per-seat and per-listing fees over three years, plus the staff time spent working around missing fields, and set that against build, hosting and maintenance. Quotes from other developers vary widely, largely because of how much is in scope; ask for itemised quotes so you compare the same features. Ours are itemised in USD, with nothing billed before written approval.
How do job portal development services help companies hiring foreign staff directly?
By giving the company its own bilingual careers portal, so applicants reach HR without a middleman and hiring managers review them in one shared pipeline. The eligibility fields that matter to agencies matter just as much to an employer recruiting from abroad.
A direct employer's portal is usually simpler: no client dashboards and no partner logins, but clearer job pages, an application form that captures residence status and Japanese level, and a pipeline where HR and line managers leave comments on the same candidate instead of forwarding emails. Interview slots can be offered online, which matters when candidates are several time zones away.
Companies that also use agencies sometimes want both routes in one place. The portal can record the source of every applicant, whether a direct application, a referral or a named agency, so HR can see where good hires really come from. Where the company employs Specified Skilled Workers, the Immigration Services Agency's guidance describes support duties that may involve registered support organisations; the portal can hold task lists and dates for whoever provides that support, while the duties themselves stay with the responsible parties.
- Bilingual careers pages with job posting markup
- Application form with eligibility fields and uploads
- Shared pipeline for HR and hiring managers
- Source tracking: direct, referral or named agency
What should the first release of a custom job portal include?
The smallest set that replaces your spreadsheet: candidate sign-up and profiles with eligibility fields, job listings, applications, a staff pipeline and basic search. Launch that, use it for an intake cycle, then add dashboards and automation where staff feel the most friction.
Phasing matters because recruitment workflows look simpler on paper than they are. The first weeks of real use always reveal a stage you forgot, a field clients insist on, or a notification candidates ignore. Building everything at once means rebuilding some of it; building in phases means the second phase is designed from evidence.
Release one
Profiles with eligibility fields and uploads, job listings, applications, staff pipeline, search, bilingual interface, job posting markup.
Release two
Employer client dashboard, interview scheduling, document expiry alerts, email and LINE notifications.
Release three
Matching suggestions, partner agency logins, reporting, candidate mobile app if usage justifies it.
For a broader take on scoping a first version, see our guide to MVP development for startups.
Which technology stack suits job portal development services?
A modern web framework with server rendering for public job pages, a relational database for candidates and jobs, private object storage for documents, and a search index for fast filtering. That combination handles thousands of profiles comfortably and scales further when needed.
We typically build with React and Next.js or a similar framework, PostgreSQL for data, and managed cloud services for storage, email and background jobs, hosted in your account. Public job pages are rendered on the server so search engines see the content and structured data directly. Staff screens are built for speed with keyboard shortcuts and bulk actions, because agency staff live in them all day.
We avoid heavy proprietary platforms that lock your data in. Every table can be exported, the code is yours, and another developer can pick it up later with the documentation we hand over.
Want your own developers to extend it later? Our hire React developers in Japan page explains how we hand over React codebases.
How does an agency in Japan work with job portal developers in India?
Through a short weekly call during Japanese afternoons and a shared channel for questions in between. Our day starts at 12:30 pm JST, which usually fits after morning interviews and candidate calls.
We work in English. Most agencies placing foreign workers already have bilingual coordinators, and one of them becomes our main contact, bringing questions from staff and clients. Every two weeks you see working software on a staging link, with test candidates and test jobs, so feedback is about real screens rather than documents.
Quotes and invoices come from India in USD, paid by Wise, bank wire or PayPal, with nothing billed before written approval. The cloud account, domain, code repository and all data belong to your company from the first day.
Days 1–5
Workflow walkthrough with your staff, list of candidate fields and pipeline stages, user roles and what each can see.
Days 6–14
Clickable screens for candidate profile, job page and staff pipeline, then the first working build on staging with dummy data.
What are the red flags when hiring for job portal development services?
The costly failures come from ignoring workflow, data ownership and upkeep. A portal can look finished in a demo and still fail your staff in week two.
- A clone script with generic fields and no place for residence status or JLPT level
- Candidate data hosted in the developer's account, not yours
- No role-based permissions: every client sees every field
- Documents stored in public folders or sent as email attachments
- Closed jobs left online with live structured data
- No plan for backups, updates or who fixes bugs after launch
- Claims that the software makes you compliant with employment or immigration law
Ask any developer to show where each of these is handled in their plan. Clear answers are more valuable than a long feature list.
Worked example: job portal development for a hypothetical care-worker agency in Nagoya
Picture an agency in Nagoya placing caregivers and food-manufacturing workers with employers across Aichi and Gifu, working with sending partners in two countries. Staff track candidates in spreadsheets and send profiles to clients as PDF files by email.
A first release would give candidates a mobile-friendly sign-up in English and Japanese, profiles with residence status, expiry date, JLPT level and skills test fields, and document uploads. Staff would get a pipeline matching their stages, with filters and expiry alerts. Public job pages would carry job posting markup. Release two would add a client dashboard showing only the fields the agency approves, plus LINE notifications. Partner agencies abroad would get restricted logins in release three.
The first release would be quoted from US$900, with later releases scoped after real use. This is a hypothetical scoping illustration, not a client project.
Job portal development services checklist before launch
Run through this with your operations lead and one employer client before opening the portal to candidates.
- Eligibility fields required where your process needs them
- Expiry reminders tested with dates a few days ahead
- Client permissions checked: each sees only approved fields
- Consent screens and privacy notice reviewed by your adviser
- Uploads stored privately; direct links do not work without login
- Job posting markup validated and removed on closed jobs
- Interface checked by fluent readers in every language
- Backups running and a restore tested
- Cloud, domain and code accounts owned by your company