Available for workLet's talk

Résumé · Alejandro Haydar

Choose a format

Same résumé, three ways. Pick whatever your workflow needs.

Prefer to view it first? Open the PDF in a new tab →

Open to freelance and full-time work

Alejandro Haydar in profile against a vivid green lightLoading portrait motion

Alejandro Haydar

AI Forward Deployed Engineer & Product Strategist

I’m an independent AI Forward Deployed Engineer currently working with Snowplow Analytics, with more than a decade of product leadership, including three platforms acquired or spun off.

The best part is the room before anyone writes code — sitting with a team, finding the problem worth solving, then building it for real. I audit how the work actually gets done, decide where AI belongs and where it doesn’t, and ship the agents, evals, and human-in-the-loop interfaces people actually adopt.

How I think

Experience

Full story
  1. Alebuild

    Founder · Forward Deployed AI Studio

  2. Snowplow Analytics

    Design Engineer · Freelance

  3. Thought Industries

    Design Engineer · Director of UX

  4. Genscape / Wood Mackenzie

    Product Designer · Contract

  5. Philips Healthcare

    Interaction Designer · Contract

  6. Commonwealth Financial Network

    Design System Lead

  7. Liberty Mutual Insurance

    UX/UI Front End Developer · Contract

  8. Swirl Networks

    UX/UI Visual Designer

Latest notes

View feed
  1. 3 Sprints in 3 Weeks: How Learn Everywhere Came Together

I Miss You

blink-182

Last played recently

Okay — so how does any of this actually get made?

The Double Diamond, run small

Not one big diamond. Many small ones.

Every phase still happens, in small loops, against working software.

01 Multi-agent parallelism

Agents work every step in parallel, each in its own worktree. I’m the gate between steps: ten directions in, two kept, every cut with a reason.

Develop · in parallel

  1. Research

    • NotebookLM
    • Mobbin

    synthesis → spec v0.1

    1 spec

  2. Directions

    • Claude Code
    • Conductor
    • Cursor
    • MagicPath

    10 working directions

    10 → 2

  3. Previews

    • Netlify
    • GitHub

    /playground links

    2 → 1

  4. Polish

    • Figma
    • Subframe

    tuned components

    next loop

cuts and findings feed the next loop

10 in → 2 kept. Every cut gets a reason.

  1. blocking
  2. in context
  3. room for sources
  4. detached
  5. covers
  6. cramped
  7. noisy
  8. tiny
  9. heavy
  10. hidden

8 cut: blocking · detached · covers · cramped · noisy · tiny · heavy · hidden

02 Solution-first validation

A working prototype, early. Touch and feel surface the real problem faster than a spec can.

Discover + Define · on a working build

Spec · v0.1

Problem

Answers aren’t accurate enough.

the real problem is the wait.

prototype · answer panel

Why did signups drop last week?

Thinking…4.2s

Testers stopped waiting at about four seconds.

03 The live playground loop

Every direction ships to a live /playground preview, so people react to the real thing while it’s still cheap to change.

Deliver · early, to real people

…/playground/answer-panel
Thinking…

Signups dipped the day the pricing page changed. Most of the drop is on mobile…

Session note “V2. I could start reading while it worked.”

04 Taste over template

Generated UI drifts toward a polite, generic middle. I pull it back by hand: timing, spacing, and motion, tuned in code.

Deliver · converged by hand

answer panel · final pass

Why did signups drop last week?

✨ Generating response…

Reading 3 sources

Signups dipped the day the pricing page changed.

Tuned by hand

Timing
spinner until donefirst words at 280ms
Spacing
16 everywhere8 · 12 · 24 rhythm
Motion
linear fadeease-out · 40ms stagger

same wait. feels shorter.

Get in touch

Building something complicated?

Tell me what you’re building. If it needs product thinking, interface design, and production code, I’d like to hear about it.