Product Designer

EVERJUST is a software factory. We build software products and take them to market.

The design language already exists — Instrument Serif for display, Geist for body, near-black ink, one accent — but it is a short list of CSS variables living on the marketing pages. This role turns it into a system and applies it to the software: EVERJUST.APP, CustomAgents, Custom Domain, FaceSmash, and the products we build for clients inside their own repositories.

What you do

• Own the design system as a versioned artifact — tokens, type scale, spacing, states, light and dark — in the same repository as the code that consumes it, not in a file people copy from once.
• Design the interfaces for EVERJUST.APP, CustomAgents, Custom Domain and FaceSmash, and keep them recognisably related without making them identical.
• Draw the interaction while the architecture is being settled, before feature code exists, so the empty state, the error state and the loading state are decided rather than discovered.
• Design the Service Configurator checkout, where someone assembles a $9,650 storefront build and add-ons up to $27,650 and pays without speaking to anyone. The price is on the screen. The design has to carry the decision on its own.
• Make technical constraints legible in the interface. FaceSmash keeps biometrics in the browser; a user should understand that from the screen, not from a paragraph explaining it.
• Work in the client's own repository from the first commit, review built screens against the design, and file the difference as work rather than as a complaint.
• Decide in writing what the accent colour is for, so that six months and four products later it still means one thing.

What we look for

• Software you designed that shipped and that people used — a product surface, not a landing page or a rebrand deck.
• A design system you authored yourself in Figma, down to components, variants and variables, and an honest account of where it broke.
• You read front-end code well enough to tell whether a built component matches its spec, and to open a pull request changing a token yourself.
• Evidence you have designed the unglamorous screens: permissions, billing, failure, migration, the settings page nobody screenshots.
• Typographic judgement you can defend out loud — why this scale, why this measure, why this weight at this size.
• You treat a constraint from engineering as information about the problem rather than an obstacle to route around.

Nice to have

• You have run one design system across more than one product and know what breaks when the second product arrives.
• You have designed for software that acts on its own. A CustomAgent has its own email address, phone number and Slack profile; it does things while nobody is looking, and the interface still has to show what it did.
• Accessibility work you did because it was correct, not because an audit demanded it.
• You prototype in code well enough to test a motion or a state machine without asking anyone.

What it is like

The good part: nothing sits between your decision and the shipped screen. Architecture is settled before feature code is written, so you are in the room while the shape of the thing is still open, rather than handed a spec to decorate. Client work is built in the client's own cloud and repositories from the first commit and handed over by changing permissions, which means your files and your rationale have to be readable by whoever inherits them. Every price is printed on the site, so no one will ever ask you to design a page whose purpose is to hide one.

The hard part: the current design language was drawn for marketing pages, and product screens will find every place it does not hold — density, tables, long forms, states nobody drew. You will be changing work that is already live, in public, while four products keep shipping. The team is small and research and writing are not separate jobs here, so they are yours too, and some weeks the system work loses to whatever is due.

Not for you if

• You hand off a file and move on. Here you follow the design into the repository and check what actually got built, screen by screen.
• You want a research phase, a content partner and a design manager in place before you start. Design is not divided up that way here.
• Your strongest work is brand and marketing sites. That surface is largely settled; this job is software interfaces.
• Your best conversion ideas depend on hiding the price until a call. Prices are published and stay published.
• You would not take on a paid, time-boxed piece of real work from our backlog as part of hiring. That is step three, and it is how the decision gets made.