Skip to content
FP

Fabio Piras

Frontend Engineer · b. 1990

I build fast, accessible React and Next.js interfaces, from Figma to production.

Reach out

About Me

I've been a frontend engineer for almost five years, working as a consultant with a focus on web development. My earlier roles, in operations and working directly with clients, taught me to involve people from the start, manage my time well and spot the priorities quickly.

Interface quality

I enjoy building interfaces, simple or complex, that are optimized and accessible. I care about usability and WCAG compliance without neglecting performance and code quality, building scalable components that stay easy to maintain as the product grows.

Collaboration & AI

Every day I work closely with designers and developers as part of a team. I bring AI into the way I work in a practical, deliberate way, using tools like Claude Code, Codex, MCP servers, and custom agents and skills to be more effective without compromising on quality.

Preferred toolkit

I choose tools to fit the problem. These are some of the ones I currently use to build, verify and ship frontend products

Drag to rotate, or use the arrow keys.

Frontend

  • React
  • Next
  • TypeScript
  • Tailwind
  • shadcn
  • Motion

UI engineering

  • a11y
  • React Hook Form
  • Storybook

Data & backend

  • TanStack Query
  • Zustand
  • Zod
  • Supabase
  • RTK Query
  • Recharts

Quality

  • Vitest
  • React Testing Library
  • Playwright

Delivery

  • pnpm
  • Vercel
  • Claude Code
  • MCP

Consulting industries.

As a consultant, I've worked on products across very different industries, from digital payments and sports data to platforms for events and campaigns.

  • Fintech & Payments

    Interfaces for electronic money platforms, financial transactions and digital payments, including mobility services and electronic toll collection.

    • eMoney
    • DigitalPayments
    • Mobility
  • Energy & Utilities

    Applications and dashboards supporting the energy transition: consumption monitoring, data visualization and platforms for electric mobility.

    • Consumption
    • Dashboards
    • eMobility
  • Real Estate & Valuations

    Web applications and management tools for property valuation, bank appraisals and due diligence workflows.

    • Valuations
    • Appraisals
    • DueDiligence
  • Sport Tech & Fitness

    Interfaces for sports medicine applications, athletic data and test visualization, alongside platforms for booking fitness services and activities.

    • AthleticData
    • TestReports
    • Bookings
  • Marketing & Events

    Platforms connecting physical campaigns with digital interactions: QR tracking, sponsor and event management, and dashboards for analyzing scans.

    • QRTracking
    • Sponsorships
    • Analytics

Engineering

How I structure interfaces, define boundaries and verify the behaviors that matter. Small decisions that keep a product understandable as it grows.

Compose responsibilities.

I build interfaces from focused components; hooks coordinate stateful behavior.

  • Single responsibility
  • Custom hooks
  • Explicit props

ReleaseSummary.tsx

type Props = { tasks: Task[] };

function ReleaseSummary({ tasks }: Props) {
  const { ready, filter, visible } = useReleaseSummary(tasks);
  return (
    <Card>
      <Readiness value={ready} total={tasks.length} />
      <TaskList tasks={visible} filter={filter} />
    </Card>
  );
}

“Make each program do one thing well.”

Doug McIlroy

Keep a feature close to its context.

I organize code by feature: each view has its own folder, where components, hooks and tests live together. Other modules import only from its public entry point.

  • Colocation
  • Feature scope

Feature structure

views/tasks/
├── index.ts            
├── components/
│   └── task-list/
│       ├── index.tsx
│       └── task-list.test.tsx
├── hooks/
│   └── useTaskPage.ts
└── model/
    └── task.ts

“Place code as close to where it's relevant as possible.”

Kent C. Dodds

Optimize what users actually feel.

I treat performance as part of the user experience, with Core Web Vitals as the reference: how fast content appears, how fast the page responds and how stable it stays.

  • Core Web Vitals
  • Server Components
  • React Compiler

From metric to solution

LCP
How fast the main content appears
Server Components: HTML ready on arrival, less JavaScript
INP
How fast the page responds to a click or tap
React Compiler: fewer re-renders, automatic memoization
CLS
Whether the layout shifts while loading
next/image and next/font: space reserved in advance

Test what someone needs to get done.

I test the flows people depend on: filling in a form, understanding an error, getting back to a usable screen. Tests use the page like a user does, finding elements by role and label rather than by internal details.

  • Playwright
  • Testing Library

new-task.spec.ts

test("creates a task", async ({ page }) => {
  await page.getByRole("button", { name: "New task" }).click();

  const form = page.getByRole("dialog");
  await form.getByLabel("Task name").fill("Review form");
  await form.getByRole("button", { name: "Create task" }).click();

  await expect(page.getByText("Review form")).toBeVisible();
});

Usable by everyone, with any input.

I build to WCAG 2.2 AA from the start, not as a final check: semantic HTML first, ARIA only where HTML falls short, visible focus and full keyboard support. These tabs are an example: try the arrow keys.

  • WCAG 2.2 AA
  • Keyboard & focus
  • Screen reader

Keyboard navigation

Built to be used.

Not a screenshot. Search it, resize it, tab through it, break the form.Search it, filter it, add a task, break the form.

Release DeskOverview
Fabio

Frontend Engineer · Demo

Overview

Your release, at a glance.

Total tasks04
In review03
Ready01

Release readiness

25%

1/4 readyOne clear view of what is ready to ship.

Create a task

Add one small piece of work to this release.

Now let's build yours.

Have a project or a question? Let's talk.