CaribDevs
A marketplace where roughly 10,000 Caribbean developers — mostly auto-imported from public GitHub data and claimable by their real owners — get discovered and hired, alongside a regional tech job board.
- ~10,000
- developers across 25 islands
- Proof-of-work
- scores from real GitHub activity
- Live
- in production at caribdevelopers.com
The problem
Caribbean developers are hard to find and hire from the outside, and there's no single place they're visible as a talent pool. CaribDevs makes the region's developers discoverable — with real signal about their work — and connects them to companies and jobs.
What it does
Each developer has a public 'calling card' — handle, role, island, timezone, skills, links — plus a computed 'scouting report' of quality signals derived from real public GitHub activity and verified authorship, rather than self-reported claims. Most of the directory isn't self-registered: it's seeded by crawling public GitHub data per Caribbean territory, and a profile becomes fully interactive only once its real owner signs in and claims it.
Companies can search the directory, message a developer directly in real time, post a job, or post a freelance brief that developers submit proposals against. Alongside that runs a job board that mixes employer-posted roles with a weekly-refreshed aggregator of remote and Caribbean-local tech jobs pulled from several sources, always linking back to the original posting. There's also a forum, threaded discussion, and a moderation console.
Key features
A talent pool that already exists on day one
The directory is seeded from real public GitHub profiles across the region, so companies find thousands of actual developers immediately — not an empty site waiting for sign-ups.
Signal from real work, not self-report
A profile's quality scores come from real GitHub activity and verified authorship, so a hiring company gets proof-of-work signal instead of a self-graded résumé.
Claim your own profile
A developer signs in and their pre-seeded profile auto-claims, becoming editable and messageable — so the pool is real people who can take ownership, not scraped ghosts.
Hire, commission, or just message
Companies can search, message directly, post a job, or post a freelance brief for proposals — several real ways to engage, not just a contact form.
A job board that's actually full
Employer posts are blended with an aggregated feed of remote and regional tech roles, so the board has real jobs from day one and always links back to the source.
Where it stands
Live and fully functional, but currently a shipped, unmaintained sprint rather than something under active iteration — and most profiles are auto-imported from public data, so the directory is broad rather than hand-curated.
Under the hood — for the technically-minded
How it's built
The distinctive engineering is the pipeline from public data to a vetted directory: a territory-partitioned crawl of GitHub's search API (working around its 1,000-result-per-search cap by splitting the region into territories), followed by deterministic scoring from real repository metrics, plus an authorship-verification layer built specifically to catch fork-only or copy-pasted profiles. Its own seed code carries the rule: it does not fabricate hireable attributes for real people.
It's a deliberately lean Remix app over Postgres with Drizzle — real-time messaging runs on Postgres's own notification channel plus server-sent events rather than extra infrastructure, and the whole production stack is three services: the app, the database, and a daily backup. The jobs aggregator is nine source adapters with role and location filtering, dedupe and auto-expiry, run on a schedule behind a secret-guarded endpoint.
The hard problems
Building a directory of real people, honestly
Seeding from public GitHub data means representing real people who never signed up — so the scoring is derived strictly from real metrics and verified authorship, profiles stay claimable by their true owner, and the code refuses to invent hireable attributes. Getting that ethics-and-accuracy balance right is the core of the product.
Real-time messaging without heavy infrastructure
Rather than add a message broker, direct chat rides on Postgres's own LISTEN/NOTIFY plus server-sent events, keeping the production footprint to three services — a pragmatic choice that keeps a real-time feature cheap to run.
A jobs feed that stays fresh and de-duplicated
Nine different job sources, each formatted differently and overlapping, are filtered to genuine tech roles, de-duplicated, and expired automatically — run on a cron-secret-guarded endpoint rather than a standing background service.
Built with
- Remix
- Drizzle
- Postgres
- OAuth
Building something in this space?
Work with us →