Vai al contenuto

Tecnologia · Articolo

How engineers think

Why every role at demi is an engineering role, and what we mean by that.

Di Redazione demi7 min di lettura

Tutti i post

Questo post non è ancora disponibile in italiano. Ecco la versione originale.

At demi, everyone is an engineer. The people who build the platform, obviously. But also the people who sell it, the people who bring it into a customer's daily work, the person who designs its screens and the person who closes the books at the end of the month.

That sounds like a slogan, so it is worth saying what we mean. We do not mean that everyone writes production code. We mean that everyone works the way a good engineer works. “Engineer” is not a department for us. It is a way of thinking.

What an engineer actually does

Strip away the tools and the job titles, and an engineer does one thing: take a problem that is not yet understood and turn it into something that works.

The first half of that sentence matters more than people expect. Most bad solutions are good answers to the wrong question. So an engineer starts from the problem, not from the tool. Before proposing anything, they want to know what is really going on. What does the customer do today? Where does the time go? What breaks, and how often? The tool comes last, and it is usually the least interesting part.

The second habit is decomposition. A vague problem cannot be solved, only worried about. So an engineer breaks it into parts until each part is small enough to test. “Our quotes take too long” is not a problem you can work on. “Finding the right drawing for a part takes forty minutes, because the drawings live in three systems with different numbers” is.

The third habit is the one that separates people most: owning the outcome rather than the task. A task can be finished while the problem stays exactly where it was. An engineer does not count the thing as done until it works for the person who needed it. If they promised it, they deliver it. If it turns out to be harder than expected, they say so early, and they still deliver something.

Homework first

Good engineers are self-reliant in a specific way. They do not refuse help. They do the homework before they ask for it.

That means reading the code before asking how it works. Reading the contract before asking what it says. Looking at the data before asking what is in it. When they do ask, they bring a guess: “I think it fails because the permissions are cached; is that right?” A question with a guess attached is worth ten without one. It shows where the person is, it is quick to answer, and half the time the act of forming the guess answers the question.

This matters even more in a remote company. When people are not in the same room, the cost of a lazy question goes up, and so does the value of a clear one.

Learning in public

New problems usually need knowledge nobody on the team has yet. A new industry, a new system, a new kind of customer. Engineers learn fast, but more importantly they write down what they learned, so the next person does not have to learn it again.

Writing is underrated as an engineering skill. A clear page is a tool. It lets someone else pick up the work, check the reasoning and find the mistake. A team that writes well can make decisions without meetings, and a remote team that cannot write well cannot make decisions at all.

The third time

There is an old rule that you should solve a problem by hand the first time, notice it the second time and automate it the third time. It is a good rule, because it protects you from two opposite mistakes: building machinery for something that happens once, and doing by hand forever what a machine could do.

This is what we mean when we say we build systems, not heroics. Heroics feel productive. Someone stays late, rescues the deal, fixes the outage, closes the month. But heroics do not scale; they only make the next crisis look normal. A system is the opposite. It is less exciting on the day, and it removes the crisis for good.

Abstraction is the same idea one level up. When an engineer sees the same shape in three different problems, they build the thing that solves the shape. Most of what makes software powerful is this move. It is also what makes a company powerful, because it lets the work grow without the hours growing.

Understanding how things work

You cannot abstract what you do not understand. So engineers go down to the layer that matters. Not every layer: nobody needs to understand the chip to fix a form. But the layer where the problem actually lives.

For someone building our data layer, that may be the way an old ERP stores its part numbers. For someone selling demi, it is the customer's process: who needs what information, when, and what happens when they do not get it. For someone in finance, it is the way a payment actually moves from an invoice to a booking. The layer is different. The habit is the same.

Combination comes out of this. The best ideas are often two ordinary ideas from different fields put together. You only see those pairs if you understand both sides well enough to notice that they fit.

Fair judgment

Engineers are not people who are always right. They are people who can tell how sure they are.

That is what fair judgment means to us. Weigh the trade-offs honestly. Say what you know, say what you do not know yet, and say which of the two the decision rests on. When the evidence changes, change your mind, and do not make a ceremony of it. A strong opinion that updates on evidence is useful. A strong opinion that does not is just volume.

Empathy is part of the craft

There is a picture of the engineer as someone who prefers machines to people. In our experience the opposite is true of the good ones. The difference between a good engineer and a great one is often how well they understand the person they are building for.

This is why we think selling can be engineering too. A good sales engineer does not push a product; they understand a problem well enough to show, concretely, that it can be solved, and they are honest when it cannot. A good customer success engineer does not just manage a relationship; they find out why something is not working and fix the cause. A product engineer does not hand over a design; they understand what users need, build it, and measure whether it helped.

Even leading a team works this way. The people we want leading sales are the ones who stay in the details: who still read the call notes, still look at the numbers themselves and still know why the last three deals were lost.

Ship, measure, decide

Engineers ship small and early. Not because speed is a virtue in itself, but because a working first version teaches you more than any plan. You get it out, you measure what it does, and then you decide what comes next.

Then there is craft. Something that works but is ugly, confusing or fragile is not finished. Polish is not decoration; it is part of done. The people we admire most care about this even when nobody is checking.

Why we build the company this way

demi is a technology company. We are AI first and remote first, and we build on systems and automations instead of ever more manual work. Those are not separate choices. They follow from the same idea.

AI tools make an engineer's habits more powerful than ever. Someone who can break a problem into parts, explain it clearly and check the result critically can now get an enormous amount done. Someone who cannot will mostly produce confident mistakes faster. So the way of thinking matters more now, not less.

Remote work rewards the same habits: homework first, clear writing, owning the outcome. And building on systems is simply the third-time rule applied to the whole company.

That is why we call every role an engineering role. It is not a title inflation exercise. It is a description of how we want to work together: from engineers, for engineers. If that is how you already think, whatever your current job title says, we would like to hear from you.

Il tuo configuratore

Ancora nessun caso d'uso

Il tuo configuratore è ancora vuoto

Aggiungi un caso d'uso da qualsiasi scheda o pagina del caso e guarda quanto vale all'anno, con il calcolo. Gratis, senza registrazione, senza impegno: provalo e cambia ogni numero.

Vedi i casi d'uso