ronutz

The Roles · Who sells it

Systems engineer

Held this role - at two vendors, the second on a carrier account, 2004-2005, 2009-2010

The technical half of a vendor sales team. A systems engineer owns whether the proposed thing will work, while the account manager owns whether it will be bought. The pairing is deliberate and the split is clean: one person carries the commercial relationship and the other carries the technical truth, and both answer for the same deal.

What the day looks like

  • Qualifying an opportunity technically: what the customer runs today, what they are trying to reach, and whether the product genuinely gets them there.
  • Designing the proposed solution and writing it down in a form the customer's engineers will accept and the customer's finance will approve.
  • Running a proof of concept in the customer's environment, against the customer's traffic, with the customer's people watching.
  • Answering a request for proposal, which is a written examination with a commercial consequence.
  • Briefing the account manager on what the technology will and will genuinely do, so that the commercial promise matches the engineering one.

What it answers for

  • The technical accuracy of everything proposed under the account manager's name.
  • The design surviving contact with the customer's environment.
  • The proof of concept demonstrating the thing it claimed to demonstrate.

What it is measured on

  • Revenue on the account, shared with the account manager.
  • Opportunities advanced through the technical stages of the pipeline.
  • Proof-of-concept outcomes, and increasingly customer satisfaction after the sale.

Who it receives from

The account manager
The opportunity, the commercial shape, and the deadline.
Product management
Roadmap, positioning, and the honest limits of the current release.
The customer's engineers
The environment as it actually is, which frequently differs from the environment as documented.

Who it serves

The customer's technical staff
A design they can operate, and answers they can verify.
The account manager
Technical confidence the commercial position can stand on.
Professional services
A design that survives implementation, and a handover that says what was promised.

Who else has a stake

  • The customer's procurement and finance functions, whose questions are commercial and whose answers depend on technical facts.
  • The channel partner, when the deal transacts through one.
  • The vendor's support organisation, which inherits whatever the design turns out to be.

What it takes

  • Depth in the product, and enough breadth in everything around it to be credible about the whole system.
  • Writing that a stranger can act on, because the design outlives the conversation that produced it.
  • The judgement to say when the product fits the problem, which protects the account far more than an eager answer does.
  • Comfort presenting to a room where some people want the project and some people want it to fail.

What the job turns on

The role answers for accuracy and is measured on revenue, and those two lists point the same way only while the truth is favourable. The systems engineers who last are the ones who say early and plainly when the product fits the problem partially, because a deal won on an overstated fit becomes a support case, then a renewal risk, then a reference the vendor stops offering. The honest answer is the commercially durable one, and it is worth having that clear before the pressure arrives rather than during it.

Where it leads

Roles that lead here

The work itself

The Practice covers how this work is done — triage, escalation, evidence, handover — across the whole corpus.

Read The Practice