ABOUT
A professional path from direct implementation to back-end systems, automation, technical leadership, and independent consulting-with law and research developing in parallel.
My early work at PADC and Develandoo focused on responsive interfaces, client-side state, and API integration. It showed me how users experience a product-and how decisions made elsewhere in the system surface on the screen.
I became more interested in what sat behind the interface: where data came from, how business rules became software, how systems communicated, what happened when integrations failed, and how manual work could become a reliable workflow.
The shift was gradual rather than a clean change of discipline. Front-end and full-stack work taught me to see complete product flows; back-end engineering, databases, APIs, automation, and integration became where I took deeper responsibility.
01 - FROM FEATURES TO SYSTEMS
At ITMedia, my role moved from PHP and full-stack implementation into JavaScript team leadership and architecture decisions. At MFMsoft, I began by building internal automation workflows, then moved into end-to-end ownership of back-end services and integrations between external platforms and business operations.
Inside MFMsoft, that development is visible in three roles: Automation Engineer, Back-End & Automation Engineer, and now Back-End & Automation Technical Lead. The progression matters because the current role grew out of direct implementation experience with the same class of operational and integration problems.
The underlying question changed over time. It was first, “Can I implement this correctly?” It then became, “How should this system be designed, what can fail, how should its parts communicate, and will it remain reliable after deployment?”
02 - FROM IMPLEMENTATION TO OWNERSHIP
A meaningful part of my current work happens before code is written. I interpret requirements, challenge assumptions, define system boundaries, evaluate technical approaches, identify edge cases and risks, and turn the chosen direction into an implementation plan that a team can execute.
The responsibility continues through task breakdown, code review, solution validation, testing, production-readiness checks, release sign-off, documentation, and the operational behavior of the system after deployment. I remain hands-on with architecture and the parts of implementation where correctness or reliability is especially important.
I still treat this as engineering work. Some of its value lies in preventing an avoidable production problem before it exists.
The measure is not how much code is written, but whether the right system is designed, delivered, and ready to operate.
03 - INDEPENDENT TECHNICAL CONSULTING
Independent B2B work introduced a different kind of ownership. I had to begin with the business process itself: speak with stakeholders, clarify the requirement, identify system and integration boundaries, and turn an unclear problem into a practical route to delivery.
My first substantial independent engagement involved financial and back-office systems integration and automation. I was responsible for requirements analysis, system and data-flow mapping, solution and integration architecture, implementation planning, development, testing, documentation, and delivery.
Independent consulting is a growing part of my work. It requires the same problem-first responsibility seen across my broader engineering work: choosing the appropriate technical approach and carrying it through delivery without starting from a preferred framework.
04 - A SECOND PROFESSIONAL TRACK
I have been studying Law at the European University of Armenia since 2022 and expect to complete the degree in 2027. I am a law student, not a practicing lawyer, and I do not offer legal advice. This is developing as a genuine second professional track.
My research interests focus on how technology changes legal responsibility and regulation: AI governance, liability for agentic and automated systems, information-security regulation, and questions of authorship and originality raised by generative AI.
This direction is already active: I have two scientific publications touching on agentic AI liability and originality in the context of generative AI and higher education, alongside broader interests in AI and information-security regulation.
2scientific publications
Explore research →05 - WHERE THE TRACKS MEET
Technology, automation, and business already meet in my engineering and consulting work: systems have to be technically sound, operationally useful, and reliable in practice. Law is developing alongside that work as a separate track concerned with rules, responsibility, governance, and limits.
The longer-term direction is Technology × Automation × Business × Law. I am still developing that intersection, grounded in engineering work, consulting responsibility, legal education, and research.
EDUCATION
The degree covers legal theory, analysis, research, structured reasoning, and argumentation. My developing interests include technology law, AI governance, information-security regulation, and digital regulation.
An intensive program covering AI, machine learning, neural networks, data analysis, AI ethics, applied AI, and integration into real systems and workflows.