Gagik Yeranosyan — Senior Software Engineer

I build software
that removes
manual work.

I'm Gagik Yeranosyan, a Senior Software Engineer with 6+ years of experience. I design and ship full-stack web applications for fintech, healthcare, industrial, and robotics teams — from the interface people use every day down to the services behind it.

  • Vancouver, BC, Canada
  • Full-stack web development
  • Open to work
Start a conversationView experience

6+

Years shipping production software

5

Companies across four industries

$380B

Annual volume on a platform I built for

4

Professional certifications

Six problems I get
hired to fix.

The first three started as a business cost — slow quotes, long support calls, or a team that could not ship confidently. The last three are the ones that cause the first three: requirements nobody confirmed, work nobody owns, and teams that only talk through tickets.

In the product

Manual process

Turning manual process into product

Quoting, approvals, and reporting workflows that still live in PDFs and spreadsheets get rebuilt as interactive applications. At Wasserstrom that meant replacing a 100-page PDF quoting workflow with a web application used by customers, account managers, and administrators.

100pages

PDF workflow replaced

Complex data

Making complex data usable under pressure

Support agents, clinicians, and field teams work against the clock. I design the data layer and the interface together — a Backend-for-Frontend over GraphQL, then dashboards and wizards that put the right number in front of the right person.

60%

Lower call handling time

Team velocity

Leaving teams faster than I found them

Shared component libraries, technical documentation, and a test suite people trust. I have led onboarding for engineering teams and raised coverage to the point where releases stop being an event.

50%

Faster engineer onboarding

In the team

Unclear requirements

Confirming the requirement before writing the code

Most rework starts with a ticket that two people read differently. Before I open an editor I run the discovery conversation, write the requirement back in my own words, and get that version confirmed — edge cases included. At Wasserstrom I do this as the primary technical contact with the AutoQuote Revalize team, turning business requests into specifications the whole team can build against.

  • Discovery sessions
  • Written specs
  • Acceptance criteria

Unowned work

Owning the outcome, not the ticket

A task is not done when the pull request merges; it is done when the feature works in production for the person who asked for it. I follow my work through review, release, and first real use, and I pick up what is blocking the release instead of waiting to be assigned it — environment configuration, authentication, and CI/CD pipelines have all become mine that way.

  • Owned through release
  • Blockers raised early
  • CI/CD and environments

Team handoffs

Keeping engineering, product, and vendors talking

Delivery slows at the seams — between frontend and backend, between a product team and an external vendor, between the engineer who wrote something and the one who now maintains it. I keep those exchanges short, written down, and open to everyone who needs them, and I make time for teammates: I led onboarding for seven engineers with documentation and training sessions that halved ramp-up.

  • Cross-team updates
  • Onboarding and mentoring
  • Documentation people reuse

Numbers from
shipped work.

Each figure comes from a production engagement and was measured after release, not estimated during planning.

Marqeta / Uber

60%

Lower call handling time

Cardholder Support Portal

Marqeta / Uber

80%

Test coverage reached

Jest and SonarQube enforcement

Marqeta / Uber

50%

Faster engineer onboarding

Documentation and training for 7 engineers

Finning / Caterpillar

40%

Fewer support requests

Contextual errors and self-service feedback

Built with the team, not beside it.

Engineering decisions land better when product, design, and business are in the room for them.

I develop modern, high-performing web applications and work closely with product managers, designers, business stakeholders, and fellow engineers to deliver seamless digital experiences, while helping drive engineering best practices across the organization.

I work alongside product managers, designers, and business stakeholders from requirements through release, so what ships matches what was actually needed.

I take part in architectural discussions and frontend design decisions, weighing state management, data flow, and component boundaries before code gets written.

Shared component libraries, technical documentation, code review, and test coverage — the practices that let a team keep moving after I hand the work over.

Projects.

Personal builds where I owned the data model, the services, and the interface.

Healthcare

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

Patients register, book, and manage appointments while administrators schedule, confirm, and cancel them. Appointment updates are delivered by SMS, with runtime errors tracked in Sentry.

HealthPro

Next.js · TypeScript · Twilio · Appwrite · Sentry

Real-time video

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

A conferencing application for creating rooms, scheduling meetings, sharing invitation links, and saving recordings. Clerk handles authentication and user management, including GitHub and Google sign-in.

Meeting

Next.js · TypeScript · Clerk · Video SDK · shadcn/ui

Productivity

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

A full-stack task manager with complete CRUD support and Google sign-up. Data is persisted through Prisma and MongoDB, and the responsive interface works at any screen size.

Task Manager

Next.js · Prisma · MongoDB · Clerk · Tailwind CSS

E-commerce

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

A Payload CMS storefront with role-based access control. Ships with authentication, a shopping cart, Stripe checkout, a paywall, a layout builder, and SEO configuration.

Bilstein

Payload CMS · Stripe · Next.js · MongoDB · SCSS

Analytics

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

An analytics dashboard with a bar chart, a recent orders view, and a customers page, styled with Tailwind CSS and driven by an in-memory data collection.

User Dashboard

Next.js · React · Chart.js · Tailwind CSS

API integration

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

Current conditions, a five-day forecast in three-hour intervals, air quality, and geocoding from the OpenWeatherMap API. Requests were designed in Postman, then implemented with the Fetch API.

Weather App

JavaScript · OpenWeather API · Postman · CSS

Marketing site

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

A car sales site built on semantic HTML for readability and SEO. ScrollReveal drives animations as elements enter the viewport, Swiper powers the catalog slideshow, and MixItUp filters listings by brand.

Car Trade

HTML · CSS · JavaScript · Swiper · ScrollReveal

The full record.

Experience, skills, and credentials each get their own page rather than a scroll-by summary.

Experience

Five roles across fintech, healthcare, heavy industry, and robotics, with the outcome of each.

5

Roles

View

Skills

The stack grouped by where it sits — interface, services, data, delivery, and quality.

76

Technologies

View

Education

Professional certifications from Microsoft, IBM, Meta, and Johns Hopkins, plus my degree.

8

Credentials

View

Let's talk about the problem.

I'm open to new opportunities and collaborations. Email me at gagik.yeranosyan14@gmail.com or use the form.