Senior Full Stack Developer

Here's a skills list based on the actual stack and patterns in this codebase: ## Core technical skills **Backend / API** - Node.js serverless functions (Vercel's `api/*.js` convention — file-based routing, no framework like Express) - REST API design with dynamic route dispatchers (`[resource].js`, `[id].js` patterns handling multiple actions per file to stay under platform route-count limits) - Postgres, specifically comfortable with Drizzle ORM (schema definition, migrations via `drizzle-kit push`, raw `sql` queries for aggregates) - Designing cascade-safe deletes across relational data (FK order matters — classes → entries → scores etc.) - Session/auth patterns: reading and enforcing server-side authorization (role-based: organizer/judge/scribe/announcer/rider/staff), not trusting client-supplied IDs **Frontend** - Vanilla JavaScript and hand-rolled DOM string-templating (no React/Vue — the whole site is server-rendered HTML strings assembled in big `render()` functions) — comfort reading/writing large single-file HTML+CSS+JS documents (some files exceed 10,000 lines) - CSS without a framework: custom design tokens/variables, responsive breakpoints, print stylesheets - Real-time UI patterns: polling-based live sync (not websockets), debounced writes, optimistic UI with rollback **Integrations** - Clerk (auth/identity) - Stripe (Connect Express for multi-party payouts, Checkout Sessions, webhooks with signature verification, server-side price authority) - Vercel Blob (file storage, public vs private access) - Resend (transactional email) - Vercel deployment workflow (preview vs production, env vars, `vercel --prod`) ## Judgment / process skills - **Security-first instincts**: server-side validation of everything client-sent, especially pricing/amounts and cross-user data access (IDOR awareness) - **Read-before-you-build**: this codebase rewards finding and reusing existing functions/patterns instead of introducing parallel ones — a lot of the work is "trace how X already works elsewhere, do it the same way" - **Comfort with ambiguity + confirmation discipline**: distinguishing what's safe to just do vs. what needs explicit sign-off (production DB writes, live-mode payment changes, deploys) - **Live verification habit**: willingness to actually click through a flow in a real browser rather than trust that code changes work ## Domain knowledge (helps a lot, not strictly required) - Horse show / equestrian competition operations: classes, divisions, judging/scoring (dressage-style movement scoring, hunter/rail placement judging), ride order, scratches/DQs, ribbon placings, USEF/USDF/AQHA-style rules — understanding this domain makes it much easier to know what a "correct" feature even looks like, versus just implementing literally what's asked. Want this trimmed down to an actual formatted job posting (title, responsibilities, requirements sections), or is this list itself what you needed?