Careers

Build products that stay built

GateBuild is the app-building department of Arnica AI — the product that turns one sentence into a working app, website, agent or game, with its database, sign-in and hosting included. We are a small, remote-first team, and we hire slowly and on purpose.

Apply via Support

How we work

Four values run this team. They are not poster text — they are how work is assigned, reviewed and kept.

Ownership

If it has your name on it, it is yours end to end: the decision, the build, the check, and the fix when something is wrong. Nobody here waits to be told what their own work needs.

No red tape

Small team, short paths. The person doing the work talks directly to the person who needs it, and a good reason beats a long approval chain every time.

Ship and verify

Done means shown working, not announced. Every claim in this team comes with the thing itself — a live page, a passing test, a number that can be checked.

Compounding work

Every unit of work should become a durable asset: a template others start from, a capability the product keeps, a document the next person uses. Work that evaporates is work we redesign.

How hiring works

Four steps, in the open. There is no applicant portal on this internal build — applications come through the support route, and a human reads every one.

  1. Apply

    Send your application through the Support route: who you are, what you have built or run, and the role you are applying for.

  2. Conversation

    A real conversation with the team you would join — about your work, how you think, and what this role actually does day to day.

  3. Trial task

    A small, real piece of the job, done the way the job is done. It shows us your work and shows you ours — both directions matter.

  4. Offer

    If it fits both ways, you get an offer with its real terms in writing — role, work model and compensation, stated plainly.

Open roles

Roles are grouped by department. This internal test build carries the department structure and the posting format with two sample listings — real postings are published here with their real terms when a role opens.

Product

What gets built, in what order, and why.

Engineering

The platform, the engine and the infrastructure.

Design

Product design and the design system.

Marketing

Growth, content and the story told straight.

Customer Care

Support and success for builders.

Data

Measurement, analysis and reporting.

Operations

The machinery that keeps the holding running.

Sales

Partnerships and business development.

Content

Guides, docs and the blog.

Design · Sample listing — internal test build

Product Designer (Remote — US)

Own the look and feel of the builder and of the apps it produces: flows, components and the design tokens every generated app inherits. You would work with Product and Engineering from first sketch to shipped, verified interface.

Apply via Support
Customer Care · Sample listing — internal test build

Support Specialist (Remote — US)

Be the human a builder reaches when something blocks them: answer tickets, reproduce problems, route bugs to Engineering with evidence, and turn repeated questions into better docs.

Apply via Support

What every posting here contains

Every real role published on this page follows the same structure, so nothing important hides between postings:

Role summary

What the role is and where it sits in the team.

What you will do

The actual work, in plain language — no inflated titles.

What you bring

The experience and skills the work genuinely needs.

Work model

Where and how the role works — remote-first, stated per role.

Compensation & terms

Real postings carry their real terms at publication. This sample carries none, because inventing figures would make it fiction, not a template.

How to apply

Through the Support route, following the four steps above.

Working here, in plain terms

Remote-first

The team works remotely. What matters is the work and whether it can be verified, not where the chair is.

Products the holding owns

You build for products this holding owns and keeps — your work becomes part of an asset that stays, not a deliverable handed away and forgotten.

Small team, direct access

The team is small and the founders are reachable. Decisions are made by the people close to the work, and you will know exactly why yours shipped or changed.

Careers questions

How do I apply?

Through the Support route on this build: send who you are, what you have built or run, and the role you want. A human reads every application.

Are these sample listings real openings?

No — they are labelled samples that show the posting format on this internal test build. When a real role opens, it is published here with its real terms, and the sample label comes off.

Is the team fully remote?

Remote-first. Roles state their own location expectations in the posting itself; where a role needs a specific region, the posting says so.

What does the trial task involve?

A small, real piece of the role's actual work, scoped so it respects your time. It is how both sides see the fit before an offer — us seeing your work, you seeing ours.

Want to build the builder?

Tell us what you have built. That is the whole pitch.

Apply via Support