Contact
Talk to the resume builder team in the simplest channel that fits your issue
There is no forced support maze here. If you have feedback, a bug report, or a security concern, use the public routes below so the conversation stays transparent.
Read the disclosure guidance in SECURITY.md before reporting sensitive issues.
Open Security Policy (GitHub)Use discussions for roadmap ideas, Q&A, and community conversation.
Open GitHub DiscussionsBest for reporting bugs, feature requests, issues, and discussions with the resume builder or templates in a transparent way.
Open GitHubGood for quick feedback, updates, and discussions about the resume builder at @VeriWorkly X(prev twitter) account.
Open X / TwitterCheck what is already planned before starting a new request or discussion about features and improvements of VeriWorkly.
Open RoadmapWhat to include
- The page, resume template, or feature you were using when the issue happened.
- A short reproduction path, if the issue is technical.
- Screenshots or screen recordings for layout problems.
- Whether the issue affects the public site, resume editor, or dashboard.
- For security issues, share the minimum details needed to reproduce the problem and wait for a response before wider disclosure.
Security reports
Report sensitive issues privately through the security page.
If you believe you found a vulnerability, do not post it publicly first. Use the security page so the issue can be assessed before any wider disclosure.