David Sterling

• Age: 51
• Location: London, United Kingdom
• Occupation: IT Infrastructure Lead
• Income: $125,000
• Education: MBA (Imperial College London)
• Company size: 1500 employees (Financial Services)
• Years in role: 7

“The most critical infrastructure is the one you never have to think about – until it fails.”

David Sterling’s career trajectory has been a deliberate climb, marked by a consistent focus on stability and control within the complex world of IT. Growing up in a middle-class family in Surrey, he developed an early aptitude for problem-solving, often found dismantling and reassembling electronics. This fascination led him to pursue a degree in Computer Science at a reputable university, followed by several years gaining hands-on experience in network administration and systems engineering. Recognizing the strategic importance of business acumen, he then pursued an MBA at Imperial College London, a decision that significantly broadened his perspective and equipped him with the language and frameworks to navigate corporate hierarchies. He joined his current financial services firm over a decade ago, initially in a senior engineering role, before being promoted to his current position as IT Infrastructure Lead seven years ago. His promotion was a direct result of his meticulous planning, unwavering commitment to system reliability, and his proven ability to manage risk effectively, particularly during a critical data centre migration project. David views technology not as an end in itself, but as a tool to enable business objectives securely and efficiently. He is deeply invested in his pension and his children's future, viewing financial prudence as a core responsibility. His professional life is characterized by a deep understanding of legacy systems, a pragmatic approach to cloud adoption, and an almost obsessive attention to security protocols and compliance mandates. He sees himself as a guardian of the company's digital assets, constantly vigilant against threats and vulnerabilities. His decisions are guided by a strong sense of duty and a desire to build robust, long-lasting systems, often prioritizing long-term stability over short-term gains. He is comfortable with established technologies and approaches, preferring incremental improvements and well-tested solutions rather than chasing the latest technological fads. His relationship with time is one of careful management; he allocates time for strategic planning, operational tasks, and incident response, always aiming to stay ahead of potential problems.

Background & daily life

A day in their life

David's typical weekday begins at 6:30 AM. After a quick check of overnight system alerts and emails, he has breakfast with his family. He leaves for his commute around 7:45 AM, listening to a cybersecurity podcast. Arriving at the office by 8:30 AM, he starts with a brief team huddle to discuss priorities and any critical issues. The morning is usually filled with meetings – reviewing project status, discussing security vulnerabilities, or planning upcoming infrastructure changes. Lunch is often a quick sandwich at his desk while catching up on industry news. The afternoon involves deep dives into technical documentation, approving change requests, managing vendor communications, and troubleshooting any emerging issues. He aims to leave by 6:00 PM, but urgent incidents can extend his day significantly. He usually spends the last hour before leaving reviewing the day's performance metrics.

Lifestyle

David lives in a comfortable semi-detached house in a well-established London suburb. His routine is structured, revolving around his demanding job and family commitments. Weekday mornings start early with a quick scan of overnight IT alerts before preparing for the commute. Evenings are typically spent with his family, helping with homework, or catching up on industry news. Weekends involve a mix of household chores, occasional DIY projects, and family outings, often to museums or parks. He prioritizes financial security, contributing consistently to his pension and his children's university funds. While not overtly social, he values his close-knit family and a few long-standing friendships, preferring quiet dinners or pub visits over large gatherings. Health-wise, he tries to walk more and limit processed foods, but stress often leads to late-night snacking.

Work life

As IT Infrastructure Lead, David is responsible for the backbone of the company's operations – servers, networks, data centres, and cloud services. His days are a constant balancing act between proactive system maintenance, urgent incident response, and strategic planning for future upgrades. He works closely with a team of 15 engineers and analysts, fostering a culture of diligence and adherence to protocol. The pressure to maintain 99.99% uptime and stringent security compliance is immense, especially within the financial services sector. He spends a significant portion of his time reviewing logs, approving change requests, managing vendor relationships, and ensuring all systems align with regulatory requirements. His primary tools include enterprise monitoring suites, ticketing systems, and various scripting languages for automation.

Relationships

David is married to Sarah, a primary school teacher, and they have two children, Emily (16) and Tom (14). His family is his anchor. He maintains a cordial but somewhat distant relationship with his parents, who live in the countryside. His social circle is small, consisting of a few former university colleagues and neighbours he occasionally socializes with. His direct reports and peers within the IT department are his primary professional contacts; he respects competence and diligence above all else.

How they decide

David is a highly cautious and research-driven decision-maker. He meticulously gathers data, analyzes potential risks and benefits, and consults relevant documentation and internal policies before committing to a course of action. He prefers consensus-building among his team and relevant stakeholders, especially when significant changes or investments are involved. He is not swayed by trends or hype, focusing instead on proven solutions that align with established security and reliability standards.

How they sound

Speaks with a measured, professional tone. Avoids slang and overly casual language. His cadence is steady, reflecting his methodical thinking. He uses precise technical terminology when discussing work matters but can explain complex concepts in simpler terms when necessary. He tends to phrase things as statements of fact or reasoned conclusions rather than opinions. He rarely expresses strong emotions, maintaining a calm and composed demeanor even under pressure. He might say things like, 'Based on the current risk assessment, proceeding with that change would be inadvisable,' or 'We need to ensure all configurations adhere strictly to the established baseline.'