dlmarques.com
about · work · writing

Senior Frontend Engineer building considered, durable web experiences.

Daniel Marques

I started writing code professionally in 2019 and have spent the years since shipping production frontends across e-commerce, fintech, and real-time operations. The thread through all of it: architecture that holds up, interfaces that respect the people using them, and teams that ship calmly.

These days I work mostly in React and TypeScript, but I've been expanding into backend work with .NET and building APIs in production. I'm also pursuing a BS in Computer Science. I care about performance, accessibility, mentoring the engineers around me, and owning features from database to UI.

Get in touch Read the work
About

A bit more about me.

I started writing code professionally in 2019 and have spent the years since shipping production frontends across e-commerce, fintech, and real-time operations. The thread through all of it: architecture that holds up, interfaces that respect the people using them, and teams that ship calmly.

6+years shipping production frontends
50k+downloads of a shared component library I architected
98Lighthouse perf on the headless platforms I lead
4microfrontends I architected and shipped

How I work.

  • Owning end-to-end. From architecture decisions through ship and incident response — I want skin in the game on every layer.
  • Quality on a budget. Performance and accessibility are constraints I plan for, not regression-tests we hope for.
  • Writing it down. ADRs, design docs, and code comments are how teams scale knowledge — I make them part of how I ship.
  • Learning loudly. Currently going deeper into backend with .NET, and pursuing a CS degree alongside work.
— keep scrolling, the rest of the site continues below.

Six years, four chapters.

From freelance MERN work to leading frontend architecture for headless commerce in production.

    • Leading the frontend architecture for two Shopify headless e-commerce platforms (Sprüngli and Biral), integrating DatoCMS, Algolia search, and Shopify Storefront APIs.
    • Hit Lighthouse scores of 98 Performance, 94 Accessibility, and 100 Best Practices through careful rendering optimization, semantic HTML, and performance budgeting.
    • Built a modular component library that powers product configurators, checkout flows, and filtering across both platforms, documented in Storybook as a standalone package.
    • Shipping backend features in .NET: RESTful API endpoints, DatoCMS webhook integrations with token-based auth, data validation, and SendGrid email integration.
    • Mentoring two engineers through daily code reviews, pair programming, and architecture discussions. Writing ADRs to document decisions for the team and for AI agent context.
    • Presented Biral's tech approach at our company all-hands. The CEO specifically highlighted how we're using AI in our development workflow (Figma MCPs, Claude Code, Cursor).
    • React
    • TypeScript
    • Remix
    • Next.js
    • .NET
    • Shopify
    • DatoCMS
    • Algolia
    • Azure
    • Architected a shared component library and frontend framework that hit 50k+ downloads across multiple teams. We treated it like an internal product, not just shared code.
    • Built and managed 4 microfrontends for a large-scale internal service catalog, enabling teams to deploy independently and own their domains.
    • Cut developer onboarding time by roughly 30% and reduced project setup boilerplate by about 40% through better documentation, starter templates, and self-service tooling.
    • Pushed quality forward through automated testing (Jest, Playwright), thorough code reviews, and consistent architectural guidelines across all consuming teams.
    • React
    • TypeScript
    • Microfrontends
    • Jest
    • Playwright
    • Took a legacy web application and rebuilt it in React and TypeScript for Portugal's national road authority. The platform handles real-time CCTV monitoring, incident reporting, and resource dispatch.
    • Built a 20+ component library from Figma specs, turning design tokens into accessible, reusable React components.
    • Improved overall app performance by about 35% through code-splitting, modern rendering patterns, and modular component architecture.
    • Shipped features in a safety-critical, real-time environment where reliability actually matters and iteration cycles are tight.
    • React
    • TypeScript
    • Figma
    • WebSockets
    • Built and deployed full-stack web applications using the MERN stack, owning everything from client requirements through to production deployment.
    • Designed REST APIs, implemented auth flows, integrated third-party services, and managed CI/CD pipelines across multiple client projects.
    • MongoDB
    • Express
    • React
    • Node.js

Always learning.

What I bring to a team.

A working set, not a buzzword list — these are the tools and practices I reach for daily.

Architecture & System Design

  • Scalable Frontend Architecture
  • Headless Commerce
  • Microfrontend Design
  • Design Systems & Component Libraries
  • SSR & Hydration Strategies
  • API Design (REST, GraphQL)
  • State Management Patterns

Performance & Quality

  • Core Web Vitals Optimization
  • Accessibility (WCAG)
  • Automated Testing (Jest, Playwright, RTL)
  • Performance Monitoring & Profiling
  • CI/CD Pipelines

Engineering Practices

  • Technical Mentoring
  • Architecture Decision Records
  • Code Review Culture
  • Cross-functional Collaboration
  • AI-assisted Development (Claude Code, Cursor)

Technologies

  • React
  • TypeScript
  • Next.js
  • Remix
  • TanStack
  • Node.js
  • Express
  • C# / .NET
  • Shopify (Headless)
  • DatoCMS
  • Algolia
  • PostgreSQL
  • MongoDB
  • Azure
  • Docker
  • AWS

Things I built on the side.

LearnInFive

An AI-powered educational platform that delivers concise daily CS concepts. I built the whole thing end-to-end with React, Vite, Express, MongoDB, and the OpenAI API.

  • React
  • Vite
  • Express
  • MongoDB
  • OpenAI
learninfive.com

Notes from the practice.

A reserved space for essays on architecture, performance, and shipping.

First essays landing soon.

I’m drafting a few pieces on component libraries as internal products, headless commerce tradeoffs, and architecture decision records. Drop your email below and I’ll let you know when the first one ships.

Let's talk.

I’m open to senior frontend roles, architecture consulting, and the occasional fun side project. The fastest way to reach me is email.