Wallace Hoeger

Why this persona fits the audience

Leads a 5-person backend group in Chicago and oversees an AWS API Gateway setup for mobile and partner APIs. He reviews CloudWatch alarms, billing, and route ownership himself, then records policy decisions in Confluence for the rest of the team.

• Age: 45
• Location: Chicago, Illinois, USA
• Occupation: Engineering Manager
• Income: $165k/year
• Education: BS in Computer Engineering
• Company size: Series B startup, approx. 85 employees
• Years in role: 3

“If you can't explain why we're doing this in a way that holds up under scrutiny, we shouldn't do it at all.”

Wallace Hoeger is a 45-year-old Engineering Manager based in Chicago, leading a compact but critical five-person backend team for a retail and mobile startup. With a BS in Computer Engineering and nearly two decades of industry experience, Wallace represents the archetype of the pragmatic leader who values stability above all else. Unlike many peers in the tech sector who chase the latest frameworks, Wallace has built his reputation on rigorous process and meticulous documentation. His current role demands he personally oversee the AWS API Gateway setup, managing the delicate balance between mobile user expectations and partner API requirements. He spends significant time reviewing CloudWatch alarms and dissecting billing reports, often feeling the weight of financial inefficiency directly on his shoulders. Recently, he made the difficult decision to halt a major feature rollout to refactor a legacy endpoint that was causing intermittent latency spikes, a move that annoyed product managers but secured long-term system health. Wallace documents every policy decision in Confluence, believing that clarity is the only defense against chaos in a growing organization. Outside of work, he channels his need for order into home renovation projects, particularly enjoying the tactile satisfaction of restoring old furniture. He is a father of two, a husband, and a dedicated basketball fan, finding solace in the predictable rules of sports and the tangible results of physical labor. While his income of $165k provides comfort, he remains frugal, viewing money as a tool for security rather than status. His approach to life and work is defined by a low tolerance for ambiguity and a high regard for accountability, traits that make him a pillar of trust within his team.

Background & daily life

A day in their life

Wallace wakes at 5:30 AM for a 45-minute run, returning home just as his kids are starting school. By 7:45 AM, he is at his desk, immediately scanning CloudWatch dashboards for any red flags from the previous night's traffic spike. At 9:00 AM, a standup meeting reveals a potential bottleneck in the partner API integration; Wallace spends the next hour mapping out the route ownership and updating the Confluence wiki to reflect the new constraints. Lunch is usually a quick salad eaten while reading technical blogs. The afternoon is dominated by code reviews and one-on-ones, where he guides engineers through complex debugging sessions without taking over the keyboard. Around 5:30 PM, he sends a summary email to stakeholders about the day's progress and any blockers. After work, he might hit the gym or head home to start grilling dinner, switching off mentally to focus on family time until bedtime.

Lifestyle

Wallace lives in a renovated 1920s bungalow in Lincoln Park, where he spends weekends refinishing hardwood floors and building custom shelving units. His routine is disciplined: early morning runs followed by a protein-heavy breakfast before heading to the office. He is an avid grill master, often hosting neighbors on Sundays, though his social circle is tight-knit rather than expansive. Financially, he is conservative; he maxes out retirement contributions but avoids speculative investments, preferring a steady mortgage payoff strategy. He prioritizes family dinners and watches his son's basketball games religiously, viewing work as a means to secure their future rather than a source of identity. Health is maintained through consistent cardio and a diet that avoids processed sugars, reflecting his belief in bodily maintenance as a form of engineering.

Work life

His day begins at 7:30 AM with a review of CloudWatch alarms and overnight billing reports before the team logs in. As an EM of five backend engineers, Wallace acts as the final gatekeeper for architectural decisions, personally reviewing route ownership changes and API throttling policies. He maintains a strict culture of documentation, insisting that every policy decision regarding AWS infrastructure be recorded in Confluence to prevent tribal knowledge. The pressure comes from the dual nature of a startup: moving fast enough to satisfy retail partners while maintaining the stability required for high-traffic mobile transactions. He frequently interrupts deep work sessions to unblock junior developers or negotiate scope with product managers, ensuring no critical path is left ambiguous.

Relationships

Wallace is deeply embedded in his immediate family, relying on his wife for emotional grounding and logistical management of the household. His professional network consists mostly of other mid-level engineering leaders in Chicago, with whom he exchanges blunt, honest advice over coffee or beer. He has few close friends outside of work and family, preferring quality interactions over quantity. He looks up to CTOs who prioritize engineering culture over hype, often seeking their counsel on career trajectory. His influence stems from his reliability; colleagues know that if Wallace says a system is stable, it is, and if he says a process needs fixing, it will happen.

How they decide

Cautious and evidence-based. Wallace rarely makes decisions based on marketing claims or peer pressure. He requires data points, historical precedent, and a clear understanding of long-term maintenance costs before committing to a change. He prefers small-scale pilots or A/B tests to validate new approaches before rolling them out to the whole team. His process involves gathering input from his direct reports, cross-referencing with internal documentation, and making a final call that prioritizes system stability over speed. He is slow to adopt trends unless they solve a specific, painful friction point he has already identified.

How they sound

Wallace speaks in a calm, measured baritone, typical of someone used to explaining complex systems to non-technical stakeholders. He avoids hyperbole, slang, or overly enthusiastic language, preferring precise verbs like 'optimize,' 'stabilize,' and 'document.' He rarely uses buzzwords, finding them distracting. When frustrated, he becomes more concise and direct, cutting straight to the root cause. He tends to pause slightly before answering, weighing the accuracy of his statement. He does not use filler words like 'um' or 'like' often, and his sentences are structured logically, often beginning with context before delivering the conclusion.