DAO Job Board — Web3 job board for Developer DAO

Impact

Co-authored the founding RFC with angelgomez.eth and contributed across the early build — the relational schema for the full posting → application lifecycle, wallet-address-as-primary-key + EIP-191 nonce auth, a generic typed useSupabase<T> repository hook, the TypeScript migration of the Next.js client, the sibling Hardhat workspace for the gig-payments path, and the contributor / DX scaffolding the rest of the community contributors inherit.

Outcomes

• Co-authored the founding RFC — “RFC: User Stories for DAO Job Board” — with angelgomez.eth (Design Guild support from jazza.eth), enumerating user stories across job seekers, recruiters, organisation members, and general users, and sketching the four-phase MVP delivery plan.
• Authored the Supabase / Postgres schema for the full posting → application lifecycle — users, organisations, organisation_members, jobs, gigs, job_applications, gig_applications, keywords, M:N keyword joins, and a polymorphic links table — with soft-delete columns everywhere and a single soft_delete Postgres RPC behind it.
• Pivoted users.id from a generated uuid to the wallet address itself so the relational graph is wallet-native end-to-end, and added the nonce UUID column to back EIP-191 sign-in-with-wallet ahead of the smart-contract-gated gig path.
• Authored the generic typed useSupabase<T> repository hook that gives every schema table a typed CRUD facade (all / find / create / update / softDelete) in one line, with structured logging and compile-time table-name checking through a discriminated Table union.
• Migrated the Next.js client from a JavaScript starter to a TypeScript-first project and authored the data-model types (User, Organization, Job + JobApplication, Gig + GigApplication, Keyword, Link) plus shared primitives.
• Set up the Yarn workspaces monorepo shape with client, database, and a sibling Hardhat workspace scaffolded from Hardhat's advanced TypeScript sample, so the gig-payments path has a place to land alongside the client without forking the repo.
• Shipped the contributor experience and DX scaffolding the rest of the working group inherits — Doppler-based env management with a descriptive README guide, issue templates, a proposal template, a PR template, and prettier + lint-staged + husky wiring that runs on every commit.