Ramil Mamedov

Senior Frontend Engineer

Madrid, Spain

From first releaseto real scale.

I'm Ramil. For 9+ years, I've built React and TypeScript products, owned frontend architecture, and fixed performance problems that show up at scale.

Explore my work Get in touch

I care about the product and the system behind it.

Selected work

What I built.
What changed.

Three projects where I owned frontend decisions and could measure the result.

Identity AI Labs

Founding Senior Software Engineer

A real-time product. A million users.

I owned the frontend architecture and system design for an AI companion platform as it grew from an MVP to approximately 1M+ users.

  • Real-time systems
  • Performance
  • Technical leadership

20s → 3s

LCP · approximate

Media, payload & critical path

Read the engineering story: Identity AI Labs

The engineering problem

The product had complex asynchronous state, long-lived sessions, and several external services. As usage grew, the frontend had to handle that complexity and get faster on mobile.

What I owned

I owned server rendering, data loading, client state, background sync, analytics, and production monitoring. I also set frontend standards, led reviews, and mentored engineers.

The work

I optimized media, deferred noncritical resources, and shortened the critical rendering path. I also built product features and external API integrations with product and design.

Outcomes

  • LCP improved from approximately 20 seconds to approximately 3 seconds.
  • Initial mobile payload fell from approximately 4.3 MB to approximately 1.7 MB.
  • Eliminated major main-thread blocking problems.

React · TypeScript · Remix · WebSockets

These figures are approximate comparisons from the project.

Thrive Career Wellness

Senior Frontend Engineer

Modernizing a large frontend.

I led frontend modernization in a large monorepo and built a Chrome extension for AI-assisted résumé tailoring and job applications.

  • Modernization
  • Browser extensions
  • Developer experience

≈82%

Smaller bundle

Create React App → Vite

Read the engineering story: Thrive Career Wellness

The engineering problem

The monorepo contained several applications, an Ember interface, an aging build system, and a mixed test setup. My work covered each of them, along with the conventions shared across the apps.

What I owned

Led the Create React App to Vite migration and approximately 80% of the Ember to React migration. Built and maintained the AI-assisted Chrome extension for résumé tailoring and job application workflows.

The work

I moved tests from Jest to Vitest, documented frontend conventions, and improved day-to-day workflows across the codebase.

Outcomes

  • Reduced bundle size by approximately 82% in the CRA to Vite migration.
  • Led migration of approximately 80% of the Ember UI to React.
  • Delivered job application and résumé-tailoring workflows in a Chrome extension.

React · TypeScript · Vite · Vitest · Chrome Extensions

The bundle and UI percentages come from separate projects. Both are approximate.

Buglance

Frontend Lead

Seven repositories, one product.

I led frontend work across seven repositories covering the core SaaS product, a browser extension, and a marketing application.

  • UI foundations
  • Product workflows
  • Frontend leadership

7

Repositories

One connected product ecosystem

Read the engineering story: Buglance

The engineering problem

The product ecosystem covered project management, scheduling, analytics, and role-based workflows. Frontend work extended beyond the main application into a browser extension and a marketing platform.

What I owned

I was the primary frontend contributor across seven repositories. I built core product workflows, the Chrome extension, and the Next.js marketing application.

The work

I built a reusable TypeScript component library shared by the product applications.

Outcomes

  • Delivered project management, scheduling, analytics, and role-based interfaces.
  • Built a browser extension and a Next.js marketing application.
  • Introduced a reusable TypeScript component library.

React · TypeScript · Redux · Next.js · Chrome Extensions

Seven repositories reflects the scope I owned. I don't use commit count as proof of impact.

A little context

Close to the product.
Deep in the frontend.

I work closely with product and design, then stay hands-on in the frontend. I turn complex requirements into interfaces that are fast and predictable.

Based in Madrid, I work remotely with Adia Health, a US healthcare technology company. My experience also includes AI companion products, SaaS, fintech, browser extensions, and design systems across teams in Azerbaijan, Europe, and Canada.

React and TypeScript are my strongest tools. I also spend a lot of time making tradeoffs explicit and helping other engineers make good decisions without me.

Selected experience

Request my résumé

Earlier product work at Vendiks & Finmarket and Ante Technologies included SaaS, fintech, complex workflows, and frontend tooling.

How I work

Start with the product.

I start with the workflow, then choose the abstraction. The interface and the system behind it should solve the same user problem.

Make performance tangible.

I look at loading, payload size, and main-thread work. If a user cannot feel the difference, the metric is not enough.

Leave a useful foundation.

I leave behind shared components, written conventions, and useful reviews. The next engineer should not have to rediscover the same decisions.

Away from work

A few things that
keep me curious.

Outside work, I usually have a game, match, or long ride to think about.

A galaxy far, far away.

Star Wars has been my favourite science-fiction universe since I was five or six. I've watched almost everything, played the games, and collected more than a few T-shirts along the way.

Think, aim, repeat.

I play chess at around 1900 Elo. At university, I competed professionally in archery.

Away from the keyboard.

I've followed Real Madrid since 2009. I also make time for video games, cycling, and whatever sport gets me moving after a day in front of a screen.

Let's talk

Tell me what you're
working on.

I'm open to roles, freelance projects, startup collaborations, and messages about the work.

Prefer email?