Product engineering leader focused on SaaS architecture, complex frontend systems, AI-assisted workflows, and developer-first platforms.

I work across React, TypeScript, Next.js, Node.js, Ruby on Rails, product architecture, customer-facing systems, and engineering leadership.

Recently, I’ve been focused on:

• Runtime/editor architecture for customer-facing views
• SaaS platform architecture and product delivery
• Complex frontend systems with schema-driven rendering
• AI-assisted engineering workflows with Claude / Claude Code
• Frontend performance, design systems, and developer experience
• Customer-facing product engineering and technical leadership

I occasionally contribute to open-source projects in the frontend, developer tooling, and SaaS ecosystem. These are selected examples that show debugging depth, performance thinking, framework reasoning, product UX, and public technical communication.

• Spectrum — SSR flicker / double-loading investigation
  Diagnosed a server-rendering flicker issue by tracing React Loadable bundle resolution through server-render logs, identifying why dynamic modules were loading again during hydration, and validating the fix through debug output.
  PR #5320

• Cal.com — duplicate API call performance fix
  Identified and removed a duplicate eventTypes.getByViewer request, explained the root cause, and validated the improvement with k6 load testing and p90 timing comparison.
  PR #9700

• Netlify / Next.js — dynamic import + serverless trace issue
  Reported a tricky runtime issue where experimental-serverless-trace broke dynamic imports, including a demo, reproduction repo, version details, and failure conditions.
  Issue #121

• Netlify / Next.js — optional catch-all routing edge case
  Reported a routing specificity bug with exact page structure and error output, helping maintainers isolate the issue.
  Issue #76

• React — Rules of Hooks lint-rule edge case
  Raised a subtle Hooks linting edge case with a failing test and discussed semantics with React maintainers.
  PR #22044

• Remotion — rendering API improvement
  Added Buffer support to renderStill() with test coverage and maintainer review.
  PR #1553

• Remotion — sequence API improvement
  Contributed to Remotion’s sequence API with maintainer-reviewed changes and positive feedback.
  PR #1507

• Evidence.dev — Query Viewer table scrolling
  Added scrolling support for query result tables, improving usability for larger datasets in analytical workflows.
  PR #465

• Uber Base Web — design-system contribution
  Iterated through design review and implementation feedback on a mature design-system repository.
  PR #2580

• Stitches — frontend tooling / design-system ecosystem
  Contributed small improvements across Stitches, including documentation and code clarity fixes.
  PRs

“Quality work! Thanks a lot, much appreciated! LGTM!”
— Jonny Burger (@JonnyBurger), Remotion

“Wow, amazing find. THANK YOU! This will be awesome to ship.”
— Brian Lovin (@brianlovin), Spectrum

“Awesomeeee!!!!”
— Max Stoiber (@mxstbr), Spectrum

“This is a great feature, really wanted something like this for a while.”
— Archie Wood (@archiewood), Evidence.dev

“This looks clear to me. Clearer, in fact. Thanks, @afzalsayed96!”
— Jonathan Neal (@jonathantneal), Stitches

“LGTM too”
— Pedro Duarte (@peduarte), Stitches / Radix ecosystem

“this is great! thanks so much for opening this and helping out <3”
— Lindsay Levine (@lindsaylevine), Netlify

• Evidence.dev PRs
• Remotion PRs
• Base Web PRs
• Stitches PRs
• Cal.com PRs
• Netlify Next-on-Netlify Issues

I have written publicly on frontend engineering, data visualization, ML competitions, and CSS-in-JS tooling.

• Medium
• Hashnode

Selected topics:

• React / Leaflet data visualization
• Intel Scene Classification challenge solution
• Linaria and CSS-in-JS tooling
• Frontend product engineering experiments

I also have experience in application security research and responsible disclosure through bug bounty programs.

• HackerOne: skyn3t

Recognition includes security research work with Ola Cabs.

I like owning ambiguous product and engineering problems end-to-end.

My preferred mode of work:

• Understand the business/customer problem deeply
• Translate ambiguity into technical direction
• Break large projects into small, shippable streams
• Use architecture to reduce risk, not create ceremony
• Keep old and new systems coexisting when migrations are risky
• Use AI tools as leverage, while keeping judgment and review human-owned
• Write and communicate tradeoffs clearly

• LinkedIn: linkedin.com/in/afzalsayed96
• GitHub: github.com/afzalsayed96
• Medium: medium.com/@afzalsayed96
• Hashnode: afzalsayed96.hashnode.dev