03About me
I'm Mher —an engineer who likes the whole picture.
Based in Yerevan. More than ten years of building software — and years of shipping products where the backend, the apps and the business rules all have to agree with each other.
Story
From one portal to platforms used every day.
I've been building for the web for more than ten years. The oldest commit in the repositories I still maintain is from December 2020, on the backend of a national investment portal — paid listings, payments, moderation, emails. It's a good example of what years of practice teach you: software is a chain of promises: if a company pays, the listing must publish, and expire, and notify, on time, every time.
From there the systems grew. A merch shop and a LiveOps console for a mobile game. An agency website rebuilt from scratch. Then the platforms that became my main work: a restaurant chain's ordering system with a promotion engine that always finds the customer's best price, an online store synchronised with accounting and fiscal receipts, a gym chain's CRM, and a multi-tenant POS SaaS that keeps cafés selling even when the internet is down.
Along the way I started turning repeated work into reusable packages, and repeated mistakes into rules. Today I lead products end-to-end — architecture, backend, web, mobile — and I build the tooling, including AI agents, that lets a small team move fast without breaking things.
- Years of building software
- 10+
- Commits — about half of my team's total
- 7,100+
- Repositories where I'm the top contributor
- 11
- Payment providers integrated
- 9+
02How I think
Principles I don't negotiate on.
Correct before clever
Money, orders and permissions must be right every time. I design for the edge cases first — retries, offline, double clicks, wrong tenants.
One source of truth
Rules live in one place: one API for web and mobile, one design-token system, one promotion engine. Duplicates drift.
Small, reviewed steps
Short increments with clear acceptance criteria beat big-bang releases. Everyone sees progress; nobody gets surprised.
Make it simple to use
Complex systems should feel obvious — to the customer, to the cashier, and to the next developer who opens the code.
AI-assisted engineering
I build the workflow, not just the code.
On my recent products I set up AI agents as part of the engineering process — with the same rigour as code. The result: a two-person team shipping a 181-model platform in four months, without lowering the bar.
- Project rulebooks (CLAUDE.md) with design tokens, breakpoints and architecture rules
- Planner → implementer → reviewer agent pipelines with acceptance criteria
- Browser-verify and Figma pixel-check agents that look at the real result
- Post-edit hooks that type-check, lint and verify translations on every change
04Skills
The tools I use to build.
Frontend
Interfaces that feel fast and clear.
- React
- Next.js
- TypeScript
- JavaScript
- styled-components
- Tailwind CSS
- GSAP
- Three.js
Backend & data
Reliable logic, APIs and storage.
- Laravel
- PHP
- Node.js
- NestJS
- Prisma
- MySQL
- PostgreSQL
- Redis
Mobile & desktop
Apps for every screen.
- React Native
- iOS
- Android
- Firebase
- Zustand
- Electron
Infrastructure & tooling
Shipping and running in production.
- Docker
- Linux
- Nginx
- Cloudflare
- Git
- CI/CD
Have a product in mind?Let's build it.
Tell me about your idea, your product or your team. I usually reply within one working day.