Back to Jobs

Senior Full-Stack Developer — Next.js, Supabase & Claude Code

Confidential employer

Posted 8/27/2026Rate visible after sign-upSource: Curated from source
Next JS
Fullstack
Supabase
About the Role

Gather is looking for a senior full-stack developer who can learn a complex production application, use Claude Code to work faster, and independently move well-defined work from Linear ticket to verified GitHub pull request.

This is an asynchronous relay role. You will normally work during your daytime in the Philippines, covering much of the time when the founder is offline in the U.S. Eastern time zone. The goal is for development to continue overnight so the founder can return each morning to completed work, documented decisions, and clear next steps.

ABOUT GATHER

Gather is a community-building platform that helps people spend more time together without one person carrying all the work of planning.

The application supports groups, contacts, gatherings, activities, invitations, public share links, date and time voting, RSVPs, email and SMS notifications, calendar coordination, city discovery, and an AI-powered planning concierge.

From a development perspective, Gather includes:

  • Authenticated organizer, member, staff, and administrative experiences
  • Public invitation, voting, RSVP, and discovery pages
  • An AI-assisted conversational gathering-planning experience
  • Group, contact, activity, and gathering management
  • Transactional email , SMS, calendar, and notification workflows
  • Security-sensitive authentication, participant identity, privacy, and Row Level Security behavior
  • A growing domain layer with strict boundaries between UI, business logic, data access, and the AI concierge kernel

THE TECHNOLOGY

Gather is an end-to-end TypeScript application built with:

  • Next.js 16 using the App Router
  • React 19
  • TypeScript
  • Supabase for PostgreSQL, Auth, Storage, and Row Level Security
  • Tailwind CSS v4
  • shadcn/ui and Radix primitives
  • Vercel for preview and production deployments
  • Nitrosend for transactional and lifecycle email
  • Twilio for SMS
  • Anthropic/Claude for AI-powered product functionality
  • Sentry for monitoring
  • Google Calendar integrations
  • Stripe infrastructure for future billing
  • Vitest, Playwright, ESLint, TypeScript checks, and GitHub Actions for verification

The application uses Server Components by default, explicit data-access boundaries, domain-level business logic, database migrations, RLS policies, automated tests, preview deployments, and documented architectural decisions.

HOW THE APPLICATION HAS BEEN BUILT

Gather has been developed using an AI-assisted “vibe coding” workflow under the supervision of experienced full-stack developers.

This does not mean blindly accepting AI-generated code. Non-trivial work begins with investigation and a written plan. Security-sensitive and database changes receive additional scrutiny. Work is tested, reviewed, and verified before it is considered finished.

Claude Code is the primary development environment. We are specifically looking for someone who already uses AI coding agents well, or who is eager and technically capable enough to make Claude Code part of their daily engineering workflow.

You should use AI to accelerate:

  • Understanding unfamiliar code
  • Investigating bugs
  • Writing and reviewing implementation plans
  • Implementing scoped changes
  • Generating and improving tests
  • Reviewing diffs for missed cases
  • Documenting decisions
  • Preparing accurate end-of-shift handoffs

You must still understand and take responsibility for every change you propose.

OUR CURRENT DEVELOPMENT PACE

Gather moves quickly.

In the most recent 30-day period:

  • 382 pull requests were merged in GitHub
  • 215 Linear issues were completed
  • Those issues represented 431 estimated points
  • GitHub activity occurred on all 30 days
  • The median was 12 merged pull requests per day

These are workflow-level numbers, not a quota for one developer. They demonstrate the pace of an AI-assisted system built around small scopes, fast review loops, and detailed handoffs.

You need to be comfortable working in a codebase where multiple small changes may move through planning, implementation, testing, review, and deployment in the same day. Speed matters, but correctness, security, and honest verification matter more.

WHAT YOU WILL DO

  • Learn Gather’s product behavior and technical architecture deeply
  • Take ownership of clearly scoped Linear tickets
  • Investigate existing code, tests, documentation, and architectural decisions before making changes
  • Use Claude Code throughout planning, implementation, testing, and review
  • Build features across the Next.js, React, TypeScript, Supabase, and PostgreSQL stack
  • Write and review SQL migrations, database functions, and RLS policies when qualified
  • Create focused pull requests with clear explanations and verification evidence
  • Respond to automated and human review findings
  • Test your work and clearly distinguish what was verified from what was not
  • Keep Linear and GitHub up to date
  • Improve documentation when a discovery will prevent future mistakes
  • Identify ways to improve our development system

You will also help examine how we currently use GitHub and GitHub Actions. We want evidence-based recommendations that reduce our GitHub bill without weakening security, testing, or deployment safeguards.

Potential areas include duplicated CI work, unnecessary workflow runs, inefficient triggers, poor caching, excessive artifact retention, redundant review loops, and missing concurrency controls. Measure first, then propose changes. Do not remove important safeguards simply to reduce the bill.

ASYNCHRONOUS DECISION-MAKING

You cannot wait for the founder to answer every question.

When a question comes up during your shift, you should:

1. Document the question.
2. Check the ticket, architecture documentation, prior decisions, tests, and related code.
3. Identify the reasonable options.
4. Choose the safest reversible option when the existing product direction provides enough evidence.
5. Document what you d ---------- and why.
6. Explain any risks, assumptions, or alternatives.
7. Verify the result.

For irreversible product decisions, production data changes, security-sensitive uncertainty, or unclear requirements that could materially change the outcome, document the blocker and wait for direction rather than guessing.

END-OF-SHIFT HANDOFF

At the end of every shift, provide a concise written handoff containing:

  • What was completed
  • Linear ticket and GitHub pull request links
  • What tests and checks were run, with results
  • Questions that came up
  • Decisions you made and why
  • Assumptions, risks, or items that remain unverified
  • Anything needing founder input
  • The exact next recommended action

The founder should be able to start the next day, read your summary, understand what happened overnight, and continue without reconstructing your reasoning.

REQUIRED EXPERIENCE

  • Strong production experience with Next.js, React, and TypeScript
  • Experience with Supabase, PostgreSQL, Auth, SQL migrations, and Row Level Security
  • Strong Git and GitHub pull request skills
  • Experience with automated tests and CI/CD
  • Ability to understand a mature architecture rather than treating every ticket as an isolated code-generation task
  • Experience using Claude Code or another serious AI coding agent
  • Strong written English and asynchronous communication
  • Good security and data-integrity judgment
  • Ability to explain technical decisions clearly
  • Comfort taking ownership while knowing when to stop and ask

HELPFUL EXPERIENCE

  • Vercel and GitHub Actions
  • Tailwind CSS, shadcn/ui, or Radix
  • Twilio, transactional email , Sentry, Stripe, or calendar integrations
  • Consumer social, event-planning, community, or marketplace products
  • Measuring and reducing CI or GitHub Actions costs
  • Working in an AI-native engineering organization

TOOLS AND ACCESS

We will provide access to every account you need to perform the work, including GitHub, Linear, and the relevant development and infrastructure services.

We will also provide paid Claude Code access. You will not be expected to purchase Claude Code or use a personal account for company development. Claude Code is intended to be your primary development environment.

HOW TO APPLY

Please include:

1. Links to two relevant applications or repositories you worked on, especially Next.js or Supabase projects.
2. A short explanation of your specific contribution to each.
3. How you currently use Claude Code or another AI coding agent.
4. One example where you caught or corrected a mistake made by an AI coding tool.
5. An example of a technical decision you made without immediate access to a manager, and how you documented it.
6. One example of how you would investigate a high GitHub Actions bill.
7. Your normal working hours in Philippine time.
8. Your expected monthly salary in USD.

This role is a strong fit if you are a thoughtful full-stack developer who sees AI as an engineering multiplier, communicates clearly, verifies your work, and can keep a product moving while the rest of the team is offline.

It is not a fit if you paste AI-generated code without understanding it, wait for instructions at every small decision, or treat passing compilation as sufficient verification.

Track this external role

Sign in to save this listing and apply through the original source.

Sign in to SaveReport JobOpen Original Listing