Publish Jobs to No Fluff Jobs

Use Your No Fluff Jobs Feed

Kit provides a full-snapshot XML feed that No Fluff Jobs can fetch for your account. Use the URL that matches your career portal:

https://startupkit.app/careers/your-company/jobs/nofluffjobs
https://careers.your-company.com/jobs/nofluffjobs

The first URL is for a hosted Kit career portal. The second is for an account with a custom career domain. Open Hiring > Settings > Career portal to build, copy, and preview the exact URL for your account.

Narrow the Feed

The settings screen can add filters to the URL. The URL itself is the configuration, so you can give NFJ a focused feed without changing or duplicating jobs in Kit.

Filter	Example	Result
Country	country=PL	Includes roles whose structured country is Poland. For remote roles, Kit uses the applicant-location country.
Work mode	work_mode=REMOTE	Includes only remote roles. ONSITE includes only on-site roles.
Excluded department	exclude_department[]=Marketing	Excludes an exact department name, without relying on title keywords. Repeat the parameter to exclude several departments.

Filters combine. For example, a Poland-only feed that excludes Marketing can use:

https://startupkit.app/careers/your-company/jobs/nofluffjobs?country=PL&exclude_department%5B%5D=Marketing

The unfiltered URL contains every published role that meets the NFJ field requirements. Filters never make an incomplete role eligible; they only narrow the eligible snapshot.

Make a Job Eligible

A role appears when it is published, accepts applications, is set to publish to external job boards, passes the selected URL filters, and has:

• a meaningful description;
• a positive salary minimum and maximum;
• a recognized currency and hourly, daily, monthly, or yearly pay period;
• a supported employment arrangement;
• a structured city and country when the role is not remote.

Kit maps full-time and part-time roles to NFJ’s permanent salary type, internships to intern, and both B2B and generic Contract roles to NFJ’s B2B salary type. The two differ in employment type: a B2B role is sent as undisclosed, a Contract role as permanent.

Kit sends one location and one salary range because those are the structured values the posting currently contains. It does not infer hybrid days, extra locations, additional contract ranges, seniority, language levels, contract duration, or recruiter contact details from free text.

Understand the Snapshot

The XML root is always <offers>. Each eligible role is one <offer> with a stable identifier, title, visible salary, candidate and application URLs, work mode, employment type, sanitized description, category, and the structured location required for an on-site role.

Editing an included role updates the same offer rather than creating a duplicate. Pausing, closing, unpublishing, turning off external job-board publishing, or discarding it removes it from the next snapshot. NFJ normally treats a missing offer as a request to end publication, but that behavior can be changed during customer onboarding. Confirm the removal policy with your NFJ contact before production.

The candidate URLs include utm_source=nofluffjobs and utm_medium=job_feed, so applications that return to Kit retain their source attribution. The feed contains public job data only. It does not contain candidates, applications, credentials, or dedicated contactPersonName and contactPersonEmail fields. The public job description is exported as authored, so contact details written into that description remain part of the feed.

Complete NFJ Onboarding

1. Prepare a focused URL in Career portal settings.
2. Open the feed and confirm that the intended roles are present.
3. Give the URL to your No Fluff Jobs Customer Success contact for sandbox validation.
4. Test the relevant cases, especially remote and on-site roles, salary types, structured HTML, and removal from the snapshot.
5. Agree whether NFJ publishes automatically, asks for review before publication, or reviews after publication.
6. Agree whether a role disappearing from the feed causes unpublication.
7. Move to production only after NFJ confirms that its sandbox parsed the feed correctly.

NFJ documents several fetch windows during the day, but the timezone, business-day behavior, and the customer’s publication workflow are onboarding details rather than a Kit-controlled service level. A successful response from Kit proves only what Kit served at that request.

Troubleshoot a Missing Job

Hiring > Settings > Career portal lists every published role with the reason it is or is not in the feed. If a role is missing, check that:

1. The role is published and Publish this job to external job boards is on.
2. The selected country, work-mode, and department filters include it.
3. Salary minimum and maximum are both positive, use a supported period and currency, and the maximum is not lower than the minimum.
4. An on-site role has structured city and country values.
5. The description contains visible content after sanitization.

If the role appears in the XML but not on No Fluff Jobs, send the feed URL and role identifier to the NFJ Customer Success contact assigned during onboarding. Kit has no NFJ health or publication-status endpoint to inspect.

Quick Checklist

• Build a country/work-mode/department-filtered URL if the full account feed is too broad.
• Confirm that every intended role is present in the XML.
• Validate the feed in the NFJ sandbox.
• Agree the review and removal workflow with NFJ.
• Treat feed inclusion, NFJ fetch, NFJ draft creation, and live publication as separate states.