Skip to content

About Me

Backend & Systems Engineer with VLSI roots

I started in microelectronics — my first degree is in Electronic Means at the National Polytechnic University of Armenia, with a parallel VLSI Design bachelor at Synopsys Armenia. That low-level grounding (C/C++, embedded, computer architecture) is the reason I'm comfortable now with C/C++ core business logic at QDSC and teaching OOP-in-C++ at university.

On top of that I've spent 7+ years shipping production code: C# / .NET trading services, Angular and React frontends for cryptographic and fintech platforms, and full-stack work with Python/Django. I treat the stack as one continuous system — there's no "frontend problem" that doesn't bottom out somewhere in memory layout, network behaviour, or contention on a backend resource.

Based in Yerevan, Armenia · Open to remote.

Portrait of Davit Yedigaryan

Education

Université Paul Sabatier Toulouse III · 2017 logo

Université Paul Sabatier Toulouse III · 2017

Master's in Computer Science (Aerospace)

Computer-science fundamentals applied to aerospace: algorithms, data structures, OOP, networked systems.

Armenian National Academy of Sciences · 2017 logo

Armenian National Academy of Sciences · 2017

Master's in Computer Science / Information Technology

Software engineering and data analysis.

Systems foundationNational Polytechnic University of Armenia · 2013 logo

National Polytechnic University of Armenia · 2013

Bachelor's in Electronic Means (C/C++, Embedded Systems)

Low-level computing foundation: C/C++, embedded systems, computer architecture — the systems-level grounding behind my current C/C++ work at QDSC.

Systems foundationSynopsys Armenia Educational Department · 2013 logo

Synopsys Armenia Educational Department · 2013

Bachelor's in Microelectronics & VLSI Design

VLSI design, hardware engineering, and embedded systems.

Vineti Armenia · 2018 logo

Vineti Armenia · 2018

Certified Frontend Development

Web development and quality assurance.

How I work

Read the code, not the docs

When something breaks at QDSC the answer is in a C++ source file, not a wiki page. I default to reading source — including the runtime, the compiler output, the Angular framework code — before guessing.

One stack, top to bottom

A "frontend bug" is often a network bug, a memory bug, or a backend race. I treat C++/C#/TypeScript as one system, which is what made the trading platform's low-latency UX possible.

Teach what I ship

I teach OOP-in-C++ and Computer Networks at university and IB-level CS. Forcing yourself to explain templates, RAII, or OSPF to first-year students keeps your fundamentals honest.

Looking for the technical timeline?

Month-by-month roles, stacks, and outcomes.

See experience →