Send feedback or project questions.

Helpful reports include the page you were using, the browser and device, what you expected to happen, and whether the issue affected drafting, scoring, saving, exporting, navigation, or theme behavior. If a prompt feels unclear, include the wording that slowed you down and the kind of career situation you were trying to describe.

For consulting or product questions, include the workflow you want to improve and whether you need research, design review, prototype work, security review, or a small internal tool. The same contact route can be used for accessibility feedback and privacy questions.

If you are reporting a career-tool issue, do not send private employer documents or sensitive personal records. A short example, the page name, and the step that failed are usually enough to reproduce the problem and make the next update more useful.

Good feedback is especially helpful when it explains the moment where the tool stopped matching the job-search task. That might be a confusing prompt, a score that did not reflect the draft, an export that needed a different format, or a navigation path that made it harder to return to unfinished work.

For accessibility issues, mention the assistive technology, keyboard path, or screen size involved.

Short, specific notes are easier to act on than full private drafts.