Have a project in mind?
Tell us what you are trying to do. We reply within two working days, with questions before a quote.
Careers
A small team in Dhaka building software on top of language models, writing about what it builds, and teaching others to do the same. We hire people who want to own their work from the first conversation to the running system.
Two ways in, one bar
Every application asks to see the work rather than list it. What differs is what the work is — and so what the form asks for.
Engineering
Show us a system.
- A repository you are proud of, and its hardest problem in three sentences
- An LLM-backed system you built: what it did, how you evaluated it, what broke in production
- Which parts of an agentic harness you have used in anger — skills, agents, hooks, memory, evals
- Your niche, and what it taught you that a generalist would miss
One conversation about that work, then a short paid exercise or a two-hour pairing session on a real harness from our repo.
Non-engineering
Show us the craft.
- Curators: a critique of one of our articles and three topic proposals with primary sources
- Coordinators: a one-page plan for a 30-person Saturday workshop, and your reply to a stranded participant
- Designers: your portfolio and the system behind one piece in 200 words
The application is the exercise. One conversation after it, then a decision.
Open roles
Engineering
How we hire
Four steps, two to three weeks, and an answer at every one of them.
Apply
The form takes 20 to 30 minutes and saves as you go. You get a reference and a confirmation by email.
Read and reply
Every application is read by the founder. Everyone hears back within five working days — yes or no, with a reason.
One conversation
45 minutes about the work you showed us. Engineers then do a short paid exercise or a pairing session; nobody else has a second round.
Decision
References, then an offer within a week. We agree the start date together.
Working here
What is true today, not what a careers page usually says.
Hybrid, from Gulshan-1
A desk in the office and remote days agreed per person. Programme roles are on site when there is an event.
AI tokens for everyone
Every role has a budgeted allowance for the models and tools it needs, engineering or not.
We write about what we build
The blog is part of the job, with a byline where it is earned; the workshops programme is the stage.
Own it end to end
Small team, no hand-offs into the void: the person who scopes a thing ships it and keeps it running.