The build does not match the design
Approximated spacing, an invented type scale, hover states nobody implemented. I work from the Figma file directly and raise responsive problems before building, not after.
Frontend development in React, Nuxt and plain JavaScript.
Interfaces built to the design, fast on real devices, accessible by default and readable by whoever maintains them next — from a single Figma file to a full component library.
Interfaces built to the design, fast on real devices, accessible by default and readable by whoever maintains them next — from a single Figma file to a full component library.
What I actually get called in to fix
That is the background I bring to product teams now: I am comfortable owning the frontend layer of an application, not just styling pages. Most of what makes a front end good is unglamorous — the state that does not get tangled, the component that is genuinely reusable, the layout that holds at 320 pixels, the interaction that still works with a keyboard.
It is fast on your laptop and slow for users
Oversized bundles, render-blocking scripts, images shipped at full resolution, layout that shifts while loading. Real users are on mid-range phones and imperfect networks.
It is unusable with a keyboard or a screen reader
Div elements standing in for buttons, focus states removed for looking untidy, forms with no labels. Far cheaper to build in than to retrofit.
Nobody wants to touch the component
A component that has grown a dozen boolean props and three special cases is one everybody works around instead of using.
What I deliver
- Pixel-accurate implementation of Figma designs, responsive from 320 pixels upward
- React and Next.js interfaces — components, state, routing and data fetching
- Vue and Nuxt.js applications, including server-side rendering and SEO handling
- Reusable component libraries and design system implementation
- Performance work: bundle analysis, code splitting, lazy loading and Core Web Vitals
- Accessibility: semantic HTML, keyboard navigation, ARIA where it is genuinely needed, WCAG contrast
- Marketing sites and landing pages in fast, dependency-light vanilla JavaScript
- Frontend refactors that reduce a codebase rather than adding another layer to it
TECHNOLOGY I USE
- React
- Next.js
- Vue.js
- Nuxt.js
- JavaScript
- TypeScript
- HTML5
- CSS3
- Tailwind
- Sass
- Figma
- Git
How a project runs
-
Design and technical review
I go through the design file before writing anything, and flag the places that will not survive a narrow viewport or a long string of real content. Catching these in review costs minutes; catching them in QA costs days.
-
Component architecture
What is a component, what is a page, what is shared, and where state actually belongs. Deciding this deliberately is the difference between a codebase that scales and one that calcifies.
-
Build
Semantic HTML first, then styling, then behaviour — so the thing works before it is decorated. Mobile-first, tested at real breakpoints on real devices rather than in a browser resize.
-
Accessibility and performance pass
Keyboard navigation, focus order, screen reader labels and colour contrast, alongside bundle size, code splitting and Core Web Vitals. A dedicated stage with its own checklist.
-
Handover
Readable code, a clear commit history, and documentation of anything non-obvious. The measure of a good handover is that the next developer does not need to ask me anything.
Who you’re working with
Ashekur Rahman
You get back what your designer drew, including the states and details that make it feel finished, optimised for mid-range phones on ordinary networks — where your users actually are and where Core Web Vitals are measured. Conventional patterns, small components and honest naming, no clever abstraction that only makes sense to the person who wrote it.
- Based in
- Bangladesh, worldwide clients
- Experience
- 11 years frontend & WordPress
- Rating
- 5.0 — every Upwork contract
- Response time
- Within one working day
Questions I get asked
What frontend frameworks do you work with?
React and Next.js, Vue and Nuxt.js, and plain JavaScript where a framework would be overhead. Four years of that was leading React work at Peymynt and a year building Nuxt.js applications at Sumashtech, so both are production experience rather than side-project familiarity.
Can you work with our existing team and codebase?
Yes — that is a large part of what I did across my years on agency and product teams. I follow the conventions already in the codebase rather than importing my own preferences, and I would rather ask than guess about anything architectural.
Do you do backend work as well?
No, and I would rather be clear about that than stretch. I work at the frontend layer and integrate with whatever API your backend team provides. For WordPress and Webflow projects I handle the full build, because the backend there is the platform.
Can you convert a Figma design to code?
Yes, and it is a significant share of my work. I build to the file accurately, including hover and focus states, empty states and error states — the parts that are easy to skip and obvious when they are missing.
Do you write tests?
If the project has a testing setup, I work within it. If you want one established, that is worth scoping explicitly rather than assuming — it changes the estimate and it is better discussed than discovered.
Are you available for contract or long-term work?
Both. I take fixed-scope projects and ongoing part-time arrangements with product teams. I am freelance full-time, so availability is a scheduling question rather than a moonlighting one.
Projects built this way
- Alpe — a B2B marketplace front end for the oil and energy industry, every screen written by hand
- Zapta — a demo agency site with a filterable portfolio, team, testimonials and blog
- Velour — a luxury fashion photography studio site with no framework, custom CSS and vanilla JavaScript
Available for new projects
NEXT STEP
Tell me what you are building.
Based in Dhaka, Bangladesh, working with clients worldwide. Describe the project and where it is stuck — every serious enquiry gets a reply within one working day.
- Reply within one working day
- Fixed quote before work starts
- UK, EU and US hours covered
ALSO WORTH READING