Melkon Hovhannisyan

Most of Melkon's work sits at the boundary between engineering and product. He is not purely an infrastructure engineer, and not purely a product manager. He understands both, which means he can make decisions that are technically sound and commercially relevant at the same time. That is where most of the value is in early-stage and high-growth environments.

His engineering philosophy is biased toward reliability and clarity over cleverness. Systems should be easy to understand, easy to debug, and easy to hand off. He avoids premature abstraction and prefers direct solutions that match the actual problem. A system that does the right thing slowly and predictably is almost always better than a fast one that fails in unexpected ways.

On the AI side, Melkon focuses on production-grade agentic systems — not demos. He designs workflows that integrate LLMs into real business processes with proper error handling, observability, and fallback logic. He is skeptical of complexity for its own sake and evaluates tools based on outcomes, not novelty.

As a CTO and tech lead, he prioritises clarity of direction over volume of output. Engineering teams slow down when context is unclear. Clear requirements, early technical alignment, and honest progress tracking have more impact than adding headcount or tooling. He has built teams from early hires to 20+ engineers and learned which problems are people problems and which are engineering problems — they are not always the same.

Outside of software, Melkon has worked in international tech competition, represented Armenia at WorldSkills, and spent time in environments from Yerevan to Seoul to Barcelona. That mix of backgrounds shapes how he approaches problems: with curiosity, directness, and a preference for practical results over theoretical frameworks.

He documents things he builds publicly when they are genuinely useful to others. The two-Claude-accounts guide on this site is an example — a real workflow problem, solved, written down clearly so others can replicate it. That approach to sharing reflects how he thinks about engineering knowledge: it should be transferable, not locked up in a specific team or organisation.

Melkon is currently based in Barcelona, Spain. He consults for technical teams, advises early-stage founders on architecture and execution, and builds products in the AI and software space. He is reachable for consulting engagements, senior engineering partnerships, technical advisory roles, and press or podcast conversations on software, AI, and startup strategy.