Ali PajandI ship accessible UIs and reliable releases-design systems, frontend architecture, and DX tooling.

9+ years turning messy requirements into shipped product. I own design-system rollouts, tight TypeScript/React stacks, and the release discipline teams need to move fast without breaking quality.

Based in Montreal, Quebec, Canada

Proof at a glance

9+
years building product
Design systems
rollouts & shared UI
DX & architecture
typed APIs, pipelines, review
A11y-first
UIs that ship

Peer feedback

Informal endorsements from people I worked with on these teams. Names aren’t published here without explicit permission; each line shows role and employer only, as they described it.

  • Ali built high-quality, accessible UIs and helped us ship faster with a solid design system and clear docs.

    Attribution
    Engineering
    Emplifi
  • Took ownership from design to deployment. Kept design and engineering in sync and pushed for better UX and performance.

    Attribution
    Product / Engineering
    ControlTech Startup Studio
  • Set up our frontend workflow, Storybook, CI/CD, and tooling the whole team could rely on.

    Attribution
    Engineering
    ControlTech Startup Studio

Get in touch

Use this if you want to talk about something concrete—a post, a project, or a technical question. I’m not looking for employment opportunities; I’m still happy to hear from people who share enough context to reply usefully.

Good reasons to reach out

  • Feedback or questions on writing or work on this site.
  • Design systems, accessibility, TypeScript/React, or DX tooling—when you have a specific angle.
  • A concrete product or architecture problem (not generic networking intros).
  • Something else that fits what you see here—skip vague “just connecting” messages.
Message me here

Jumps to the form below—use it if you want everything in one thread instead of email or LinkedIn first.

Contact form

Prefer the form? I usually reply within a few business days. All fields are required.

How you’d like to be addressed.

I only use this to reply—no mailing lists.

Role, location, timeline, stack, or the problem you’re solving—short is fine.