Want to make your operations a priority this quarter?Book a call
Book a discovery call
Services, in the order we work
How we typically start working with companiesDays 1–7MapSee where your bottlenecks areDays 8–14PrototypeSee what your custom business system would look likeDay 14RoadmapGet a clear roadmap of what to fix and in what orderDay 14 onwardBuildBuild it with us, or in-houseThe timeline, the total cost and what you own at each stage
Case studies by industry
Featured case studies
Resources
Latest
Blog post · Oct 6, 2026Whether a new system streamlines your operations is decided before you build itResearch · Oct 1, 2026State of Operations 2027
Company
How we think
ManifestoWhether a new system streamlines your operations is decided before you build it.

Full-Stack Engineer

Build the systems client teams use every day, from a map and a prototype the client has already approved.

Apply for this role

What you will own in your first 90 days

Each outcome is something a client will have seen and used.

  1. 01
    Take one client feature from the approved prototype to production, on the client's own accounts, and see it used by their team.
  2. 02
    Build one integration with a tool a client keeps, such as an accounting system or a CRM, with logging and alerts when it fails.
  3. 03
    Turn a new client's prototype into its first working release, and join the business analyst for the launch training.

The work starts from a map and a prototype the client has already approved

You start from an operating map of the client’s business and a clickable prototype their team has already criticized. Your job is to turn that into a production system people use every day: role-based workspaces, job pipelines, client portals, dashboards and integrations with the tools the client keeps.

Most systems are web applications on a Postgres database (Supabase), hosted on Vercel in accounts the client owns. AI features use models from providers such as OpenAI and Anthropic, chosen task by task, and a person approves the output until it has proven accurate.

You work with the founder, the business analyst and the client’s own people

You work with the business analyst who mapped the client’s business and with the founder, Mihkel Sinikas. You talk to client staff directly during prototype reviews and launch training, because the people who use a system are the best testers it will have.

Four traits decide whether you would do well here

  • Judgment about what not to build. You can explain why a feature should wait, and back it with evidence.
  • Care for the person using the screen. You notice when a form asks for something nobody knows at that moment.
  • Reliable integrations. You assume the other system will fail, and you log and alert accordingly.
  • Clear handover. You write code and notes that another engineer, or the client’s own developer, can pick up.

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.

  1. 01
    30 minutesFirst call

    We talk about the role, your experience and what you want to work on next.

  2. 02
    About two hours, in your own timePractical 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.

  3. 03
    About 60 minutesCase or technical interview

    Business analysts work through a real, anonymized engagement. Engineers walk us through the exercise and a system they built.

  4. 04
    About 45 minutesFounder conversation

    A talk with Mihkel Sinikas about how you work and what you want from the role.

Apply for the full-stack engineer role

  • LocationRemote, global
  • TypeFull-time
  • ReplyWithin ten working days, from a person

One link we can open without signing in.

A person reads every application and replies within ten working days. See our privacy policy.