Watch · About a minute
AIDA Portals, in about a minute each
For job seekers
For recruiters
Captioned, no sound needed.
AIDA Portal
Artificial Intelligence Data Analysis, delivered through a secure portal. An AIDA Portal takes what a client gives it, runs it through AIDA's analysis, has a person review the results, and publishes them to a portal the client signs into. Two AIDA Portals are running today, on one shared platform.
Two portals, one platform
Job Seeker Portal
Live, in pilotFor job seekers. Instead of thousands of search results, a short, honest list of real, currently open jobs, each scored against the client's background and reviewed by a person before the client sees it.
- A keyword matrix built from the client's background, in seven weighted layers: title, skill, tool, certification, industry, seniority and location
- Live postings collected every day from company career pages, Canadian Job Data and employer hiring-system feeds, for Canada and (by choice) the US
- Every posting scored against the matrix by one database function, with whole-word matching
- The Top 100 reviewed by a person (Data Queen): Best Match, Worth a Look or Removed, each with a written reason
- Ghost-job and employer checks: stale reposts and employers with a poor track record are flagged
- Scheduled rescans, daily to monthly; after the first review, only new postings need a fresh look
- Deliverables: Jobs Report, Career Bio, Search Strategy, resumes (Word, PDF and ATS text), cover letters, application kits for one specific job, interview playbooks
- In the portal: picks with their reasons, Request a Scan, Not Interested, resumes and kits
Recruiter Portal
Being configuredFor recruiters ("Know Your Candidate"). The job-seeker side turned around: one job, many candidates, every candidate scored against the job and explained.
- One job description and a stack of candidate resumes
- Every resume normalized into the same format first, so candidates are compared like for like
- The same scoring engine as the job-seeker side; the keyword matrix drafted for the job is approved by a person before it scores real candidates
- A human-reviewed deep pass on the strongest candidates
- Every candidate sorted Best Match, Worth a Look or Weak Fit, with the reason why; explanations never invent missing detail
- Candidates never get logins and can be reused across postings
- Deliverables: candidate profiles and a candidate analysis report
- Credits are used per deep-reviewed candidate
How an AIDA Portal works
Both portals run the same six steps. Only the intake and the deliverables change.
Data collectors: dozens of sources, one clean format
A portal is only as good as the data behind it. AIDA designs and builds data collectors that pull public information from dozens of sites, each of which builds and presents it in its own way, and turn it into one clean, consistent record. For the Job Seeker Portal, three collectors run every day:
What every collector does
- Public information only, collected on a schedule spread through the day
- Every posting standardized to one record: title, company, location, description, source, search term, country
- Each posting stored once, keyed by its address
- Each new posting scored the moment it arrives, by the same function as everything else
- Every run logged, so a source that changes or breaks shows up right away
- Each collector is its own workflow, so one site changing its layout can't break the others
The same approach works beyond jobs: any public information that is published across many sites in different ways.
Live job-market data
The database behind the Job Seeker Portal is open to explore, read-only. See what the collectors gather every day, where it comes from and how every posting is checked.
The dashboard talks to the live database through a gate that allows exactly two read-only reports: an overview and a list of postings. It has no way to write, change or delete anything.
The reports read only the columns they need from the job postings table: title, employer, location, source, industry, dates, status and the link to the original advert. Job seekers, clients, profiles, resumes and recruiters are out of reach, and scores, which belong to individual job seekers, are counted but never listed.
The database runs at our Toronto site and the page is served from our server in Quebec, so the data stays in Canada.
Built with guardrails
AIDA uses AI sparingly: to help build the portals and prepare documents, never as an unsupervised actor on client data.
All ten guardrails AIDA runs on: About Us ›
Where it runs
Data platform
- PostgreSQL database: postings, profiles, scores, reviews
- Staff dashboard and the scoring function
- Daily data collectors
- Everything in containers
Client portals
- A separate server in Canada hosts the portals
- Results synced from the data platform; client requests synced back through a checked job
- No client ever reaches the data platform
Network
- DNS and HTTPS for every portal
- A secure, outbound-only tunnel to the data platform, with no inbound ports open