Complete your profile
Persona, skills, availability, and open-to preferences help discovery and matching.
Why profile completeness matters
Recruiters, collaborators, and matching systems do not read your mind. They use your persona, headline, skills, availability, open-to preferences, and — most of all — proof on your Builder Passport.
A half-empty profile with no projects usually loses to a clear profile plus one shipped demo.
Checklist (do these in order)
- Finish persona onboarding (your current stage, not your dream title in five years)
- Add a sharp headline and short bio (what you build + who you help)
- Set builder role and skills you can actually demonstrate
- Add location / timezone so collaboration is realistic
- Set availability and open-to (roles, internships, collabs, mentoring)
- Publish at least one portfolio project or finish a challenge submission
- Review Passport visibility so public vs private matches your comfort
What recruiters and collaborators notice
- Recent projects with problem → approach → outcome (not only a tech stack list)
- Challenge finishes with working links
- Skills that match the artifacts you show
- Clear availability (ghosted “open to work” with no proof looks weak)
Where to edit
Update these anytime under Settings / profile and journey settings. Revisit after every major ship — stale Passports convert poorly.
Tip
Ask Aurora: “What is missing from my profile for a junior backend builder?” Then fix one gap this week instead of rewriting everything.
Was this helpful?