Add it
Paste the code where the jobs should go. For every open job:- Every open job: Settings > Embed in the web app or the desktop app has the code with your slug in it.
- One job: Add to your site in a job’s … menu has the code with that job’s id in it.
- Your agent: ask it to put your jobs on your site. The
careers_embedtool hands it both.
div isn’t there, the jobs go right before the script.
What it does
- Every open job: your jobs grouped by department and team, with the same search, work type, and location filters as your company page. A filter with one choice is hidden.
- A job: its description, then the apply form under it, and All jobs to go back.
- One job’s form: only the apply form.
- A closed job says it’s no longer taking applications, and goes back to your list when there is one.
?job= with the job’s id, so a reload or a shared link opens that job.
At the foot of the embed a line says applications go to your company through Hotfix, with a link to Hotfix’s privacy policy.
Applications from your site
Everyone applies as a guest and confirms their email with a code, as on hotfix.jobs unless you turned confirmation off. An application from the embed hassource: "site", and in the app it says they applied on your site. Filters > Source on Home narrows to them. See Where they came from.
The embed passes your page’s ?source= or utm_source on as the application’s channel, so tracking links to your own careers page still count.
When someone applies, your page gets a hotfix:applied event on window, with the company’s slug and the job’s id. Nothing about the person is in it.
Make it look like your site
Without a stylesheet, the embed has a plain look: no background of its own, a system font, and simple rows. Your stylesheet changes as much of it as you like. Settings > Embed has the stylesheet. Save draft checks it and keeps it as a draft, Preview opens the embed with the draft, and Publish puts it on your site. You can also ask your agent to match your site’s look: it reads your site’s CSS, writes the stylesheet, and sends you the preview before anything changes. Owners and admins change the stylesheet.Variables
Set these on:root for most of the look:
Classes
For anything further, style these classes. They stay the same as the embed changes.
A field carries
data-type with its kind (text, email, textarea, single_select, boolean, file, and so on) and data-invalid when it has an error.
An example
This is the stylesheet behind Beacon, the made-up company on the hotfix.jobs homepage: black and white, each department in a column of its own beside its jobs, every job’s facts under its title with an arrow at the end, and the filters as one underlined bar. The@media block follows the visitor’s light or dark setting. Upload the font under Settings > Embed first and use its address in @font-face.
What a stylesheet can’t do
The embed takes applications, so a few things hold whatever the stylesheet says:- What a candidate must see stays visible: the privacy line, the voluntary self-identification note, every question’s label and required mark, errors, and the submit button. You can restyle them but not hide them.
url()reaches only your own files: fonts and images you upload under Settings > Embed (woff2, woff, png, jpeg, gif, or webp, up to 2 MB each), or smalldata:images, SVG included, and fonts. A web font from elsewhere has to be uploaded first.- No
@import,@layer, or@namespace, and noimage-set(),expression(), orpaint().