Avery Lindqvist

Taking on two projects for Q2

I build software that feels quiet, considered, and quick.

Fifteen years turning ambiguous problems into interfaces people trust. Independent since 2019, working with founders and small teams who care about the details nobody asks for.

Selected work

Things I have built

A few recent engagements. Each one includes what the constraint actually was, and what changed.

A financial dashboard showing reconciliation charts on a dark background

A payments dashboard rebuilt around the two questions operators actually ask: what broke, and what is it costing me?

  • TypeScript
  • Next.js
  • PostgreSQL
  • Tremor
A grid of interface components and colour swatches

A design system for a 40-person product org, built so it survives the people who made it.

  • React
  • TypeScript
  • Style Dictionary
  • Storybook

How I can help

Ways we might work together

01Product engineering
Embedded with your team, from first sketch to something running in production with tests, telemetry and a migration path.
02Interface systems
A component library and token set your team will actually keep using — documented, accessible, and boring in the ways that matter.
03Technical discovery
A two-week engagement that turns a vague ambition into a scoped plan, a prototype, and an honest estimate.
04Performance work
Profiling, budgets and the unglamorous fixes that take a slow product back under a second.

About

Avery Lindqvist

Product Engineer & Interface Designer

Copenhagen, Denmark

Independent product engineer working at the seam between design and systems. I take projects from a vague document to something shipped, measured, and maintainable.

Engineering

  • TypeScript
  • React & Next.js
  • Node.js
  • PostgreSQL
  • Go
  • Edge & serverless runtimes

Design

  • Interface systems
  • Typography
  • Prototyping
  • Design tokens
  • Accessibility (WCAG 2.2)

Practice

  • Technical discovery
  • Incremental migration
  • Observability
  • Design–engineering handoff
  • Team mentoring

Writing

Notes and essays

The real cost of a component

Every component in a shared library is a promise you make to future colleagues. Most libraries make far too many promises.

Read

Latency is a design material

We treat speed as an engineering concern that designers inherit. It is closer to a material property — something you design with, not around.

Read

Next step

Have something in mind?

Tell me what you are trying to build and what is in the way. I read everything and reply within two working days.