MRMahdi RashidiFull-stack developer
GitHub
Open to full-stack project conversations

Brief → build → stable release

One accountable builder for the whole product.

I’m Mahdi Rashidi, a full-stack developer who turns ambitious briefs into dependable digital products—with clear decisions, visible progress, and no mystery between the interface and the system behind it.

See how I work
Scope first
Unknowns surfaced early
SSR-first
Less JavaScript by default
Public source
Inspect the work yourself
Portrait of Mahdi Rashidi, full-stack developer
Case ownerMahdi Rashidi
MR / 2026
Delivery map
  1. 01Interface
  2. 02Systems
  3. 03Release

Full product accountability

The trust ledger

Trust is not a claim. It is a delivery system.

A strong stack matters. What stakeholders feel, however, is whether the project stays understandable, inspectable, and under control from the first decision to the final handoff.

01

Before build

We make the unknowns visible.

The brief becomes a scoped system map: users, critical flows, technical risks, and a release path everyone can understand.

Scope · architecture · priorities

02

During build

Progress stays inspectable.

Small, reviewable delivery loops keep decisions, trade-offs, and working software in view—before they become expensive surprises.

Working increments · clear decisions

03

Before handoff

The product is prepared to outlive the sprint.

Accessibility, performance, maintainability, and release checks are part of the build, not a cleanup phase at the end.

Quality checks · documentation · release

End-to-end ownership

The interface, the application, and the release belong to one story.

I work across the full product boundary so design decisions survive implementation and technical decisions remain legible to the people funding and using the product.

Product surface

Interfaces people can trust on first contact.

Responsive, accessible experiences with a deliberate visual system, clear interaction states, and performance treated as part of the design.

  • React & Next.js
  • Design systems
  • Accessibility
  • Motion with purpose

Part of the same delivery system

Application core

Systems that make the interface dependable.

Clear application boundaries, typed data flows, API thinking, validation, and maintainable server-side behavior behind every visible promise.

  • Server rendering
  • API integration
  • Data modeling
  • Validation & errors

Part of the same delivery system

Delivery control

A release path stakeholders can follow.

The work is broken into testable increments with explicit trade-offs, production checks, and a handoff that does not depend on hidden context.

  • Technical planning
  • Code quality
  • SEO & performance
  • Release readiness

Part of the same delivery system

Career experience

The roles behind the product thinking.

A concise record of where I worked, what I was trusted to own, and how each role shaped the way I build dependable products today.

  1. MyRegal

    Frontend Engineer

    Owned key frontend architecture and authentication workflows for a dynamic carpet catalog platform, with a focus on reliable data management, performance, and maintainability.

    Key contributions

    • Designed frontend architecture and authentication flows, including silent token renewal to maintain user sessions.
    • Built a concurrent PDF-generation workflow producing image-heavy catalogs of up to 172 pages in at most two minutes.
    • Reduced source image sizes by 90% through image-processing optimizations.
    • Applied TanStack Query for mutations, Suspense queries, infinite scrolling, and cache revalidation strategies.
    Next.jsReactTypeScriptTanStack QueryExpress.jsPuppeteerSharp

    Career record / 01

  2. MyRegal

    Freelance Frontend Developer · Remote

    Contributed to the development of a dynamic carpet catalog application as a remote freelance engagement, delivering frontend features for an evolving commercial product.

    Key contributions

    • Developed and refined frontend features for the carpet catalog experience.
    • Translated business requirements into usable interfaces within an existing product workflow.
    • Built the product context that informed broader architectural ownership in the subsequent MyRegal role.
    Next.jsReactTypeScriptTanStack QueryExpress.jsPuppeteerSharp

    Career record / 02

  3. Aseman Karmania

    Frontend Engineer · Team Guidance

    Helped deliver public-sector applications with real-time interfaces, large-data reporting, and operational workflows while supporting the growth of other frontend developers.

    Key contributions

    • Contributed to real-time operational interfaces for strategic public-sector applications.
    • Worked on reporting and download workflows involving substantial amounts of data.
    • Guided one frontend developer and two interns through implementation practices and project work.
    VueNuxtTypeScriptReal-time communicationReporting interfaces

    Career record / 03

  4. Aseman Karmania

    Frontend Developer

    Built data-intensive frontend interfaces for emergency-response and operational systems, where real-time updates and efficient rendering were essential to usability.

    Key contributions

    • Developed interfaces using Vue, Nuxt, and Vuetify.
    • Used virtualized lists to render large datasets more efficiently.
    • Integrated SignalR and Socket.IO for live operational updates.
    • Contributed to SOS, nationwide ambulance, and firefighter-management workflows.
    VueNuxtVuetifyJavaScriptTypeScriptSignalRSocket.IO

    Career record / 04

  5. Hamoon

    Frontend Developer

    Worked on frontend improvements in a startup environment, focusing on code maintainability and compatibility across devices.

    Key contributions

    • Helped migrate JavaScript code toward TypeScript to improve maintainability and type safety.
    • Improved Progressive Web App compatibility on iOS.
    • Supported frontend development in a fast-moving product environment.
    JavaScriptTypeScriptProgressive Web Apps

    Career record / 05

The working stack

A focused toolkit for the full web product.

From the first semantic element to the server that answers it, these are the technologies I use to turn product decisions into fast, maintainable web experiences.

The product surface

Frontend

09 technologies

  • HTML
  • CSS
  • SCSS
  • Bootstrap
  • Tailwind CSS
  • JavaScript
  • TypeScript
  • React
  • Vue.js

The application core

Backend

02 technologies

  • Node.js
  • Express.js

One connected system

Full-stack

02 technologies

  • Next.js
  • Nuxt

Proof before promises

This portfolio is the first case file.

The source is public because trust improves when the work can be inspected. The same standards described here are built into the page itself.

Live evidence
Portfolio system / current build

A working example of the delivery standard

  • Server-first architectureStatic content stays server-rendered; animation lives in focused client islands.
  • Accessible by constructionSemantic sections, keyboard focus, reduced motion, and meaningful content structure.
  • Intentional motionOne ambient blueprint, a scroll progress signal, reveal choreography, and portrait depth.
  • Inspectable sourceThe implementation is public, typed, and organized around reusable project primitives.
Inspect the source

A visible working contract

The project always has a next known step.

The sequence is simple on purpose: understand the pressure, map the system, build the riskiest truth first, then release with context.

  1. 01

    Read the real problem

    Clarify the user, business pressure, constraints, and what success must look like.

  2. 02

    Map the whole system

    Turn the brief into flows, boundaries, risks, milestones, and a credible release shape.

  3. 03

    Build in visible loops

    Ship the highest-risk slices early, review working software, and keep decisions reversible.

  4. 04

    Release with context

    Verify the product, document what matters, and leave the next owner a clear path forward.