The difference between a web designer and a software engineer

They both make "something on the internet", but they are two trades. How to tell them apart, and how to avoid hiring the wrong one.

If you do not work with it daily, the distinction is invisible: both make “something on the internet”, both send a quote, and sometimes both use the same job title. Yet they are two trades, and hiring the wrong one is an expensive mistake that only becomes visible months later. Here is the difference, without making either the lesser trade.

Two trades

The web designer builds how your company presents itself: design, copy, findability, a site that earns trust and moves visitors to the phone or the form. The centre of gravity is design and communication, and the tool is usually a system like WordPress with themes and plugins. Good work, and for most companies exactly what is needed.

The software engineer builds systems that do something: calculate a quote by your rules, track stock across three channels, run a customer portal with a hundred people in it at once, connect your webshop to your accounting package. The centre of gravity is logic, reliability and data that is still correct five years on.

The rule of thumb: does it describe your business, or does it run your business? A business card on the internet is web design work. A system your operations flow through is software.

Why the confusion is expensive

In practice the mistake almost always goes one way: a business process is placed with a web designer, because they already did the website and “can probably build this too”.

What follows is predictable and nobody’s fault. The process is pressed into plugins and custom snippets, because that is the tool at hand. The demo works. Then come the edge cases, the accounting integration, the second user editing at the same time, and every gap is patched with another layer. Two years later there is a system nobody dares touch, and the search begins for someone to rebuild it.

The reverse happens too: a software engineer building a simple company website tends to deliver something solid and needlessly expensive. For a site that mainly has to look good and be found, the web designer is faster and better.

How to tell who you are talking to

Ask three questions, and watch the shape of the answer:

1. “What happens when two people edit the same thing at once?” A software engineer answers immediately; it is the core of the trade. Whoever talks past it does not build systems.
2. “How do you connect to my accounting package, and what happens when that connection is down for a while?” Listen for whether the answer is about reliability, what happens during an outage, what gets recorded, or only about it being possible.
3. “Who owns the code, and can someone else continue with it?” Any serious answer is fine; no answer is the signal.

And look at the evidence. A portfolio of beautiful websites proves web design work. Whoever builds systems can show what runs in production and what it does there; asked that question, we point at our own products, software users load every day.

Sometimes you need both

Many companies need both: a website that presents the business and software that runs it. Those may be two different parties, each good at their own trade. The order that works: first know which problem you are solving, then pick the trade to match.

Not sure which category your plan falls into? That is exactly the kind of question to put to us via contact; it costs you two minutes, and you get an honest answer, including when that answer is “we are not the right party for this”.