Alanna Fischer

Alanna Fischer

Senior Product Designer · Developer platforms, data infrastructure & AI

I help teams get to clarity when the problem is fog, then ship it. For seven years I've designed for technical users: enterprises at Dune, developers as the founding designer at smlXL (acquired by Dune), and investigators at Chainalysis.

I like starting from the mental model, keeping powerful tools easy to pick up, and building in the codebase myself when it helps.

In my free time I ride horses, make meticulously curated playlists, and go on long walks around the city.

Open to senior and staff roles in developer platforms, data infrastructure, and AI.

Experience

7+ years
Show other experienceHide other experience
  • Several internships and freelance work

    Various employers and clients

    2017 to 2019

Education

Work

How I work

01

Low floor, high ceiling

Make the first step obvious and keep the depth for experts. Sim IDX asked developers to learn two concepts, sim.studio paired a wizard with a code editor where code earned its place, and simAI drafts every step but lets developers edit it.

02

Structure before features

Chainalysis' community workflows, smlXL's pipeline model, Dune's org layer: each was infrastructure first and interface second, built to hold next year's requirements instead of the loudest request today.

03

Break hard problems into parts

Fog clears one decision at a time. For Sim IDX, that meant daily sessions on one open question each; for the rebrand, sorting every component into seven buckets before designing anything.

04

Bring people in early

Legal before the scope sets, engineers into research, a skeptical engineering manager into user testing. Match fidelity to the room: frameworks, then concepts, then workflows, then UI.

05

Leave the team better set up

At Chainalysis I set up the pipeline from customer success to design and ran research before we had a researcher. At Dune, the rebrand changed how designers work for good: designers kept shipping code, a weekly reviewer rotation took hold, and I started a prototype, review, hand off, polish loop with engineering.

06

Ship it, then sweat the details

Specs became PRs. I stay with the work through engineering and polish the small things after handoff, so what ships matches what we meant.

Receipts

7 years in, 4 numbers out.

What teammates say

Let's talk

The deep dives live in conversation. If you're hiring for hard, structural product problems, I'd love to hear about them.