You have had three quotes and each one describes the person differently. One is front-end, one is full stack, one is a software engineer. You are trying to work out whether this changes anything for you.
Usually it changes quite a lot. Here is what each actually means and how to pick.
The split, plainly
Every web project has two halves. The half that runs in your visitor's browser, and the half that runs on a server somewhere.
Front-end is the first half. Back-end is the second. Full stack is somebody who works across both.
Front-end
Everything the visitor sees and touches. The layout, the typography as it actually renders, what happens when they tap something, how fast it appears, whether it works on a four-year-old Android phone on a weak connection.
A strong front-end developer is the difference between a site that feels expensive and one that feels like a form.
Back-end
Everything the visitor never sees. Where the data lives, who is allowed to see what, how a payment is taken without losing it, what happens when the property feed sends malformed data at two in the morning.
Back-end problems are the ones that cost real money when they go wrong, because they involve data, payments or access.
Full stack
Both, with one side usually stronger. This is not a compromise title. For most business projects it is the correct hire, because the project is not big enough to keep two specialists busy and every handover between them costs you clarity.
Ask any full stack developer which half they are stronger in. Anyone who says they are equally expert in both is selling.
Which one does your project need?
| Your project | Who you need |
|---|---|
| Brochure site, no accounts, no payments | Front-end, or full stack |
| Site plus enquiry forms going into a CRM | Full stack |
| Booking, payments, user accounts or a portal | Full stack, with real back-end strength |
| Property search pulling from a live feed | Full stack, with real back-end strength |
| Redesigning an existing site that already works | Front-end |
| Internal tool where nobody cares how it looks | Back-end |
| Product with a team and a roadmap | Specialists, not a generalist |
The question that sorts it in one minute
Does the site need to remember anything?
If the answer is no, it only displays information, you are mostly in front-end territory. If the answer is yes, it stores enquiries, accounts, orders, bookings, uploads, anything, you need back-end capability and you should not hire someone who treats it as an afterthought.
Why this matters more than the day rate
A front-end specialist taking on a back-end project will usually get it working. The problem arrives later: data modelled badly, no thought given to who can see what, secrets stored where they should not be, and no plan for what happens when something fails halfway through.
None of that shows at launch. All of it shows in month six, and fixing it then means rebuilding rather than patching.
What about the frameworks in the quote?
React, Next.js, Node, Laravel, WordPress. These are tools, and the choice matters less than people pretend as long as the person is genuinely fluent in the one they picked.
The one thing worth checking is whether the choice suits who will run the site afterwards. A custom build needs a developer for every change. A WordPress site lets your team edit pages themselves. That is a business decision rather than a technical one, and it should be yours.
Frequently asked questions
Is full stack worse than hiring two specialists?
For a small or medium project, no, and it is usually better. One person holds the whole picture and nothing is lost in handover. Past the point where one person cannot keep up, specialists win clearly.
Do I need a DevOps person as well?
For a normal business website, no. Modern hosting handles deployment, certificates and scaling without a dedicated person. For a product with uptime commitments and real traffic, eventually yes.
How do I check someone's back-end claim without being technical?
Ask what happens when a payment succeeds but the confirmation email fails, or what they do when an integration goes down. Someone with real back-end experience answers immediately and in detail, because they have lived it. Someone without changes the subject to frameworks.
Does the title affect what I should pay?
Less than the complexity of your project does. My own published project minimum is AED 31,500 regardless of which half the work sits in, with retainers from AED 16,000 a month. Those are my rates rather than market data.
Published 4 October 2026 by a Dubai-based freelance full stack developer.