What makes a good project post?
The best project posts are specific, realistic, and honest about what's needed. Vague posts like "I want to build something with AI" attract no one. Specific posts attract the right people.
Required fields
- Title — a clear, specific name (not "My portfolio project")
- Problem statement — what problem does this solve, and for whom?
- Roles needed — be specific: "1 data scientist for ML modeling, 1 SWE for the API"
- Skills needed — list the specific technologies and skills required
- Scope — rough estimate of the project size (small/medium/large)
Tip: Write your problem statement as a user story. "A student wants to track their job applications but can't find a simple tool that also surfaces insights" is 10× better than "a job tracker app."
After posting
Your project appears in the feed immediately. You'll start receiving join requests from builders who want to collaborate. Review each request and check the applicant's profile before accepting.
Managing your project
From your project page you can:
- Review and accept or decline join requests
- Post build updates to share progress with the community
- Manage your team through the HiveOS workspace
- Submit for peer review when ready