Business Analyst
Map how client businesses run, find the bottlenecks and turn them into the systems we build, from the first mapping call to launch.
What you will own in your first 90 days
Each outcome is something a client will have seen and used.
- 01Run the mapping sessions for one full diagnostic, and present the operating map to the client's owner and team.
- 02Own that client's ranked roadmap, with a value, an effort and an owner for every item, and defend what it leaves out.
- 03Lead one client's launch training and report what changed, as a before and an after with a base and a period.
The work is finding out how a business really runs, then making the fix stick
A typical engagement starts with an owner who says everything runs through them. Your job is to find out why. You run four or five mapping calls with the owner and their team, map how work really moves handoff by handoff, and agree with the client which problems are worth solving. Then you stay through the build until the team uses the system without calling the owner.
Most weeks you run two or three working sessions on video, turn what you heard into maps and roadmap items, and hold a weekly status call with each client. You review every prototype screen with the people who will use it, because adoption is decided in those reviews.
You work with the founder, the engineers and the client’s own people
You work with the founder, Mihkel Sinikas, and beside the engineers who build the systems, and you are their first reference on what the client needs. On the client side you work with owners of companies and with the people who do the daily work. Many clients are in the US, so some sessions run late in the European day.
Four traits decide whether you would do well here
- Trust on both sides of the business. You can earn the confidence of an owner and a front-line employee in the same afternoon.
- Plain writing. You can explain a process problem in five sentences that an owner would forward to their partner.
- Numbers with a base. You put a figure, a base and a period on every claim, and you say when you do not know.
- Follow-through. You measure success by whether the team uses the system a month after launch.
Four steps, and a reply within ten working days
Each step tests the work you would do here. Exercises over two hours are paid, and every rejection comes from a person.
- 01First call
We talk about the role, your experience and what you want to work on next.
- 02Practical exercise
A short, real task: map a process from a recorded interview, or build a small feature from a prototype screen. If it takes longer than two hours, we pay for your time.
- 03Case or technical interview
Business analysts work through a real, anonymized engagement. Engineers walk us through the exercise and a system they built.
- 04Founder conversation
A talk with Mihkel Sinikas about how you work and what you want from the role.
Apply for the business analyst role
- LocationRemote, global
- TypeFull-time
- ReplyWithin ten working days, from a person