Ramil Mamedov

Senior Frontend Engineer

Madrid, Spain

From first releaseto real scale.

I’m Ramil. I build React and TypeScript products—and the frontend architecture, performance, and practices that help them grow.

Explore my work Get in touch

Product judgment. System thinking. Hands-on engineering.

Selected work

The work behind
the words.

A few examples of what I’ve owned, improved, and helped teams build.

Identity AI Labs

Founding Senior Frontend Engineer

A real-time product. A million users.

Owned frontend architecture and system design for an AI companion platform, from 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

A real-time companion platform combines complex asynchronous state, long-lived sessions, and external services. As the product grew, the frontend needed to support that complexity while improving the experience on mobile.

What I owned

Frontend architecture and system design, from server rendering and data loading to client-side state, background synchronization, analytics, and production monitoring. I also established frontend standards, led code reviews, and mentored engineers.

The work

Optimized media, deferred resources, and tightened the critical rendering path. Alongside the performance work, I built product features and integrated external APIs, working closely 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

Approximate before-and-after figures from the project.

Thrive Career Wellness

Senior Frontend Engineer

Modern foundations for an evolving product.

Led frontend modernization across 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

Multiple applications shared a large frontend monorepo. Modernization involved the build system, an existing Ember interface, testing, and the conventions engineers used day to day.

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

Migrated testing from Jest to Vitest and contributed to frontend architecture, documented conventions, and developer 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 reduction and UI migration percentage describe separate modernization efforts. Both figures are approximate.

Buglance

Frontend Lead

One product ecosystem. Shared UI foundations.

Led frontend development across seven repositories, spanning 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

Led frontend development as the primary contributor across seven repositories. My work included the core product workflows, the Chrome extension, and the Next.js marketing application.

The work

Built a reusable TypeScript component library alongside the product applications, creating shared UI foundations for the ecosystem.

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

Repository count describes the scope of frontend ownership. Commit counts are intentionally not used as a measure of impact.

A little context

Close to the product.
Deep in the frontend.

My work sits between product thinking and frontend architecture. I turn complicated requirements into interfaces that feel simple, fast, and predictable.

Based in Madrid, I’ve worked with teams across Azerbaijan, Europe, and Canada. My experience spans AI products, SaaS, fintech, browser extensions, and design systems.

React and TypeScript are my strongest tools. The work is broader: making sensible tradeoffs, setting a direction, and helping other engineers do good work.

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.

Understand the workflow before choosing the abstraction. The interface, the system behind it, and the user’s task need to make sense together.

Make performance tangible.

Look at loading, payload, and main-thread work. A performance improvement should be something a person can feel.

Leave a useful foundation.

Shared components, clear conventions, thoughtful reviews, and mentorship help the next engineer move with confidence.

Let’s talk

Good products start
with a conversation.

Building a product, evolving a frontend, or looking for someone to help shape the engineering? I’d like to hear about it.