Before you write a single prompt, answer three questions:

1. Who are the employers? (What kind of companies post jobs here?)
2. Who are the job seekers? (What makes this audience specific enough to charge for?)
3. What will you charge for a featured listing? ($99, $199, or $299 — pick one before you build)

The niche determines everything else. A board for "remote Python engineers" implies different filters, different company profiles, and different marketing than "NYC fintech operations roles."

Write your one-sentence positioning before you open Blink:

"A job board for [specific job seekers] looking for [specific role type] at [specific company type]."

Open Blink and start with this prompt:

"Build me a job board with: a jobs table (title, company name, description, location, job type, salary range, apply URL, featured flag, posted date), a companies table (name, logo URL, website, description), a public jobs listing page with search by keyword and filters for job type (remote/hybrid/onsite) and location, and an employer admin panel where companies can submit new job listings. Include user auth for employers."

Blink creates the database schema, the API layer, and the initial UI in one pass. With Blink, the database is handled automatically — no SQL migrations to write, no Supabase project to configure.

The public listing page is what job seekers see. It needs:

• A search bar (keyword matches title and description)
• Filters: job type, location, salary range
• A clean card layout showing title, company, location, and type
• A "Featured" badge for paid listings — these appear first

Tell Blink: "Add salary range filter and a Featured badge that highlights premium listings at the top of search results."

With Blink, the frontend and backend connect automatically. No API routes to wire up manually.

Employers need to manage their own listings. The admin panel handles:

• Submit a new job listing (form with all required fields)
• Edit an existing listing
• Delete a listing
• View listing performance (views, clicks)

Tell Blink: "Create an employer dashboard where logged-in users can submit, edit, and delete their job listings. Show view counts per listing."

Auth is built in — employers sign up, verify their email, and access only their own listings.

Featured listings are how job boards make real money. A featured listing appears at the top, highlighted, for a fixed fee.

Stripe is the standard integration. Tell Blink:

"Add a payment flow for featured listings using Stripe. When an employer marks a listing as featured during submission, redirect to a Stripe checkout for $199. After payment confirmation, set the featured flag to true and surface the listing at the top of results."

Blink's API layer handles the Stripe webhook and updates the database automatically after payment.

Every job listing should have its own indexable page at a clean URL. Google indexes these pages, and organic traffic compounds over time.

Tell Blink: "Create individual job pages at /jobs/[slug] where slug is auto-generated from the job title and company name. Include the full job description, an Apply button linking to the apply URL, and structured data markup for job postings."

With Blink, routing and server-side rendering are handled automatically — no Next.js config or Vercel deployment to manage.

Most of the core functionality — listings, search, employer panel, auth — takes 4–8 hours with Blink. Adding Stripe for featured listings takes another 1–2 hours. A full-featured board with custom domain can go live in a single day.

No. Blink generates the full-stack app — database, backend API, auth, and frontend — from natural language prompts. You describe what you need; Blink builds it. If you want to customize beyond what the prompt produces, Blink lets you edit the generated code directly.

Yes. You have two options: redirect applicants to the company's own ATS (Greenhouse, Lever, Workable) via an apply URL, or build a native application form that collects resumes and notifies the employer. For a v1, the redirect approach is faster. Native applications add complexity but give you data to offer employers as a premium feature.

Three channels that work for niche boards: (1) Post in communities where your target job seekers gather — Slack groups, Discord servers, subreddits, newsletters. (2) Reach out directly to 10–20 employers in your niche and offer a free first listing. (3) Individual job pages at /jobs/[slug] get indexed by Google and drive long-tail organic traffic that compounds over months.

You start free. There are no separate Supabase, Vercel, or Clerk bills. As your board grows, Stripe takes 2.9% + $0.30 per featured listing transaction. A board making $3K/month in featured listings pays about $90 in Stripe fees — versus $70–130/month in infrastructure costs on a manual stack.

Yes. Tell Blink: "Add a job alert signup where job seekers enter their email and select preferences (job type, location). Send a weekly digest of new matching listings." You'll need to connect an email service like Resend or SendGrid, but Blink handles the subscription logic and database schema automatically.