Publishing a role on Luminid takes four steps. The builder saves your draft automatically every 30 seconds, so you can leave and come back, and each role gets a requisition ID for your records.
Step 1. Role basics
Title, description, location and work type, and the screening criteria that inform matching, such as languages. Your company description comes from your company profile, so it stays consistent across every role you post.
Luminid does not run work samples in New York City yet. The builder will not publish an on site or hybrid role in the five boroughs, it asks for the state when a role in the United States has none, and every remote role shows that line on its job page. Anyone who tells us they live in the city never gets a work sample. Their card is flagged for your team with that reason and no work sample score, and a teammate decides the next step. While that flag is open, nothing from your flows reaches them, whatever starts the flow. A step that would message them, move their stage, tag them, or call a webhook or GoHighLevel is not run, the flow stops there, and its Runs list says why. Notes and teammate notifications still run. Their work sample invite is not sent, and their apply confirmation says that Luminid cannot run work samples for people who live in New York City yet instead of asking them to start one. If a teammate picks Keep them in, your flows go on, but anything that invites them into a work sample stays held, including the reminders about it.
Step 2. Skills and simulation
Pick the required and preferred skills for the role from the taxonomy. This list drives Role Match, so choose the skills that actually decide success in the role rather than a wish list. Then attach a work simulation. You can attach up to three in sequence, each with its own advance threshold. There is a toggle to force applicants who already passed the same simulation elsewhere to retake it fresh. It is off by default because it adds friction, and it is worth turning on only for security-sensitive roles.
Step 3. Knockouts and pipeline
Add knockout questions for the role's hard requirements, chosen from a catalog of compliant types. Luminid checks skill knockouts only today. The builder warns you when a knockout depends on a skill your attached simulation does not test. Then configure the pipeline stages this role will use, such as how many interview rounds.
Step 4. Review and publish
You see the job exactly as job seekers will see it. Publish when it reads right.
What happens at publish
The role goes live on the public job board and applications land on your pipeline board in real time. One honest expectation to set inside your team before the applications arrive. Every applicant sees a visible timeline of their application, and your decision window once you save one in Settings, so plan to keep each application moving.