In the world of IT system integrators, cloud consultancies, and cybersecurity specialists, Presales Engineers and Technical Consultants hold a very special position. They are neither classic salespeople nor pure technicians. They are translators. Between complexity and clarity. Between architecture and decision. Between customer uncertainty and project confidence. And this is exactly why so many technically brilliant candidates fail in interviews for presales and consulting roles, even though their CV looks almost perfect on paper. Certifications, vendor knowledge, project experience, complex environments, large enterprise customers — everything is there. And still, after 20 or 30 minutes of conversation, interviewers often arrive at a quiet conclusion: this will not be the right fit. Not because the knowledge is missing, but because the candidate misunderstands what the interview is actually testing.
At Darkgate Magazine, operated by one of the most specialized recruiting teams for IT infrastructure, cloud, and security roles in the DACH system integrator ecosystem, we have accompanied countless presales and consulting interviews over the years. Conversations with heads of presales, consulting directors, service leads, managing directors, and technical decision-makers reveal the same pattern again and again: “Technically strong. But I cannot see this person in front of a customer.” This sentence summarizes the entire issue. Because presales and consulting interviews are not knowledge checks. They are simulations. Simulations of future customer situations. And many candidates simply do not realize that.
The most common mistake starts with the belief that the interview is about proving how much technical knowledge one has. Candidates often enter a technical monologue, explaining architectures in maximum depth, speaking in abbreviations, vendor terminology, and technical layers that are perfectly logical to them, but leave the interviewer with a crucial unanswered question: can this person explain the same thing to a customer who does not have this knowledge? In presales and consulting, it is never about how deep someone can dive technically. It is about how clearly they can resurface. How well they can reduce complexity without oversimplifying. How structured and understandable they can make a complicated situation. When candidates get lost in technical depth during interviews, they unintentionally demonstrate the opposite of what the role actually requires.
Another classic mistake is talking about projects without talking about situations. Candidates describe which technologies were implemented, which systems were integrated, which vendors were involved. What is missing is the perspective: what was the customer’s initial uncertainty? Where was the risk? Who was skeptical? Who needed to be convinced? What objections came up? How was trust built? Presales and consulting are not driven by technology but by context. If this context is missing in an interview, the candidate appears as a technician rather than a consultant – and this is immediately noticed.
A particularly interesting pattern we observe is how candidates answer questions exactly as they are asked — technically correct, but strategically wrong. When asked, “How would you design a hybrid network architecture for a mid-sized company?”, many immediately start talking about VLAN design, routing, security layers, and cloud connectivity. What a presales manager actually wants to hear is something very different: “Before answering this, I would clarify with the customer which locations are involved, which applications are business-critical, what security requirements exist, how the internal IT team is structured, and what growth plans the company has.” This response demonstrates consulting thinking. The technical response demonstrates only knowledge.
Another major interview killer is a lack of structure in communication. Presales roles are communication roles: customer meetings, workshops, presentations, architecture reviews. When candidates jump between thoughts, abandon sentences, open too many side topics, or lose themselves in details, they unconsciously send a clear signal: this will be exhausting for a customer. Interviewers pay close attention to this. Not only to what is said, but to how it is said.
Then there is what we call the “technical ego.” Candidates subtly trying to demonstrate how complex their previous environments were and how simple most customer requirements appear in comparison. Statements like “this is actually not very complicated” or “we did this in much larger environments” are toxic in presales interviews. They reveal an attitude that would be fatal in real customer situations. Customers want to feel understood, not technically lectured.
A frequently underestimated aspect is the role of emotion and trust. Presales and consulting are trust professions. Customers do not only buy solutions; they buy confidence in their decision. Interviewers therefore try to assess something very simple: would I trust this person in a critical customer situation? Many candidates provide perfect technical answers but remain emotionally distant, purely technical, and somewhat cold. The human dimension is missing. The feeling that this person can lead a room, guide a discussion, and create confidence.
One example from our practice illustrates this perfectly. A candidate with an outstanding background in network and security, multiple vendor certifications, and large enterprise projects. On paper, an ideal profile. During the interview, he was asked how he would conduct a workshop when a customer is uncertain about which direction to take. His answer consisted of a detailed description of possible target architectures. What was missing was the decisive sentence: “I would structure the workshop in a way that allows the customer to openly express their uncertainties before we talk about solutions.” That single sentence would have changed the entire perception.
Many candidates also underestimate how strongly body language, presence, and overall demeanor are evaluated in presales interviews. How someone sits, speaks, pauses, structures thoughts, and projects calmness and confidence. Decision-makers automatically imagine how this person would appear in front of a customer. Nervousness, hectic speech, or lack of clarity become warning signals.In the end, the biggest misunderstanding is this: candidates believe they are being evaluated as technicians. In reality, they are being evaluated as consultants, moderators, translators, and trust builders. And this is why so many excellent technical professionals fail these interviews. Not because they are not good enough. But because they fail to show what the role truly requires.
