JOB TITLE: Full-Stack Developer (TypeScript / React / Node / Supabase), Part-Time, $10/hr SALARY FIELD: $800/month (20 h

READ THIS ENTIRE POST BEFORE APPLYING.

This post is direct on purpose. It saves your time and ours. Applications that ignore the instructions at the bottom will not be replied to. And to be upfront about the process: text answers don't get you hired here. A screen-share does. If you're not willing to show your real work, live, on camera, stop reading now.

ABOUT US
1 DASH ( ---------- ) is a US payments and merchant services company with 20+ years in the industry, serving businesses nationwide. Our stance with our customers is simple: "Running a business is hard. Your payments shouldn't be." The software behind that promise is what you'd be building: a payment and invoicing SaaS, an agent dashboard, a mobile app, and internal analysis tools. Our values are simplicity and transparency, in the product and in how we work. That's also why this post is blunt. Small dev team, zero bureaucracy, and the features you ship get used by real businesses to move real money.

THE STACK (THIS IS WHAT YOU'LL ACTUALLY WORK IN)
• TypeScript everywhere, strict mode
• Frontend: React 18/19, Next.js 15/16, Vite, Tailwind CSS, Radix UI, TanStack Query, React Hook Form, Zod
• Backend: Node 20, Express APIs
• Database: Supabase (Postgres + Auth), Drizzle ORM and Prisma
• Mobile: React Native / Expo with NativeWind and Zustand (nice to have, not required)
• Integrations: payment processor APIs (Valor, Dejavoo), OpenAI, Resend, webhooks
• Testing: Vitest, Playwright, Supertest
• Infra: Vercel, Railway, GitHub Actions, pnpm / Turbo monorepo

You do not need every item on this list. You do need to be genuinely strong in TypeScript, React, Node/Express, and
SQL/Postgres.

WHAT YOU'LL DO
• Build features end-to-end: database schema, API endpoint, UI
• Fix bugs without being babysat
• Write typed, Zod-validated code that passes lint, typecheck, and tests before you say "done"
• Work with payment APIs and webhooks. This is fintech, correctness matters more than speed.
• Use AI coding tools (Claude Code, Cursor, etc.) daily. We expect this. We don't care that you use AI, every good dev does now. We care whether you understand what it produces, and we will verify that live.

WHO THIS IS FOR
• Mid to senior level: around 3-5+ years of real, shipped work
• You can take a loosely defined task and come back with a working, tested feature
• You communicate proactively. Blocked means you communicate the same day, not three days later.
• You use AI tools heavily however, you can read, verify, and fix everything they produce. If you cannot explain your own code line-by-line on a call, please do not apply. You will be asked to.

Please DO NOT APPLY IF
• You're an agency or you plan to subcontract the work
• You need step-by-step instructions for every task
• You cannot explain code you've submitted without an AI tool open
• You will not record a Loom video or join a live screen-share call

PAY AND SCHEDULE
• $10 per hour. This is the rate.
• Part-time, around 20 hours per week to start. Can grow into more (and full-time) if you're good.
• Flexible schedule, long-term role.

THE HIRING PROCESS (SO YOU KNOW WHAT YOU'RE SIGNING UP FOR)
1. Application (instructions below)
2. 15-minute live screen-share call. You'll open your own code from the project in your Loom, and I'll ask you to walk through specific files, explain decisions, and reason through a change on the spot. I'll also show you a small snippet from your codebase and ask what it does and what's wrong with it. No prep needed if the work is actually yours.
Note on the call: AI tools must be closed during it. Not because we're anti-AI (you'll use Claude Code daily here) but because the call tests the one thing AI can't do for you: understanding.

HOW TO APPLY. FOLLOW THIS EXACTLY
Read carefully, because the first instruction is not where you expect it. Somewhere in this paragraph is your first filter: the first line of your application must be the word SHIPIT followed by the name of the database from our stack list above. Applications missing either are deleted unread. If you pasted this post into an AI tool and skimmed its summary, you've probably already failed.
1. Attach your resume, or include a Google Drive link set to "anyone with the link can view". A locked link counts as no resume.
2. Record a Loom video, 3-5 minutes. This is the core of your application. Requirements:
o Introduce yourself briefly on camera (face visible at the start)
o Say today's date and the word from your application's first line out loud
o Walk through ONE project you built. Show the actual code in your editor or the live app. No slideshows, no reading from a script.
o Open the git history or git blame on at least one file and show your commits
o Explain one hard problem you solved AND one design decision you'd make differently today
o Videos showing tutorial projects, cloned repos, or code you can't git-blame to yourself are an instant rejection
3. Answer ALL of the questions below, numbered. Skipped questions = deleted application. Keep answers SHORT, 2-3 sentences each. We can tell the difference between concise-because-you-know and long-because-AI-padded.

QUESTIONS: EXPERIENCE (links over stories, everything you claim should be checkable)
1. Years of professional experience, and the biggest thing you've shipped that is live right now. A link is required: live URL, App Store listing, or public repo. "I can't link anything" needs a one-sentence explanation (NDA, internal tool, etc.) plus the closest verifiable substitute.
2. Rate yourself 1-10 on each (be honest, the live call and test task will verify): TypeScript, React/Next.js, Node/Express, Postgres/SQL, Supabase.
3. One feature you built end-to-end, database to API to UI. Link the live feature, repo, or PR/commit range, and tell me which parts you personally wrote.
4. Have you worked with payments, fintech, or third-party API webhooks? One concrete example with specifics (which processor/API, what you handled).
5. GitHub or portfolio link. If your GitHub is empty, link whatever you HAVE built instead.

QUESTIONS: AI WORKFLOW
6. Which AI coding tools do you use daily and for how long? Then in 2-3 sentences: your last real task with one, what it got wrong, and what you fixed manually. (This gets verified on the call, so be accurate, not impressive.)

QUESTIONS: AVAILABILITY
7. How many hours per week are you actually available, and in what timezone?
Generic copy-paste cover letters will be deleted. AI-polished applications might slip past me here, but they do not survive the screen-share, so you're only wasting your own time. Only shortlisted applicants will hear back from us. If you followed everything above, you are already ahead of 90% of applicants.