Private person record
Email and LinkedIn
Overflow uses these for review, contact, event participation, and matching. The application LinkedIn URL stays private; marked LinkedIn career context is removed from the uploaded profile.
How matching works
Evidence first. Introductions after.
Overflow's matching layer starts with profile v5: a reviewed view of your local agent work, authenticated GitHub history, optional career context, and an anonymous cohort section added after submission.
The flow
From your evidence to a private matching record.
- Run profile v5. The public prompt reads supported local agent history and your authenticated GitHub activity. LinkedIn career history is optional.
- Review the report. Nothing submits itself. Edit or remove anything you do not want to share. The local copy shows the complete staffing read but withholds the cohort-comparison section.
- Submit the application. Overflow requires the reviewed HTML, email, and a private LinkedIn URL. Any optional LinkedIn career section in the local report is removed during upload.
- Unlock the cohort section. Overflow calculates the anonymous comparison from the submitted snapshot and adds it to the stored report. Applicant-supplied cohort data is discarded.
- Choose visibility. The profile is private to Overflow by default. Public publication is an explicit choice, and profile owners can change it later.
- Enter membership review. A completed application sets the membership record to applied. The organizer decides membership through the private admin.
- Keep matching evidence queryable. Overflow stores structured profile data and skill rows so the private bench can be searched and compared when fit matters.
What is separated
Contact identity and project-fit evidence do not have to travel together.
Project-fit record
Skills, tools, domains, and fit
The uploaded file and its structured data support the matching view. The current upload path also checks for common secrets and private keys.
Private by default
No public URL unless selected
Applicants choose between private-to-Overflow and public publication. Private is the default in the application interface.
Owner controlled
Publish, replace, or delete
A secure management link lets the profile owner preview, publish, unpublish, replace, update the private LinkedIn record, or delete the project-fit profile.
Separate on purpose
An event RSVP is not a membership application.
People can request an invite to the Austin event with a short RSVP. A project-fit profile is not required for event attendance.
The project-fit profile becomes required only when someone applies to the standing community and its private matching layer.
- Attend: request an event invite with name, email, and LinkedIn.
- Apply: submit the reviewed project-fit profile with the standing-community application.
- Manage: use the secure profile flow to change publication or replace the evidence.