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.
- @razour08 (Ramzi Dekali) — Arabic translation support (
modes/ar/andREADME.ar.md) for the Arab market. - @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)
- @chinna63055 — 200 listings evaluated, 2 weeks from first scan to offer. Most useful feature: A–F evaluation scoring. (#388)
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
Everyone below has had work merged into career-ops. This list is not a ranking and not a hierarchy — it is alphabetical, and the icons say what kind of work someone did, not how much. Roles with actual repository access live in MAINTAINERS.md.
Key: 💻 code · 📖 docs · 🌍 translation ·
Missing? Nothing here is deliberate exclusion: this list was seeded from merged
pull requests, so non-code work (bug reports, ideas, reviews, support) is still
being added. Comment on any issue or PR with
@all-contributors please add @your-username for bug, ideas and the bot will
open a PR. You can also ask on your own behalf — that is not rude here.
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.