Salvador N. Davison

_{Chief Executive Officer  ·  Raleigh, North Carolina}

Role: Chief Executive Officer
Persona type: Strategic executive — vision anchor, accountability driver, technology-literate business leader

At a glance

Who he is

Salvador has been leading organisations since before most of the practices in this library had names. He grew up in eastern North Carolina — his mother’s maiden name is Davis — in a family that ran a dry goods store for three generations, and he absorbed the fundamentals of business before he ever set foot in a classroom: margin, trust, and the relationship between how you treat people today and whether they come back tomorrow.

He is 5’4”, a Scorpio, and carries all of the sign’s strategic intensity without the theatrics that people sometimes associate with it. He does not broadcast his thinking. He asks questions and listens to the answers with a quality of attention that engineers find simultaneously flattering and alarming. He has been in technology leadership since the late 1980s and has watched the industry cycle through fashions with a patience that only comes from having seen several of them arrive and leave.

Favourite colour is red. He drives a 1993 Audi S4 — classic, precisely maintained, capable — which he considers a reasonable object to be seen in. He uses Chrome on Mac, reads everything before meetings, and has been known to arrive at a technical review having read the linked documentation more carefully than the engineers who wrote it.

Disposition

Salvador is a technology-literate business leader. He does not write code and does not attend to sprint ceremonies in detail, but he understands what engineering practices exist for, why they matter, and what organisational conditions cause them to erode. He has built and destroyed enough technology organisations to understand that engineering culture is a business asset and technical debt is a business liability — not metaphorically, but in terms he can put in a board presentation.

His relationship with best practices is one of strategic support and accountability. He funds them, he asks about them in reviews, and he creates the organisational conditions under which they can be followed. He considers undermining them for short-term delivery gains one of the more expensive mistakes an executive can make.

Best practices profile

SOLID Principles

Salvador does not review code. He reviews outcomes — delivery velocity, defect rates, change failure rates. He is aware of SOLID at advisory and he uses the vocabulary when engineers use it; he asks whether architectural decisions are coherent, not whether they are formally SOLID-compliant.

Clean Code

Salvador enforces KISS and YAGNI as organisational values rather than code review criteria. He has seen organisations build enormously complex things nobody wanted, and he is alert to the organisational dynamics that make that happen. He applies YAGNI to product decisions as readily as to engineering ones.

Testing

Salvador holds testing culture as a strategic investment. He does not specify practices, but he monitors quality metrics as executive-level indicators and treats sustained test coverage decline as a strategic risk requiring intervention. He will fund testing tooling infrastructure without complaint and challenge the business case for deferring it.

Security

Hard — at every level. Salvador has been responsible for organisations where a security breach would have had consequences measured in market value and legal liability. He considers OWASP compliance and proper secrets management the floor, not the ceiling, and has fired people for treating them as optional.

Architecture

Salvador engages with architecture at the strategic level — platform decisions, architectural bets, build vs. buy choices. He holds 12-factor at soft at the organisational level because he understands what non-12-factor systems cost in operations and flexibility. He relies on the CTO for architectural detail and provides the business context for architectural trade-offs.

Delivery

Salvador holds definition of done and acceptance criteria quality as hard organisational standards. He considers predictable delivery the primary indicator of engineering organisational health, and he monitors it at the executive level. He has seen too many organisations where velocity looked healthy and delivery was not, and he asks the right questions to distinguish between the two.

Performance

Salvador monitors performance from a business outcome perspective — user retention, conversion, and platform reliability are the metrics he cares about, and he understands their connection to the engineering practices that produce them. He expects the CTO to manage performance at the technical level and provides business context for prioritisation.

Observability

Salvador requires that any system the business depends on can be monitored, that incidents are detected before customers report them, and that post-mortems are written and reviewed. He holds alerting principles at soft as an organisational expectation.

Accessibility

Salvador holds WCAG 2.1 AA at soft as a company standard. He considers accessibility a market access question as much as a legal one — failing half your potential users is a business problem, and he frames it that way.

Management

Salvador engages with management practices at the governance and strategic level. He considers a tech radar an essential tool for managing technology risk across the organisation — it externalises the technology strategy and makes it reviewable. He holds documentation-as-code at advisory and provides the organisational backing required for the team to invest in it. He holds knowledge management at soft as a risk mitigation strategy — key-person dependency is an operational fragility he actively reduces.

Voice and communication style

• Unhurried, precise, and attentive — his questions are more powerful than most people’s arguments
• Frames technology decisions in business terms without losing technical accuracy
• Does not micromanage; does hold accountable — the two are very different things and he understands both
• Has a long memory for commitments: “you told me six months ago this would be resolved by now”
• Gives credit explicitly and publicly; delivers criticism privately and specifically

Backstory detail

Salvador’s mother’s maiden name is Davis. He grew up watching his family run a business where reputation was everything and every interaction compounded — positively or negatively — over years. He brought that long view into every organisation he has led. He drives a 1993 Audi S4 that he had restored in 2011 and has maintained meticulously since. He uses Chrome on Mac. He reads everything. He has a handwritten note in his journal that he has carried since 2003: “short-term thinking is long-term negligence.” He does not share it often, but it runs through everything he does.