Written first
Proposals, decisions and post-incident notes are documents. Meetings exist to resolve what a document could not, which is far fewer meetings than you are used to.
// careers
A small team, working on a hard, useful problem
We are building product analytics that small teams can trust without hiring an analyst. That means correctness work, latency work and a lot of care about what a number means — and a handful of people who each own a real surface.
// how we work
What it is actually like
We are a small distributed team. That is a real constraint, not a perk: you will own more surface than you would elsewhere, and there is nobody to hand the unglamorous half to.
Ship weekly
Something user-visible goes out most weeks. Long branches are a smell; if a change cannot be split into shippable pieces, that is the first problem to solve.
No on-call theatre
There is a rota, and it is quiet by design, because the ingestion path is the thing we invest most in keeping boring. Being woken up is treated as a bug in the system, not a badge.
Everyone talks to users
Engineers and designers take a turn in the support queue. It is the cheapest research there is and it changes what you build next.
Distributed, with overlap
Fully remote inside a stated timezone band per role, with a few hours of daily overlap. We do not pretend asynchronous means never being available at the same time.
Time off that is actually taken
A stated minimum rather than an unlimited policy nobody uses, plus local public holidays and a genuinely quiet week at the end of December.
Being straight about the trade-offs: we are early, the roadmap moves, and some weeks are support-heavy. If you want a large, settled organisation with a specialised remit, this is not that.
// open roles
Nothing open right now
We are not hiring at the moment, and we would rather say so than leave a list up that goes nowhere. When that changes, the roles will appear here first.
// hiring process
What happens after you email us
Five steps, about three weeks end to end if diaries cooperate. We will tell you where you are in it at every point, and we do not ghost people.
Application reply within 5 working days
Email us with whatever makes the case — a CV, a repository, a written piece, a product you shipped. No cover letter template, no form with eleven required fields. Tell us which role and what drew you to it.
Intro conversation 45 minutes
A conversation about your work and about ours, with the person who would work with you most closely. You will get real answers about stage, funding position and what is hard here; we would rather you self-select out early than late.
Practical exercise 2 hours, paid
A scoped, realistic problem — a small feature, a query to make fast, a flow to design, a support thread to answer. We pay for your time at a fair rate. If you would rather walk us through something you already built instead, that is an equally good option.
Deep dive 90 minutes
We go through the exercise or your prior work together, then dig into a domain problem: how you would design an event schema, debug a latency regression, or decide what a screen leaves out. Collaborative, not a quiz.
Decision and references within a week
Two reference conversations of your choosing, an offer with the numbers written down, and a clear answer either way. Everyone who reaches the exercise stage gets specific feedback, not a template.
Accommodations of any kind — timing, format, a different exercise — are available on request and will never count against you. Just say so in your first email.
// before you apply
Have a look at what you would be working on
The fastest way to work out whether you would enjoy this is to use the thing. Read how the product fits together on the product overview, skim the quickstart, and read a couple of posts on the blog — they are a fair sample of how we think and write.
If you disagree with something we published, say so in your application. That is a genuinely good opening.
Practical details
- Location
- Fully remote, within the band stated per role
- Equity
- Offered on every full-time role, numbers in writing
- Equipment
- Machine of your choice plus a desk budget
- Interviews
- Five steps, roughly three weeks, exercise paid
- Applications
- careers@alitycs.com
Compensation bands are shared in the first conversation, before we ask you to spend time on an exercise.
Tell us what you want to own
One email, no form. Name the role, or describe the one you think we are missing.
Every application gets a reply, usually within five working days.