Project Setup

Goal

Create a project structure that remains usable after more features, more roles, and more interview rounds are added.

Who This Is For

• Users preparing multiple target roles or companies
• Users moving from one-off testing into repeatable project-based work
• Users who want learning, interview, and resume changes to stay attached to one target role

Outcome

After this guide, you should have:

• A clearly named formal project
• A primary target JD with a clear purpose
• A resume baseline ready for versioned iteration
• A project route that can continue into learning center and interview simulation without rework

Recommended Setup Rules

1. Name the project by role + company/direction + date or cycle so later comparisons stay readable.
2. Start the project from formal onboarding, not only from quick experience, when you want long-term continuity.
3. Add one primary JD first. You can expand later, but the first round should always have one clear target.
4. Keep one baseline resume version immediately after upload or template initialization so rollback always has a clean anchor.
5. Use version labels that explain intent, such as v1-upload, v2-roundtable, v3-preview-ready.

Current Workflow Notes

1. Source-aware onboarding now changes the opening explanation and the recommended next CTA. Treat it as your project router, not only a creation form.
2. If you skip the readiness assessment, the project still enters the formal chain. The system will guide you toward the workspace first and keep assessment as a later action.
3. If you came from quick experience, remember that the formal project is where versions, learning plans, interview reports, and archive history become persistent.
4. Once the project exists, move into the workspace and bind the JD before you depend on roundtable suggestions or downstream learning recommendations.
5. Keep the help replay button available in major surfaces so team members can re-run the current guide when the feature set changes.

Screenshot reference: capture the onboarding source card, the formal-project result CTA, the primary JD selection state in the workspace, and the version naming pattern used in a real project.

In-Product Links

• Start Onboarding from Dashboard
• Start Onboarding from Projects
• Open Projects
• Open Dashboard

FAQ

• Should one project track one role or one company?
  • Default to one role direction per project. Add company-specific differences inside JD selection and versions.
• Can I keep using quick experience instead?
  • Only if you are testing the product briefly. Formal projects are the only reliable place for long-term guidance and records.
• What is the first milestone after setup?
  • A JD-bound resume baseline with version labels ready for roundtable consultation and preview review.

Next Step

Move to Resume Optimization Workflow to use suggestions, versions, preview, and export as one controlled loop.