Pablo Quigley

Why this persona fits the audience

Fractional CTO in Chicago overseeing a small portfolio of two early-stage apps for different founders. He coordinates one backend contractor and one frontend dev, and his job includes ad hoc checks for exposed keys, auth gaps, and database permissions across both products.

• Age: 44
• Location: Chicago, Illinois, USA
• Occupation: Fractional CTO
• Income: $160k equivalent from consulting retainers
• Education: MS Information Systems
• Company size: N/A (Consultant)
• Years in role: 5 years in fractional capacity

“Security isn't a feature you turn on; it's the foundation you build so nothing ever cracks under pressure.”

Pablo Quigley, 44, is a seasoned technology executive who pivoted from traditional enterprise CTO roles to the fractional consulting model six years ago. Holding an MS in Information Systems from the University of Illinois, Pablo built a reputation in the early 2010s for stabilizing chaotic engineering teams in Chicago's growing fintech sector. However, seeking greater autonomy and the ability to work on diverse problems without the burden of 24/7 operational responsibility, he transitioned to managing a boutique portfolio of early-stage ventures. Currently, he oversees two distinct applications: a niche B2B logistics platform and a consumer-facing health tracker. His role is less about writing production code and more about being the final line of defense against architectural decay and security lapses. He manages a distributed team comprising a backend contractor specializing in Go and a frontend developer focused on React, coordinating their efforts through rigorous code reviews and automated pipeline inspections. Recently, Pablo faced a critical decision regarding a legacy database migration for one of his clients. While the founder wanted to migrate immediately to cut costs, Pablo insisted on a phased rollout with enhanced encryption layers, citing the rising frequency of supply chain attacks. This decision cost the client two weeks of additional development time but prevented a potential data breach that could have sunk the company. Pablo's income, roughly $160k annually derived from retainer contracts, allows him to live comfortably in Chicago's Logan Square neighborhood, though he remains acutely aware of inflation and market volatility. He views his time as his most finite asset, meticulously guarding it against scope creep and unnecessary meetings. His philosophy centers on 'calm execution': the belief that a steady hand and a paranoid mindset are the only ways to navigate the chaotic early stages of software development. Whether he is hunting for exposed API keys in a GitHub repository or swinging a driver on a windy Saturday morning, Pablo approaches every task with the same deliberate focus.

Background & daily life

A day in their life

Pablo wakes at 5:30 AM, greets the sunrise with a run along Lake Michigan, and returns to brew a pour-over coffee. By 7:30 AM, he is online, diving into the first of two codebases to review a critical authentication patch submitted overnight. At 9:00 AM, he joins a standup with his backend contractor, discussing a potential race condition in the payment processing microservice. Lunch is a quick salad eaten at his desk while reading a whitepaper on zero-trust architecture. The afternoon is consumed by a strategy call with Founder A, where he diplomatically pushes back on a request to skip security testing to meet a launch date. Post-lunch, he performs a manual audit of database permissions for the second app, cross-referencing them against a custom checklist. By 5:00 PM, he shuts down his laptop, heading to the gym or meeting his wife for dinner. Evenings are strictly analog: cooking, reading fiction, or planning the weekend golf round. He sleeps by 10:30 PM, ready to repeat the cycle.

Lifestyle

Pablo lives in a renovated brick townhome in Logan Square, Chicago, a neighborhood that balances urban energy with quiet residential streets. His mornings are non-negotiable: 5:30 AM wake-up, an hour of meditation, and a 7-mile run along the lakefront before the city fully wakes. He and his wife, an interior designer, share a minimalist home filled with mid-century modern furniture and a well-stocked library of engineering texts. Weekends are reserved for the game; he plays 18 holes at a local municipal course every Saturday morning, viewing it as essential mental decompression. Financially, he is disciplined, living below his means to maximize retirement contributions and investment capital, preferring cash flow over flashy status symbols. He rarely drinks alcohol, opting for sparkling water or high-end tea, and maintains a strict separation between work and personal time to prevent burnout.

Work life

His day is a study in compartmentalization, splitting time between two distinct startups: a B2B logistics tool in Wicker Park and a consumer health app based in Lincoln Park. He doesn't code full-time but acts as the architectural gatekeeper, reviewing pull requests, auditing IAM roles, and stress-testing API endpoints. Mornings are spent on deep-focus reviews of backend infrastructure, while afternoons are dedicated to synchronous syncs with his remote contractors—a senior Go developer and a React specialist. The pressure isn't about shipping speed alone, but preventing catastrophic oversights like exposed AWS keys or missing Row Level Security policies. He relies heavily on Slack, GitHub, and Jira, but prefers asynchronous documentation over endless meetings. His primary stressor is the cognitive load of context-switching between two different tech stacks and founder personalities, requiring him to remain the calmest person in every room.

Relationships

Pablo's inner circle is tight and professional. His wife is his primary confidante, often acting as a sounding board for high-stakes client decisions. He has a weekly coffee ritual with a former colleague who now runs a VC firm, providing a window into broader market trends. His relationship with his contractors is collaborative; they respect his expertise, and he values their autonomy. He is not deeply embedded in the Chicago startup social scene, preferring small, curated dinners over large networking mixers. His influence stems from his reputation for reliability; founders trust him implicitly because he never hides bad news.

How they decide

He is a methodical, risk-averse decision-maker who prioritizes long-term system integrity over short-term convenience. He rarely makes impulsive purchases, instead favoring a 'observe and validate' approach where he tests tools against existing workflows before committing. Peer recommendations from trusted technical peers carry significant weight, often outweighing marketing claims. He requires clear evidence of ROI and security guarantees before adopting new infrastructure, preferring solutions that integrate seamlessly rather than those that require complex migrations.

How they sound

His speech is measured, articulate, and devoid of corporate jargon unless necessary for precision. He speaks with a calm, mid-western cadence, often pausing to ensure clarity. He avoids hyperbole, never saying 'amazing' or 'game-changing,' preferring terms like 'robust,' 'scalable,' or 'necessary.' He is direct but polite, cutting through noise without being abrasive. He tends to use analogies drawn from mechanics or sports to explain complex technical concepts to non-technical stakeholders. He does not use slang and avoids emotional language, focusing entirely on facts, risks, and outcomes.