Gaden AEL™ · Job Pages & Career Board
Gaden Recruit turns a job order into a real web page with its own shareable link. You post the link wherever your candidates already are. People apply with a resume and a portfolio — no account, no portal, no password. Whatever job board, group or referral they came from, they land in the same database, tagged with the channel that produced them. By the time you open your laptop, every applicant has been read against the job description, scored with cited evidence, ranked and attached to the right job order — and every one of those calls is still yours to make.
The link is composed while you type the title and location, and goes live the moment you publish. Every channel carries its own tag, so the candidate arrives with the channel that produced them already stamped on the record.
Why this exists
The normal way to fill a role is to pay a board for a slot, wait, and then work inside somebody else’s inbox. The applicants sit in their system. The screening is a keyword match you did not write. The moment you stop paying, the pipeline you built disappears with the listing.
Gaden inverts it. The page belongs to you, the link belongs to you, and the applicant lands in your candidate database with a fit score attached. Distribution is something you already have — your network, your groups, your posts, your email signature. What you were missing was somewhere professional to send those people, and something that reads every resume the second it arrives.
Search: how do I post a job and get applicants
Job Pages lives on the Talent side of Gaden, first in the funnel order: you publish, they arrive, you move them, they start. Opening it without picking a role gives you the board — every job order you have, which ones are live, the public link for each one, and how many people have applied.
The board shows live pages in emerald, roles that are written and ready to publish in gold, and closed roles in coral. Nothing in the board is grey, because “ready to publish” is not a dead state — it is the next thing you should do today.
Title, location, on-site or remote, employment type, pay range, the description, and the requirements split into what is required and what is preferred. That split is not cosmetic: it becomes the rubric the pre-screen scores against later.
Publishing writes three things at once: the public page, its structured data for search engines, and the preview card social platforms will render. The link stops being a draft and starts being an address you can paste anywhere.
One link, tagged per channel. Post it to a LinkedIn feed, a Facebook group, an Instagram bio, a WhatsApp broadcast, a text message, or the bottom of every email you send.
Applicants arrive ranked with the reasoning attached. The alert reaches you by email; the candidate is already in the pipeline, on the right job order, at the first stage.
Closing a page does not delete the applicants or break the link — visitors see that the role is filled, and the candidates you collected stay in your database for the next opening like it.
Search: what does the job page look like
The page carries your name, your logo and your brand colour. Text contrast is calculated from the colour you pick, so a light brand does not end up with white type on white. The only Gaden mark anywhere on it is a line in the footer.
Logo, agency name and accent colour, with contrast worked out from the colour rather than assumed.
A range with its period — per hour, per week, per year — or hidden entirely when the client will not allow it.
Candidates stop self-rejecting over a nice-to-have, and the same split becomes the scoring rubric later.
Ask what you always ask on the call. The answers travel into the record and get read with the resume.
You learn the difference between a role nobody saw and a role people saw and refused to apply to.
A posting past its date stops taking applications and says so, instead of collecting resumes nobody will read.
The form says so honestly, and the candidate gets an email confirming it arrived.
One quiet line in the footer. Everything above it belongs to your agency.
gadenrecruit.com/careers/your-agency
One permanent address for your website, your bio and your signature. It updates itself as roles open and close.
Search: career page for a staffing agency
Individual job links are for campaigns. A career page is for identity. Gaden serves both from the same data: publish a role and it appears on your career page automatically; close it and it comes off. You never maintain a second list, and you never hand out a link that goes to a dead posting.
That page is also where inbound interest lands when someone hears about you and searches your name. Instead of a contact form, they see real roles, real locations, real pay ranges, and a way to apply in under a minute. Put it in your email signature once and it works for every open role you will ever have.
Both surfaces are rendered by the server rather than assembled by a browser app, which is what makes them shareable, crawlable and fast on a phone with two bars of signal — the conditions most candidates actually apply under.
Search: where do the resumes go when someone applies
Most application forms lose the candidate at the account step. Gaden does not have one. The applicant types their name, email and phone, attaches a resume, adds a portfolio link if the role deserves one, and submits. Everything after that is machinery they never see.
PDF or Word, up to 15 MB, uploaded straight to the endpoint that handles the application. The public page never loads a database client, which keeps it light and keeps your workspace closed to the outside.
Not a form submission sitting in a queue — an actual candidate in your database, attached to that job order, stamped with the channel from the link, timestamped so every sorted view sees it, and placed at the first stage of your pipeline.
A hidden field bots fill and humans never see, a submission ceiling per address held in the database so it survives scaling, and a size limit. If the limiter itself breaks, the application goes through — a lost applicant costs more than a bot that slipped in.
The Applications inbox inside the publishing studio, which is the per-page view: who applied to this role, in order, with their file, their portfolio, their channel and their score.
Your candidate database, which is the per-person view: the same applicant sitting in the pipeline for that job order, ready to be moved, screened, submitted to the client or saved for the next role that looks like this one.
Same record, two lenses. Nothing is copied by hand between them, which is the difference between a form that emails you and a system that recruits.
Search: keep applicants from every job board in one place
You will keep posting on job boards, in groups, in messages, in your newsletter, and you should keep whatever produces candidates. Distribution was never the problem. The problem is that the people who answer end up in five different places, and by Thursday nobody can say who applied, who was any good and who never heard back.
Every place you post gets a link you own, tagged with the channel it belongs to. A board post, a group, a referral, your own career page — different doors, same room. The applicant arrives attached to the job order, stamped with where they came from, scored against the same description as everyone else.
Then you can simply ask. Who applied to the warehouse role this week. Who scored above eighty and is still waiting on a reply. Who applied twice for two different roles. Which channel actually produced the placement, not the clicks. Gaden reads the whole desk rather than one screen, so the answer comes back in a sentence instead of a report you had to build.
That is also why nothing gets lost between screens: the applicant, the score, the emails they were sent, the stage they are in and the invoice at the end are all the same record seen from different angles.
14 applicants. 4 strong fit, 5 fit, 3 consider, 2 not qualified. 6 came from your own link, 8 from a board post.
Two. M. Reyes at 92, applied Monday, no email sent. D. Kimani at 78, applied Tuesday, no email sent.
Your own link produced both placements this quarter. The board produced the most applicants and no hires.
Yes — twice. CNC Machinist in March, scored 61. Warehouse Supervisor now, scored 78. Same email address.
Same questions you would ask an assistant who had been at the desk all week. The difference is that this one read every application.
Boards, groups, referrals, your career page and direct shares each carry their own tag. At the end of the month you are comparing hires per channel, not impressions.
Every application gets a confirmation, and Gaden can tell you at any moment who is still owed an answer. Silence is what costs you the candidate you will need next quarter.
The person who was not right for this role is already screened, scored and tagged for the next one like it. You paid for that sourcing once; it should not expire when the posting closes.
Search: is this applicant any good
This is the part that changes the job. The moment an application lands, Gaden pulls the text out of the resume, puts it beside the description you published, and works through the requirements one at a time. Not a keyword count — a reasoned read that has to show its work.
The same four tiers your screening room already uses — strong fit, fit, consider, not qualified — written into the same fields, so the applicant appears ranked in the desk without a second tool.
“Supervised a 22-person receiving crew across two shifts” — matches the required 3+ years supervising in a distribution environment.
No forklift certification appears anywhere in the resume. Treated as a gap, not softened into a maybe.
Bilingual English/Spanish — preferred, present. Counted as an advantage, never as a reason to fail someone who was never asked for it.
Three roles in four years. Worth asking about on the call. Not scored as disloyalty.
Two rules are written into the reasoning itself. It is forbidden to infer or comment on protected characteristics — age, origin, family status, health, anything of that kind — from a resume. And when the extracted text is thin, a scanned image or a badly built PDF, it says so instead of inventing a confident number from nothing. A score you cannot audit is worse than no score.
Scoring runs once per application, guarded so a duplicate delivery cannot double-score a candidate or send them two emails. Read more about the rubric and the shortlist on the PreScreen Room page.
The pre-screen exists to put the pile in order, not to hire or reject anybody. Nothing is closed out on a number alone, and every step of the reasoning is on the screen so you can disagree with it in ten seconds instead of trusting it blindly.
Each judgement carries the line from the resume it came from. A score you cannot audit is worse than no score.
Candidates near the line are routed to human review rather than auto-rejected. That is where the good hires hide.
Move anyone anywhere. Your correction is the signal that calibrates the next run, so the rubric learns your desk.
Outreach can be held as a draft for you to read, edit and release. Sending on its own is a switch you turn on, never the default.
Two rules the reasoning is not allowed to break: it never infers or comments on protected characteristics, and it never dresses up thin evidence as a confident number. Both are constraints on the model, not promises in a brochure.
Search: automatic follow up with applicants
When the pre-screen clears the bar you set, the candidate gets a real next-step message and advances a stage. Momentum is the whole game in high-volume staffing: the fastest recruiter to reply wins the placement more often than the best one.
Silence is the industry default and it costs you the next role. A short, respectful close keeps your name clean in the exact community you will be recruiting from again in three weeks.
The alert that reaches you contains the assessment: tier, score, the requirements met and missed, the evidence, and the resume. You decide on the candidate from your phone, in a queue, without opening the app.
Candidate mail goes out through the recruiter’s own connected mailbox rather than a no-reply robot. Three things follow from that. The candidate can simply reply, and the reply lands in the inbox where the conversation belongs. The sending domain is already trusted, so the message reaches the primary tab instead of promotions. And your agency’s name is on it — never a vendor’s, never a platform’s.
If a mailbox was never connected, delivery falls back to your configured mail server, still branded as your agency. Every message is built with the table-and-inline-style construction that survives Outlook, because a beautiful email that renders broken is a broken email.
Search: who works my job orders when I am not working
“Send this at five” happens once and it is over. “This role is yours until it is filled” is something else entirely: it lives for days, it has a state, and it moves on its own between wake-ups. Hand a published role to Gaden as an assignment and the desk keeps working after you close the laptop.
The obvious design is to clear everything pending in one pass. It is rejected deliberately. If something is configured wrong, forty actions at three in the morning is forty times the damage, and you find out from the replies. One at a time lets the pattern show before it multiplies — and it is also how a real recruiter works: a few good plays a day, not a burst.
The ladder runs in the only order that makes sense. Nobody attached to the role, so it searches your database. People attached but unscored, so it scores a batch. Scored and untouched, so it writes. Nothing worth doing, so it writes that down and sleeps longer.
Its first play is the one recruiters never get to: attaching people already in your database that nobody had connected to this search. That sourcing was paid for months ago.
When the pool genuinely has nobody, that is recorded as a sourcing gap rather than a shrug — the role needs candidates from outside the desk, and you find that out on day one instead of week three.
They matched on supervisor, warehouse, WMS, Newark. Nobody had connected them to this search.
Best fit M. Reyes at 92 — six years supervising a receiving crew. Weakest point: no forklift certification listed.
They scored 70 or above against this role. You have this assignment set to draft only.
6 candidates attached, all screened, nobody new above the bar.
Every play writes down what it did and why, and who it touched. An employee that works at night and leaves no notes is not autonomous, it is opaque — and three days later nobody can say why a candidate is where they are.
It sources and it scores. It never writes to a candidate. For the desk that wants the pile prepared and every word of outreach kept human.
It composes the message with something real from that person’s record and leaves it waiting for you. You read, edit, release. Most desks live here for the first month.
It goes out on its own, above the score bar you set. Not a tentative version of the feature — the real one, with the rails underneath it.
A bug that drafts too much gets deleted. A bug that sends too much burns one relationship per email, and those do not come back.
Without it, a retry writes to the same person twice. Two emails in an hour from the same recruiter reads as desperation.
One switch stops every assignment without deleting any of them. At three in the morning you need a button, not a migration.
It also respects what you actually know. Notes from the intake call outrank the written description, because that is what the client really said they wanted. And you only get interrupted when something happened that is yours to look at — candidates attached, emails waiting, emails sent. Silence means nothing needed you.
Search: how do I get my job on Google
A link you share is only half the distribution. The other half is people searching for the role you are filling, in the town where it is. Every page Gaden publishes ships with the structured data search engines read to place a job in job search results — title, employer, location, employment type, pay range, posting date — written at publish time rather than assembled by a browser.
Published roles are listed in a jobs sitemap so crawlers find new pages without waiting to stumble on a shared link, and each page carries a preview card so the first impression on social is a designed object instead of a bare URL.
Whether a specific role is shown in job search results is always the search engine’s decision. What Gaden guarantees is that the page arrives with everything the engine asks for, and nothing that makes it hesitate.
Baked in when you press publish, not generated on the fly.
Every live role listed for crawlers automatically.
Title, role and agency render properly when pasted.
Server-rendered HTML, no app bundle to download first.
Search: full cycle recruiting software
A publishing feature that hands you resumes and stops there has moved the pile, not removed it. The reason the job page matters is that it is the front door of a loop that keeps running: the same employee that published the role screens the applicant, moves them, submits them, protects the paperwork, raises the invoice and chases it until the money lands. That loop is the product. Gaden calls it the Autonomous Employee Loop.
Written once, live immediately, tagged per channel, listed on your career page.
No account. File stored, record created, channel stamped, pipeline entered.
Board posts, groups, referrals and your own page all land in the same database, tagged by source.
Requirement by requirement, evidence cited, tier assigned, ranked in the desk.
Borderline candidates routed to human review; profiles come out presentable in the PreScreen Room.
The advance email can carry your booking link, so the interview lands on the calendar without a thread about availability.
Sourced through offer on the Recruitment Desk, with the assignment sourcing, scoring and writing between your sessions.
Offer letters, agreements and redlines with Gaden Counsel before anybody signs.
Start date, documents, the guarantee period counting down, at-risk placements flagged in Onboarding.
Placement to invoice without a spreadsheet handoff, inside the Payment Brain.
You are told what you are owed and who to push, and who pays late before they do, in Collections.
Which channel produced placements, which requirement kept failing, which client pays late. The next posting starts smarter than the last.
Search: job board vs own career page
| Paid job board | Gaden job pages | |
|---|---|---|
| Cost per role | Per post, per bump, per refresh, per seat | Included — publish, close and reopen as often as the desk needs |
| Who owns the link | Theirs. It dies with the listing | Yours. Your domain, your slug, permanent |
| Where applicants live | Their dashboard, exported by hand | Your candidate database, attached to the job order |
| Screening | Keyword filters you did not write | Reasoned scoring against the description you published, with cited evidence |
| Candidate experience | Account creation, then a duplicate profile to fill in | Name, email, phone, resume, submit. No login |
| Follow-up | Manual, or a no-reply template | Sent from your own mailbox — advance, decline, and the pre-screen to you |
| Channel attribution | Their traffic, unattributed | Every share tagged, so you learn what actually produces hires |
| Applicants from every channel | Scattered across each board’s own dashboard | One database, tagged by source, all scored against the same description |
| After hours | The listing sits there | A standing assignment sources, scores and drafts between your sessions, and writes down why |
| What happens next | Nothing. You copy the resume elsewhere | Pipeline, submittal, onboarding, contract, invoice, collection |
| When you stop paying | The pipeline disappears with the listing | The candidates stay. They were always yours |
Boards still have a place for reach on hard roles. The argument is not that you should never buy traffic — it is that the traffic should land somewhere that belongs to you and screens for you, instead of somewhere you rent by the month.
Short answers. The long ones are on the module pages.
Yes. Publishing a job order creates a public page at gadenrecruit.com/j/your-job-slug. It is real HTML served from the server, so it opens instantly on a phone, previews correctly when pasted into LinkedIn, Facebook, Instagram or WhatsApp, and can be indexed by search engines.
No. No sign-up, no password, no portal. Name, email, phone, resume, optional portfolio, submit. Removing the account step is the single biggest reason application forms get abandoned, and it is why a page like this outperforms a board profile on the same audience.
Into your own workspace. The file is stored under your organization, an application record is created, and a candidate appears in your candidate database attached to that job order, stamped with the channel it came from, timestamped, and placed at the first stage of your pipeline.
Yes, on arrival. It extracts the resume text, compares it requirement by requirement against the description you published, keeps required and preferred separate, cites the evidence behind each judgement, and assigns a fit tier. The result is written into the same fields your pipeline and screening screens already read, so the applicant shows up ranked rather than as another attachment.
You. Candidate email is sent from the recruiter’s own connected mailbox, so replies land in the right inbox, deliverability rides on a domain that is already trusted, and your agency’s name is on the message. If no mailbox is connected, it falls back to your configured mail server, still branded as your agency.
Yes. Alongside individual job pages, Gaden serves a career page listing every live role for your agency. Publish a role and it appears; close it and it comes off. One permanent link for your website, your bio and your email signature.
Each published page carries JobPosting structured data written at publish time and is listed in a jobs sitemap. That is what search engines read to place a role in job search results. Indexing is always their decision, but the page ships with everything they ask for.
A hidden field no human ever sees, a submission limit per address enforced in the database rather than in memory so it holds when traffic scales across instances, and a file size ceiling. If the limiter itself fails, the application is allowed through — losing a real applicant is more expensive than letting one bot in.
The same loop carries the candidate forward: shortlist in the screening room, submittal to the client, interview and offer, contract reviewed, onboarding with the guarantee period tracked, then the invoice raised and collected. That whole cycle is what the Autonomous Employee Loop means.
No, and that is deliberate. A board rents you traffic and keeps the applicants in its own system. Gaden gives you your own pages, your own links and your own database, so the candidates you attract stay yours and arrive already screened.
Yes, and you should keep whatever produces candidates. Gaden gives you a link you own for every channel, tagged per channel, so applicants from a board post, a group, a referral or your own career page all land in one database instead of being scattered across separate dashboards. Every one of them is scored the same way against the same job description.
Yes. Gaden scores and ranks; the recruiter decides. Every score shows the evidence behind it so it can be checked, borderline candidates go to human review instead of being auto-rejected, a score can be overridden, and outreach can be held as a draft for approval so nothing reaches a candidate without a person releasing it.
Yes. It reads the whole desk rather than one screen, so you can ask in plain language who applied to a role this week, who scored above a bar, who is still owed a reply, who applied twice for different roles, or which channel produced the placement — and get the answer in a sentence.
Only if you tell it to. An assignment has three modes: off sources and scores but never writes; draft composes and leaves the message waiting for you to release; send goes out on its own above the score bar you set. Send carries a cap per wake-up, a memory of everyone already contacted so nobody is written to twice, and a kill switch that stops every assignment on the desk without deleting any of them.
Yes. Your name, logo and brand colour, with the text contrast calculated from the colour you choose so a light brand does not end up unreadable. The only Gaden mark is a Powered by Gaden line in the footer.
Yes. Questions you add to the role appear on the public form and the answers travel with the application into the candidate record, so both the pre-screen and you read them next to the resume. You also choose whether phone, LinkedIn, portfolio and resume are asked for or required.
Yes. Publishing, the applications inbox, the pre-screen alerts and the pipeline are all reachable from a phone or tablet. Recruiting does not happen at a desk, and the parts of the job that decide placements — answering a good candidate first — happen while you are moving.
Gaden AEL™ · Autonomous Employee Loop
Gaden is the world’s first autonomous recruitment employee. It reasons, speaks naturally, sources candidates, builds strategies, manages pipelines, drafts email, generates invoices, and self-corrects until the job is done.