Careers Job Alerts

We're Hiring Soon

Our careers page is on its way. So are the roles.

We're growing the team this quarter across product, design, and engineering. Get on the list to hear about openings before they're posted.

Roles opening first

  • Senior Product DesignerDesignFull-time
  • Frontend EngineerEngineeringFull-time
  • Product ManagerProductFull-time
  • Community LeadGrowthPart-time
About this block

Careers Job AlertsPRO

A hiring coming-soon section with a centered square eyebrow and heading, a working job-alert email form, and a list of upcoming roles with team and employment type.

ComingSoon69: Careers Job Alerts

A Polaris hiring coming-soon section (single accent color, square eyebrow) that centers an eyebrow, a heading, and a description over a working job-alert email form, then lists upcoming roles with their team and employment type below.

Upgrade to Pro

Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.

Upgrade Now

Installation

Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.

Radix flavor

bash
npx shadcn add "https://ui.beste.co/r/comingsoon69?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

bash
npx shadcn add "https://ui.beste.co/r-base/comingsoon69?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/comingsoon69.tsx.

Quick start

The installed file exports comingsoon69Demo alongside the block: the exact props behind the preview above. Spread it to get a working job-alert page in one line.

tsx
import { ComingSoon69, comingsoon69Demo } from "@/components/beste/block/comingsoon69";

export default function Page() {
  return <ComingSoon69 {...comingsoon69Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

tsx
import { ComingSoon69 } from "@/components/beste/block/comingsoon69";

export default function Page() {
  return (
    <ComingSoon69
      label="We're Hiring Soon"
      heading="Our careers page is on its way. So are the roles."
      description="We're growing the team this quarter across product, design, and engineering."
      roles={[
        { title: "Senior Product Designer", team: "Design", type: "Full-time" },
        { title: "Frontend Engineer", team: "Engineering", type: "Full-time" },
        { title: "Product Manager", team: "Product", type: "Full-time" },
      ]}
      labels={{
        rolesTitle: "Roles opening first",
        placeholder: "Enter your email",
        success: "You're set. We'll email you the moment roles go live.",
      }}
    />
  );
}

Props

PropTypeDefaultDescription
labelstringSquare eyebrow rendered via Badge6
labelsComingSoon69Labels{}Roles title plus the form placeholder and success strings
headingstringSection heading
descriptionstringSupporting paragraph under the heading
rolesRoleItem[][]Upcoming role rows listed below the form
classNamestringExtra classes for the outer <section>
ts
type RoleItem = {
  title: string;
  team: string;
  type: string;
};

type ComingSoon69Labels = {
  rolesTitle?: string;
  placeholder?: string;
  success?: string;
};

Behavior notes

  • The job-alert form owns its email state; handleSubmit calls preventDefault and only flips to the success panel when the trimmed email is non-empty, so there is no external callback to wire.
  • On submit the form swaps for a bordered success capsule with a Check icon and the success string; the input is not restored without a reload.
  • The roles list renders only when roles is non-empty, each row a bordered card showing the title with the team and type joined by a small dot separator.
  • Every region is optional: the eyebrow, heading, description, and roles list each render only when their prop is present.
  • The header cluster and form are centered in a max-w-3xl column, and the roles list opens under a top border with its own centered caption.
  • No inline markup is parsed: every string renders as plain text, so HTML passed in shows as escaped text.

Wiring the form up

The form ships with local state and a success message but no backend, so submissions are not sent anywhere until you connect one. Point handleSubmit at your own route handler or email platform, or wire in a form library. For a walkthrough of the options, see React Hook Form, TanStack Form, and Formisch.

More Coming Soon blocks

View all Coming Soon
PRO

comingsoon22

Coming Soon Notify Page

A centered coming-soon launch page with a brand wordmark, a square eyebrow, an accent-highlighted heading, a working email notify form with a success state, a launch note, and a row of social links.

PRO

comingsoon57

Event Tickets Coming Soon

An event coming-soon section with a square eyebrow, an event name and heading, a date and venue meta row with icons, a working ticket-alert email form, and a speaker avatar row.

PRO

comingsoon15

Waitlist Coming Soon

A centered pre-launch section with an eyebrow, a large light heading, a paragraph, an image tile holding a working email-capture form with a success state, and a social-proof note.

PRO

comingsoon36

Countdown Clock Waitlist

A centered pre-launch section with a square eyebrow, an accent-highlighted heading, a large colon-separated live countdown clock, a working email-capture form with a success state, and an avatar social-proof row.

PRO

comingsoon54

Locked Product Preview

A two-column coming-soon section with a square eyebrow, a heading and a working email notify form, beside a browser-window mockup showing a blurred, lock-badged product preview.

PRO

comingsoon25

Launch Day Announcement

An editorial launch-date announcement with a square eyebrow, a kicker, an oversized date headline paired with a supporting note and a dark seal remind-me button, above a three-column ruled list of launch facts.