Davit Hayrapetyan PhD

Staff Software Engineer · Yerevan, Armenia

← Ask DAVO anything about this

Summary

Davit Hayrapetyan is a Staff Software Engineer and systems architect based in Yerevan, Armenia.

Davit specializes in distributed systems, microservices modernization, resilient architectures, cloud-native applications and enterprise integrations. He is architecture-first rather than language-first, and the range is delivered work rather than exposure: he has carried production systems to completion in Java, Kotlin, C++, Verilog, TypeScript and JavaScript, across silicon test tooling, government identity platforms, financial systems, e-commerce search and AI-backed developer tools. In each of those he worked at the level where a stack's own specifics matter — its failure modes, its concurrency and memory behaviour, its build and release tooling — rather than treating it as syntax over a familiar design. The JVM and Spring Boot are where he is deepest in high-load systems, observability and scalability; they are not the edge of his range. He has worked as a software engineer since September 2011.

Alongside hands-on engineering, Davit actively contributes to:

He combines deep technical expertise with strong communication skills, making him effective both as an engineer and as a technical leader capable of bridging business and engineering domains.

Outside traditional enterprise engineering, Davit is also deeply interested in:

Davit is also:

For more than a year his delivery has run through agentic development flows — Copilot and Codex, and for the last six months or more Claude Code as the primary tool — with his own time going into product delivery, resilience, testing, code review and verification rather than typing implementation. The practice itself is engineered: designed skills, work broken into units a session can finish and verify, and deliberate session scoping. The effect is reach — React, Angular and Go became deliverable because the binding constraint moved from syntax fluency to judgement about what to build and which failure modes matter.

Experience

  1. Staff Software Engineer — Grid Dynamics

    January 2025 – Present

    Raymond James Wealth Management Platform

    • Leading modernization of a mission-critical wealth-management platform
    • Transitioning legacy monoliths into resilient microservices
    • Designing observability and resiliency improvements
    • Integrating vendor APIs and enterprise systems
    • Establishing what the service level objectives actually are, by analysing production traffic and latency rather than inheriting a target
    • Thread and concurrency tuning to hold those objectives under peak load
    • Two-tier caching: an external Redis tier alongside in-process near-caches
    • Supporting architectural alignment between engineering, DevOps, DB, and product teams
    • Implemented resiliency patterns preventing cascading failures
    • Designed fallback strategies and observability improvements
    • Led integration analysis for third-party financial data providers
    • Service level objectives held, rather than a one-off benchmark: peaks of around 100,000 requests per minute, p50 latency around 40 ms, and p95 under 100 ms
    • Identified those objectives in the first place by analysing production traffic and latency distributions, so the targets describe what the platform is actually held to rather than a figure agreed in advance
    • Those targets were maintained while new data vendors were being onboarded continuously. The work was keeping them true as the system kept growing, not reaching them once
    • Optimized at every level rather than in one place: thread pools and concurrency, database access, parallelized calls to vendor APIs, and a two-tier cache combining an external Redis tier with in-process near-caches
    • Migrated a vendor integration on a separate service from Moody's legacy EDGE XML API to its REST API
    • Introduced local near-caches with resilient cluster-wide updating, so a node refresh never takes the cluster down with it
    • Worked directly with the data vendor to add delivery mechanisms beyond the request/response APIs — bulk files shipped daily outside business hours and processed ahead of demand — which took the largest data sets off the hot path entirely. This was as much coordination as engineering: agreeing the format and the schedule with the vendor, then implementing both ends.
    • Held full ownership of the platform on and off business hours, beginning during testing and delivery rather than after handover
    • Sole engineer on this work, reporting directly to the product owner

    Java 17 · Spring Boot · Redis · IBM MQ · OracleDB · OpenTelemetry · Splunk · Docker · Jenkins

  2. Principal Java Developer / Architect — jambit.am LLC

    March 2024 – January 2025

    Governmental Mobile Driver License Platform

    • Led development of a resilient microservices platform
    • Designed REST APIs and backend services
    • Developed Angular frontend modules
    • Managed AWS and Docker Swarm deployments
    • Worked on enrollment, encryption, and document workflows
    • Delivered as a pilot. The design, the analysis and the conformance work with EU policy were done in full; it did not carry production citizen volume
    • Owned the research, the backend implementation and the infrastructure
    • Worked alongside one mobile developer, with a product owner and a project manager

    Kotlin · Java 21 · Spring Boot · Angular · MongoDB · AWS · Docker Swarm

  3. Senior Java Developer — jambit.am LLC

    March 2023 – March 2024

    Automotive Material Verification

    • Led enterprise Java synchronization systems
    • Enhanced material verification workflows
    • Back-office Java software for a BMW project, handling vehicle composition and the legal and compliance questions attached to it
    • A monolith, and a maintenance engagement rather than a build

    Java EE · Payara · OracleDB · Azure · Swing · Angular

  4. Senior Software Engineer — Talkdesk

    July 2021 – October 2022

    Interactive Post-Survey Experience

    • Designed scalable omnichannel survey microservices
    • Proposed state-machine-driven orchestration flows
    • Researched workflow and state-machine solutions
    • Helped standardize orchestration architecture
    • Proposed Spring State Machine with state held in ElastiCache, after writing a comparison of the candidate solutions and their trade-offs
    • Led every stage through to production: development, testing and release. Infrastructure was AWS, run by the SRE team
    • Tech lead of a two-person team

    Java 16 · Spring Boot · Redis · Kafka · Docker · Jenkins

  5. Senior Software Engineer — Novanoweb Solutions

    August 2020 – July 2021

    • Led migration from relational databases to Elasticsearch
    • Optimized aggregation and search performance
    • Improved scalability of e-commerce systems
    • Aggregation queries that had been taking up to 5 seconds came down to around 300 ms
    • Consolidated several relational databases — MariaDB and PostgreSQL — behind a single Elasticsearch layer
    • A few gigabytes of catalogue and order records, across a number of online stores
    • Sole engineer on the migration, reporting directly to the company owner

    Java · Spring Boot · Elasticsearch · MariaDB · PostgreSQL

  6. Senior Software Engineer — Synopsys

    August 2015 – August 2020

    • Built the C++ and Qt desktop application used in semiconductor foundries, including TSMC, to test embedded memory designs before production and to analyse them after it
    • Programmed the memory chips' own on-chip test infrastructure, which has its own assembly language, to detect and repair memory faults
    • Modelled those memory faults in Verilog so a design could be exercised pre-production, before any silicon existed — the research half of the PhD, and the subject of the publications
    • Built one application against two back ends behind a single interface: the Verilog-emulated memory infrastructure, and the physical chip itself through a dedicated reader over a DVI port
    • Shipped it as production software in use across chip manufacturing, not as a research prototype
    • Worked independently on the research, reporting to the department lead

    C++ · QT · Verilog · Embedded assembly

  7. Senior Software Engineer — Inomma

    April 2015 – July 2015

    • Developed automated cloud-based competitor pricing scrapers

    Java · Spring Boot · AWS

  8. Software Engineer — Synergy International Systems

    September 2011 – April 2015

    • Enhanced CMS platforms for government organizations
    • Integrated web and desktop systems
    • Tech lead of a two-person team

    Java EE · JavaScript · jQuery · MySQL · Swing · JSP

Teaching

  1. Lecturer, Master's programme (part-time) — Yerevan State University

    2023 – 2026

    Development of Modern Mobile Applications

    • Taught development of modern mobile applications on the master's programme
    • Covered integration of AI into mobile applications from 2024 onwards, the same ground as his own AI-systems work
    • Set and assessed coursework, and supervised project work

  2. Lecturer, Bachelor's programme (part-time) — Russian-Armenian University (RAU)

    2019 – 2021

    • Taught x86 assembly, object-oriented programming, C++ and Java across different years of the bachelor's programme
    • Built and delivered the practical parts of those courses alongside full-time engineering work
    • Part-time throughout, held alongside a full-time engineering role

Skills

Languages
Java · Kotlin · C++ · TypeScript · JavaScript · SQL · Go · Python · Dart · Verilog · x86 Assembly
Systems and Low-Level
C++ · Qt · Verilog · x86 Assembly · Embedded assembly · Embedded memory test and repair · On-chip test infrastructure · Pre-silicon verification · Post-production silicon analysis · Virtual-hardware simulation · Hardware interfacing · Performance-sensitive software
Mobile
Flutter · Dart · Kotlin Multiplatform · Android · iOS · Offline-first and clean architecture
Backend Engineering
Java · Kotlin · Spring Boot · Java EE · Hibernate · Quarkus · REST APIs · Distributed Systems · Microservices
Performance and Reliability
SLO definition from production · Thread and concurrency tuning · Two-tier caching · Near-cache invalidation · Query optimization · Load and latency analysis · Resiliency patterns · Circuit breakers and fallbacks · Observability
Cloud & DevOps
AWS · Azure · Docker · Docker Swarm · CI/CD · Jenkins · OpenTelemetry · Splunk
Databases & Messaging
OracleDB · PostgreSQL · MongoDB · Redis · Elasticsearch · Kafka · IBM MQ
Frontend
Angular · TypeScript · React · Next.js (App Router) · Tailwind CSS · Progressive Web Apps · Server-Sent Events and streaming UIs
Leadership & Communication
System Design · Technical Leadership · Mentorship · Architecture Discussions · Stakeholder Communication · Developer Community Organization
AI & Emerging Technologies
AI Agents · RAG Systems · MCP (Model Context Protocol) · Spring AI · LLM orchestration, fallback chains and circuit breakers · Prompt design with schema-constrained output · OCR and LLM document parsing · AI-assisted Developer Tooling · Local LLM deployment and experimentation · Intelligent Automation

Education

Common questions

Is Davit Hayrapetyan authorised to work in the EU?
Armenian citizenship. Armenia is the only country where he currently holds standing work authorization - there is no EU, US, UK or Canadian permit in hand. That does not close the EU to him, and EU roles are actively wanted: either remote from Yerevan, which needs no permit and is usually done B2B or through an EOR, or on site with relocation and a sponsored permit arranged alongside the offer. The permit is a step in the process, not a reason to skip the role. No work permit outside Armenia today, the EU included. That is a gap to close together rather than a restriction on his side - he rules out no location, and for a role based anywhere outside Armenia the practical path is employer sponsorship or a work permit arranged alongside the offer, which he is glad to discuss. Eligibility is asked for and proved during recruitment, so nothing is claimed here that a document would not support.
Where is Davit Hayrapetyan based, and does he work remotely?
Asked where he would prefer to be based for a role, the answer is Yerevan, Armenia. The working arrangement is not a condition: office, hybrid or fully remote are all fine, whichever the role offers. Relocation is a separate question and is answered under contract_shape - it is open only for genuinely strong opportunities. Remote international work with European, EMEA, UK, US or globally distributed teams, where the role offers real technical scope, a modern backend stack, clear expectations and seniority alignment.
What roles is Davit Hayrapetyan looking for?
Davit is open to Staff, Principal and architect-level engineering roles - remote for international teams, or in Yerevan where the scope is right. Backend and distributed systems are his deepest ground, but the filter is the problem rather than the language: systems work, platform and developer tooling, and AI-backed products all fit. He is not urgently looking; the bar is scope, ownership and a modern stack rather than a title.
What is Davit Hayrapetyan's main technology stack?
Java 17+, Kotlin and Spring Boot - the priority. This is the stack with the most years behind it, and a role built on it outranks an equally senior one that is not. Rank JVM backend and platform work above everything else on this list; Microservices and service modernization; Distributed systems; Event-driven architecture. The full list is under Skills above.
How soon could Davit Hayrapetyan start?
One month's notice from an accepted offer.
What are Davit Hayrapetyan's salary expectations?
Davit does not publish compensation expectations on this site, and DAVO does not know them. Ask him directly — the contact links are on the page.
Is this site written by Davit Hayrapetyan PhD or generated?
The profile content is written and curated by him. The assistant on the site generates its answers at request time from those curated files, using a model on his own hardware first and a hosted one only as a fallback, and it shows which tier answered under every reply.