Careers Remote by default

Do the whole job, not a slice of it.

Rotation through the layers.

Work across the whole arc of an initiative, from technical discovery to the specification a client team builds from, on client work and on WildHire, with people who own what they ship.

Most engineering jobs hand you one layer and ask you to stay in it. Here the work moves: a client prototype one month, the pipeline that ships it the next, a WildHire service after that. It is harder than specializing, and it is the fastest way we know to become the engineer other engineers ask for help. The team is small and senior, so your work is visible, your decisions are real, and there is nowhere to hide mediocre output, including ours. Both roles open right now are internships, and they are real ones — you will be writing code that other people depend on.

What working here includes

Work that reaches someone.

Interns here are not given a sandbox project to keep them busy. You work on the prototypes clients are waiting on and on WildHire, and your code goes out with everyone else’s.

Remote by default.

Work from wherever you work best. We ask for enough overlap with our hours to pair on the hard parts, not for a fixed desk.

Seniors within reach.

The team is small, so you are never more than a message from whoever made the decision you are reading. Asking is expected. Guessing quietly is not.

Learning counts as work.

Time spent reading the docs properly, or understanding why the last approach failed, is part of the job here rather than something you catch up on afterwards.

Feedback you can act on.

Specific, written, and often — on the code and on how you are working. You will know where you stand without having to ask.

Terms in writing first.

Hours, length, what you are paid and what you own are all agreed in writing before your first day. Nothing about your arrangement gets settled after you have started.

No package to oversell.

We are a young company, so there is no health plan and no benefits brochure. What there is: real engineering problems, people who will teach you, and a reference that means something.

→

See open roles

Or send a general application below. We read every one.

Open roles

Go developer intern

Platform · Remote · Internship

Write Go services behind our prototypes and WildHire — HTTP APIs, background workers and the glue that holds a proof of concept together while it is still changing shape every week.

You can write and read Go on your own: structs, interfaces, goroutines and channels, and you know when not to reach for a goroutine.
You have built something with an HTTP API and a database behind it, however small, and can walk us through why it is put together the way it is.
You are comfortable with Git day to day — branches, rebases, resolving your own conflicts — and you write commit messages someone else can follow.
You can read an error, a stack trace or a log line and form a theory before asking. Asking early after that is encouraged, not penalised.
You write tests for the parts that would hurt to get wrong, and you can say which parts those are.
Any exposure to Docker, SQL or a cloud provider is a bonus, not a requirement — we will teach the rest.
Remote, and you can overlap with our working hours often enough to pair when it matters.

Svelte frontend developer intern

Product · Remote · Internship

Build the interfaces clients actually click through — prototype front ends and WildHire screens in SvelteKit, from the first rough version to something that holds up in a demo.

You are fluent in JavaScript or TypeScript and have built real things with a component framework. Svelte specifically is a plus; if you know React or Vue well, you will pick it up.
You write HTML and CSS by hand and understand the layout you are producing — flexbox and grid, not a framework you cannot see through.
You care that a page works with a keyboard and a screen reader, and you know what a label and a focus state are for.
You have made something responsive that holds together on a phone, not just at desktop width.
You are comfortable with Git day to day and can keep your own branch tidy.
You can take a rough design or a sketch and make sensible calls on the details that were never specified.
Familiarity with SvelteKit, TypeScript or a design system is a bonus; we will teach the rest.
Remote, and you can overlap with our working hours often enough to pair when it matters.

How hiring works

Pick the role.

Choose the opening you are applying for, or send a general application if neither fits what you do. Tell us which languages you actually reach for.

Show us real work.

Link a repository, something you built, a writeup or a talk. It does not have to be finished or impressive. Two paragraphs about a hard decision you made beats any cover letter.

Upload your CV and send.

PDF or Word, up to 10MB. A human reads every application, and we aim to come back to you within a week either way. From there it is usually two conversations, one technical and one about how you work, then a decision.