Muhamed Isabegovic Get in touch

Services

Four ways to work together. Each starts from your code and how your team actually works, not from a slide deck.

Build

When you need a product or feature built.

Hands-on product engineering

Embedded, part-time or full-time

I join your team as a senior engineer and build the product or feature end to end, from spec to production.

What you get

  • A senior engineer who owns the work from spec to production, without a full-time hire.
  • Features built the way your codebase already works, with tests and a clean hand-over.
  • AI features where they help your product: grounded in your data, with structured outputs and evals.

Lead

When your team needs technical direction.

Technical lead for your team

Part-time or full-time

I lead your engineering team, part-time or full-time: technical direction, architecture, delivery, and the people.

What you get

  • Technical direction and architecture decisions, written down so the team can follow them.
  • Delivery that holds: planning, priorities and unblocking, together with product.
  • Support for your engineers, and help hiring the people you need next.

Review

When you want to know where your system stands.

Architecture review

Fixed scope, one to two weeks

A short, fixed-scope look at your codebase and system: what holds, what will break, and what to fix first.

What you get

  • A read of your codebase, your architecture and how your team works with it.
  • What holds, what will break as you grow, and where the risk sits.
  • A prioritised plan for what to fix first, which your team can act on.

AI-native

When you want your company to build with AI.

Make your company AI-native

Workshops, then setup in your codebase

How you build and what you build. I set up a knowledge base your people and agents work from, with architecture rules checked in CI, and build AI features into your product that hold up in production, using open-source tools I build and teach.

What you get

  • A knowledge base your people and agents both work from: specs, decisions and architecture rules, across your whole development lifecycle.
  • Coding agents set up for your codebase, with guardrails they cannot bypass and architecture rules checked in CI.
  • AI features in your product that hold up in production: grounded in your data, with structured outputs, evals and observability.
  • Set up with open-source tools I build (brain, pi-brain, enola and its gems, and tabula, in private development) and taught to your team, with enola-guides as the reference.

Your team ends up with a working setup in its own repositories, and knows how to keep it running.

How it works.

  1. Get in touchA few lines about your team and what you are trying to do.
  2. A short callWe talk it through, and I tell you honestly whether I can help.
  3. A scoped proposalClear deliverables, a format and a timeline, in writing.
  4. The workI get to work, and keep you posted on what changed and what is next.

I work remotely from Vienna, and on site across the DACH region.

Why me.

  • I build and I lead. I have shipped products hands-on, and led teams from 10 engineers to around 30 across 7 time zones.
  • I build the tools I teach with. I wrote brain and pi-brain, contributed the constraints program to enola and maintain four gems around it, so the setup in your repository is one I have built and run.
  • I ship AI features, not only advice about them. Retrieval, structured outputs and evaluation are things I have built, in production and for a regulated hiring context.
See the work behind this
Muhamed leads by doing. When we hit a hard problem, he didn't start with a long discussion. He wrote the code, showed it working, and then we talked. That habit moved the team forward more than once.

Zlatko AlomerovicWorked with Muhamed at Recrubo/Carv

Tell me what you are trying to do.

A few lines is enough. I will tell you honestly whether I can help, and how.

Get in touch info@muhamed.at