Role posts that sound like the company, not the ATS.
Hiring is a marketing problem wearing a hiring badge. Candidates read the employer brand long before they read the job description, and most role posts read like they came out of an applicant tracking system, because they did. Repic describes the employer brand once, in depth, and every role post, culture story and hiring update is generated from that same description.
Who this page is for: In-house recruiters, talent teams and independent recruiters marketing roles and an employer brand.
What actually goes wrong for recruiters and talent teams.
Written for this audience specifically. If it reads like the page next door, one of the two should not exist.
Role posts are written under time pressure by whoever has the requisition, so twelve openings read like twelve different companies.
The employer brand lives in a deck nobody opens, so nothing that gets published is actually derived from it.
Candidate-facing content competes with every other company saying the same three things about culture.
Volume is spiky. Ten roles open at once, then none, and the content cadence collapses in between.
What the product actually does here.
Every point below is something Repic does today, not something planned.
One described profile for the employer brand, covering who you are, who you want and how you sound, read by every engine before it writes.
The same profile produces a carousel about the team, a static post for a role and a story for a hiring update, so a candidate sees one company across all three.
Per-component quality scoring tells you which part of the employer description is too generic to generate anything distinctive from.
Staleness tracking flags previously generated work when the underlying description changes, which is what happens after every repositioning.
What Repic will not do for you.
The section that makes the rest of the page worth reading.
Repic is not an ATS and does not touch your pipeline, candidates or applications.
It does not source candidates, send outreach or run an AI SDR. There is no outbound here at all.
There are no seats or approval chains, so a large talent team with a review process will find it thin on governance.
Who should not use Repic for this.
A talent team that needs candidate workflow, sourcing or compliance tooling. Repic only makes the employer-brand content.
Employer brand is content, and most role posts are not it
Candidates read your employer brand long before they read a job description, and they read it in the same feed as every other company. The problem is that role posts are usually written by whoever owns the requisition, under time pressure, from the description in the applicant tracking system. Twelve openings produce twelve voices, and the aggregate reads like a company that has not decided what it is.
The employer brand itself usually exists, in a deck, from a workshop, and it is almost never the thing that content is actually derived from. That gap is the whole problem: a document nobody generates from is a document that has no effect. Every engine reads the same source of truth: your Brand Persona (the 25-field description of who you are, who you serve and how you sound) and the Brand Kit generated from it (palette, typography, logo direction, voice and strategy).
Described once, that profile drives the formats separately but consistently: a carousel about how the team works, a static post for a specific role, a story for a hiring update. A candidate who sees all three sees one company, which is the entire point and is also the thing a template library cannot give you.
Hiring volume is spiky in a way content cadence is not, and that is where most employer-brand programmes die. Ten roles open at once, everything is written in a hurry, then nothing is published for two months. Because the description is the durable object here rather than the output, a burst of role posts and the quiet month after it are generated from the same source, and the Quality Engine flags previously generated work as stale when the underlying description changes, which is exactly what happens after a repositioning.
What this does not do
It is not an ATS
Repic does not touch candidates, applications, pipelines or interview scheduling, and it holds no candidate data.
There is no sourcing or outreach
No candidate search, no sequences, no AI SDR. Repic makes the employer-brand content and nothing on the outbound side.
Straight answers
Can Repic write the job description itself?
It can write the post that markets a role, in the company voice. The formal description, with its legal and compliance requirements, should stay wherever your hiring process already owns it.
How is this different from a template pack?
A template pack makes twelve role posts look alike. A described employer brand makes them sound alike, which is the part a candidate actually registers, and it also means a repositioning changes every future post in one edit.
Does it work for an in-house team with review steps?
Partly, and honestly: there are no seats, roles or approval chains in Repic. A large talent team with a formal review process will find the governance thin, and that is a real reason to choose differently.