Front-end engineering for teams that need interfaces to hold up in production — not just in mockups.
I'm Amr Dajani. I design and build web products with a focus on accessibility, performance, and maintainable code.
I partner with teams on front-end engineering — from scoping through shipped code and what comes after launch.
Three lenses I bring to every engagement; you can start where you are, and we keep the same thread through delivery.
Align
We nail scope, constraints, and what success looks like — briefs, Figma, or a rough direction. You get honest trade-offs and a plan you can share with stakeholders, not a black box.
Build
Production front-end in your stack: components, pages, and integration with real data. Small PRs, previews, and patterns that match how your team reviews code — not a throwaway prototype.
Sustain
Fast loads, accessible patterns, and documentation so the next feature doesn’t undo the last one. I optimize for maintainability after launch — when most of the real work happens.
Product goals, users, constraints, and what’s already in place — brief, deck, Figma, or a Loom. The messier the truth, the better the plan.
What “done” means, what can wait, and how we’ll know it worked. I’ll surface trade-offs in plain language so you can decide with your team.
Milestones, risks, and a sensible sequence — so you’re not buying a black box. Adjust until it fits your timeline and stakeholders.
We start with small, reviewable changes — previews or staging — so feedback stays fast and nothing surprises you in week three.
About
I partner with teams to turn complex requirements into maintainable front-ends: design systems, performance budgets, and UI that holds up in production — not just in mockups.
Whether you're shipping a new product surface or untangling a legacy app, I care about the interface people actually live in — load times, clarity, and code that the next developer won't dread opening.
Capabilities
Front-end craft, system thinking, and the habits that keep products maintainable after launch — not just shippable on demo day.
How I ship
Small PRs, clear scope, no surprise rewrites
Where I lean in
Dense UI, data-heavy views, marketing surfaces
How teams work with me
Embedded with eng & design, or async with tight loops
What I optimize for
Maintainability, a11y, and fast iteration after v1
Tokens, documentation, and composable primitives that survive handoff — designers and engineers pulling from the same source of truth.
Core
UI & motion
Ship
Accessibility baked in — focus order, keyboard paths, and reduced motion considered before polish.
Selected work
Live shipped work — commerce, agency, and SaaS.
Independent apparel label — e-commerce, seasonal storytelling, and a storefront built for repeat visits. Designed where we live; styled for every day.
View project
Digital agency marketing site — positioning, services, case-study grid, and conversion paths built for speed and polish. Engineering-led storytelling for ambitious brands.
View project
AI inventory management — marketing site for a retail platform: feature grid, social proof, pricing tiers, and demo flows tuned for conversion.
View projectFAQ
Quick answers about scope, stack, and how we work together.
Front-end engineering for web products: marketing sites, dashboards, e-commerce flows, and design-system implementation. I’m strongest where the UI has to stay fast, accessible, and maintainable after launch — not just look good in a deck.
I’m flexible. I can embed with product and design for a sprint or a longer phase, or work async with clear specs, Figma, and Slack. Small PRs, previews or Storybook for UI, and written trade-offs so everyone knows what shipped and what’s next.
Most often React and Next.js, TypeScript, and Tailwind or CSS that matches your existing system. I’m happy to follow your conventions — the goal is code that fits your repo and reviewers, not a parallel universe.
I implement and refine UI in code — spacing, motion, responsive behavior, and accessibility. If you have a designer, I partner closely with them. If you’re early-stage, I can help structure pages and components from rough direction, but I’m not a brand identity shop.
They’re part of delivery, not a separate phase. I care about real metrics (Core Web Vitals, bundle size) and real users: keyboard paths, focus, labels, and reduced motion. We fix the obvious issues before merge, not after a late audit.
It depends on timing and fit. The best next step is a short note about what you’re building, your stack, and when you need help — I’ll reply with availability and whether I’m the right person or can suggest someone.
Usually project-based milestones or a monthly retainer for ongoing work, scoped to outcomes we agree on upfront. I don’t publish a rate card here because every engagement is different — happy to discuss after I understand the scope.
I work remotely with teams in overlapping time zones. If we’re a good fit, we’ll align on hours for standups, reviews, and anything that needs real-time collaboration.
Share the product, stack, and timeline — I'll reply with availability, fit, and sensible next steps.
Get in touch
Amr Dajani