Why we don't press Send

Crossing opens the employer's own application page with your answers already in it, and then it stops. The Submit button is yours to press.

The two reasons

It is not possible without breaking something. Every mainstream applicant tracking system gates submission behind a captcha bound to its own origin, so a token minted anywhere else is refused. The server-side endpoints that do create candidates authenticate with a key issued to the employer, not to the applicant.

It is not a good idea even where it might be. Employers are filtering applications that arrive in bulk, and the name on those applications is yours. A tool that fires two hundred a week is spending your reputation on a tactic that has already stopped working.

What that means in practice

• No application is ever sent that you have not looked at.
• We hold no login for any applicant tracking system, so there is nothing to leak.
• When a board changes its form, you see it happen on the screen in front of you. You do not find out from a drop in replies six weeks later.

The engine holds this rather than trusting anyone to remember it. What the apply engine returns is either a URL to hand you or a failure — there is no third case, so "submitted" is not a state the product can represent.

Attaching your résumé

Browsers do not let a script put a file into a file input, for good reasons. So the autofill helper fills every text, dropdown and yes/no field it can, then hands you a download link for the tailored résumé and tells you it could not attach it. You pick the file. It is the one step that will not get shorter.

The long version, with what we found on each board, is on the blog: why nothing can press Send on your job application.