Core competencies
Six competencies, in priority order. For each: what I do, the class of problems it solves, and where it is proven.
- 01
Solution & enterprise architecture
- What I do
- System boundaries, modules, data models, APIs and integration contracts — with the trade-offs written down as decision records.
- Typical problems
- Fragmented tools that need to become one coherent platform with its own source code.
- Proven in
- 02
Business & systems analysis
- What I do
- Interviews, AS-IS / TO-BE process maps, requirements and acceptance criteria, data audits.
- Typical problems
- Manual, cross-department work and data nobody trusts any more.
- Proven in
- 03
AI engineering & agentic systems
- What I do
- Agent pipelines (planner, coder, independent reviewer model — an LLM judge), private RAG, MCP tools, evaluation with thresholds fixed in advance, human approval before merge.
- Typical problems
- Delivering much more with a small team — without losing control over quality.
- Proven in
- 04
Technical leadership
- What I do
- Priorities and backlog, vendors and contractors, risks, launches and the operation that follows.
- Typical problems
- Programmes where several teams and suppliers must deliver one working result.
- Proven in
- 05
Systems integration
- What I do
- Bitrix24, 1C, EDI, warehouse and hardware: event queues, idempotency, reconciliation and safe clean-up of production data.
- Typical problems
- Integrations that silently lose, duplicate or block data.
- Proven in
- 06
Engineering depth
- What I do
- Linux infrastructure and monitoring, embedded and medical-device firmware — used when the problem sits below the application.
- Typical problems
- Faults that application teams cannot see: devices, networks, timing.
- Proven in