Hiring should start with the work, not the logo
In the Philippine market, where you worked and where you studied still open and close doors before anyone reads what you actually did. Vcansee removes the shortcut in both directions: candidates cannot see the employer, and employers see evidence before anything else.
Four places we enforce it
A promise in the interface is easy to break by accident. These are structural.
Enforced at the query layer
Seeker-facing database reads use a select list that omits name, slug, logo, website, description and address. The company name never leaves Postgres on those code paths, so there is no API response for it to leak from.
Masked in messaging
Before a reveal, employers appear as "Hiring Team – A BPO company in Metro Manila". Notification emails, in-app alerts and message threads all use the same masked identity.
Absent from structured data
Our JobPosting JSON-LD publishes the anonymised label as the hiring organisation, so the company name does not reach search engines either.
Every reveal is logged
When a company reveals itself we record who did it, when and what triggered it. Candidates see the date; our moderators see the full trail.
The journey, end to end
An employer posts a role
They describe the job — with AI help if they want it — and it goes live carrying only their industry, size band and region.
You apply on the evidence
You see the full role, the salary and the shift. You apply with a resume version you choose, and optionally a cover letter drafted in your voice.
They screen on signal
Your application arrives with a match score against the stated requirements and a short digest. They read your answers, your resume and your letter.
They reveal themselves
When they invite you to interview, their identity unlocks: name, logo, website, description and the full company profile. You are told immediately.
You decide with full information
Only now do you weigh the brand — with a role you already know you want and an employer who already wants to talk to you.