career-ops exists because of the people who build with it. thank you.
Contributors with sustained technical ownership over specific areas. Full authority over content direction within their scope.
-
@bracketouverte (Michael) — Technical contributor focused on scan mode and ATS research. Running daily support in Discord.
-
@piscespieces (Andres Urdaneta) — Docs architect. Maintains the getting-started guides at career-ops-docs.vercel.app. Shipped PR #286 (portals cleanup). Authored the comparative analysis that defines what career-ops is vs. isn't.
- @CURT1S03 (Curtis) — LaTeX/Overleaf CV export (PR #362, merged — resolves #47)
- @vivek-gite — A16Z provider support (PR #271, in review)
- @3fones — LinkedIn scanner (WIP, paid Claude Max to build on top of the project)
- @kennedy58 — Testing alternative inference providers
- @kelvan — Surfaced the token consumption issue that drove the optimization roadmap
Members who landed roles using career-ops and opted in to share their journey publicly. Their tips and patterns shape how we explain the project.
- @logumani2112 — Landed Backend Developer (.NET) at an IT services company. 50 listings evaluated, 1 month from first scan to offer. Most useful feature: A–F evaluation scoring. Their tip: "Focus on quality over quantity. Use the evaluation scoring to prioritize the right opportunities and tailor your resume for each role." (#440)
Members helping newcomers in Discord day-to-day.
- @mbaku.shogun — Support in #getting-started
- @.ham__. — Support and onboarding
- @banadi (Mauricio) — Support and onboarding
- @systemsyogi — Support and onboarding
- @nafterg — Community organization suggestions, Discord structure
See CONTRIBUTING.md and the Contributor Ladder in GOVERNANCE.md. Open an issue first for anything beyond a typo fix — we merge fast when scope is clear.