About Sadig Muradov

I’m Sadig Muradov — a software engineer and independent consultant working on applied AI, web platforms, and the connective tissue that turns prototypes into systems people actually rely on. I run my practice from Baku and ship for clients across Europe and the Caucasus.

What I work on

Most of my recent work sits at the intersection of three things: language models doing real work, Python/Django services that have to keep running, and PostgreSQL data that has to be reportable, auditable, and fast. I tend to get pulled in when a team has a working prototype but no production story, or a production system that’s outgrown the assumptions it was built on.

Concrete shapes the work has taken:

• LLM-powered systems — agents, retrieval pipelines, evaluation harnesses, and the boring scaffolding (queues, observability, prompt tests) that makes them shippable.
• Django + Postgres — schema design, ORM-friendly database views, migration strategy, query plans for reporting workloads.
• JavaScript / TypeScript — React frontends, Node services, browser automation, and small experiments at the edges of the platform.
• Workflow tooling — internal automations and integrations that compress days of manual work into minutes.

Services

If you’re considering a paid engagement — consulting, architecture review, code review, or focused training for engineering teams — I’m available for short, scoped pieces of work. I’m most useful when there’s a real system in play and a specific decision to make: what to build, what to rip out, what to teach the team. The fastest way to start that conversation is the contact page, where I keep an up-to-date note on what I’ll take on and what I won’t.

Writing and speaking

I write long-form notes when I’ve used something hard enough to have an opinion worth defending — usually Django, Postgres, applied AI, or the small JS experiments that didn’t fit anywhere else. I also speak at conferences, meetups, and internal trainings, mostly on AI engineering and how the craft of software is changing as agents take over more of the routine work. Recordings are linked from each talk where they exist.

Background

I came to engineering the long way around. I trained as an economist, drifted into design, and then realized the thing I actually liked was building the systems behind the screens. That detour is why I tend to obsess about how a system feels to the people using it and the people maintaining it — not just whether it works.

If you want a more chronological view of what I’ve been up to professionally, the LinkedIn profile is the canonical version.

Get in touch

Email is the fastest path — [email protected]. I read everything and reply slowly, but I do reply.