Batch Run

Batch Run is for evaluating several postings in one pass. Use it after you have collected a list of roles from job boards, company career pages, referrals, or saved research. The goal is not to apply to everything. The goal is to sort the list into Apply, Maybe, Skip, and Manual Review so your best effort goes to the strongest opportunities.

A clean batch starts with clean inputs. Paste one posting per line when using links, or separate full job descriptions clearly when using text. Include the company name and role title when possible. Choose the run intent carefully: discovery runs should be broad, while application-prep runs should be stricter because they may create downstream kit work.

When the run completes, open Review Queue. Do not treat batch output as final action. Review the top scores first, inspect posting risk, and hold anything with missing compensation, unclear seniority, weak match, stale liveness, or unsupported source requirements.

Source behavior is intentionally conservative. Supported or launch-grade sources can move farther through the workflow only when the product has proof for that path. Greenhouse, Lever, and Ashby are review-gated and fixture-gated where supported. LinkedIn, Workday, captcha-protected, login-required, and unsupported hosts remain guided or manual-required unless proven otherwise. RoleWorth should stop at a clear handoff rather than imply it can submit everywhere.

Batch Run is most useful when paired with a weekly routine: collect roles during the week, run a batch, approve only the top few, and update Pipeline after each real action.