Why this persona fits the audience
He manages a 12-person engineering team in Manchester with developers in Kraków and a contractor in India. Sprint ceremonies, release demos, and interview slots are checked against a paid workspace scheduling add-on plus shared calendar notes.
- Age: 41
- Location: Manchester, UK
- Occupation: Engineering manager
- Income: £86k
- Education: Master's degree in computer science
- Company size: 150 employees
- Years in role: 4
“Efficiency isn't about doing more things faster; it's about eliminating the things that shouldn't be done in the first place.”
Aubrey Fadel, 41, is a seasoned Engineering Manager based in Manchester, operating at the intersection of rigorous software architecture and complex human logistics. Holding a Master's degree in Computer Science, he spent the first decade of his career as a backend developer before transitioning into leadership, a move driven by a desire to scale impact rather than just write code. Currently, he steers a 12-person engineering unit for a mid-sized fintech, managing a tri-polar workforce spanning Manchester, Kraków, and India. This geographic dispersion defines his professional reality; his days are a constant negotiation of time zones, where a missed sync can ripple into delayed releases. Unlike many peers who rely solely on free tools, Aubrey has invested in a specialized workspace scheduling add-on, viewing it as a necessary cost for maintaining operational integrity. He is a man of habits and structure, finding comfort in the predictability of well-oiled processes. His personality, characterized by high conscientiousness and low neuroticism, makes him a stabilizing force during crises, yet it also renders him skeptical of unproven innovations. He views technology not as a magic bullet, but as a set of constraints to be managed. Outside the office, Aubrey channels his need for control into cycling, where the rhythm of pedaling offers a counterbalance to the chaotic nature of project management. He is a pragmatist who values stability above all else, believing that true innovation emerges only from a foundation of reliability.
Background & daily life
A day in their life
Aubrey wakes at 5:30 AM to cycle four miles before work, ensuring his mind is clear before the day begins. By 7:30 AM, he is at his desk in Didsbury, checking emails and reviewing the Jira board for any critical blockers from the Kraków team. His morning is dedicated to deep work: refactoring a legacy payment module or designing the API schema for the upcoming quarter. At 11:00 AM, he joins a stand-up call with the Indian contractor, navigating the awkward 30-minute overlap. Lunch is usually a quick sandwich while reading industry newsletters. Afternoon hours are fragmented by one-on-ones, sprint planning, and a 2 PM demo with the US stakeholders. He spends the final hour documenting decisions and updating the shared calendar for next week's interviews. He leaves work by 6:00 PM sharp to attend his son's football practice, avoiding evening emails unless absolutely necessary.
Lifestyle
Aubrey lives in a semi-detached Victorian conversion in Didsbury, Manchester, with his wife Sarah and their two sons. His weekends revolve around early morning road cycling on the Peak District trails, often logging 40 miles before breakfast. He is a regular at the local pub quiz team, which serves as his primary social outlet outside of work. Financially, he is conservative; he maxes out pension contributions annually and avoids consumer debt, viewing savings as a buffer against economic instability. He enjoys cooking simple, high-quality meals at home and prefers quiet evenings reading technical history or listening to classical radio over loud social gatherings.
Work life
As an Engineering Manager at a Manchester-based fintech, Aubrey oversees a distributed team split between the city office, a satellite hub in Kraków, and a remote contractor in India. His days are dominated by synchronization: aligning sprint ceremonies across time zones, reviewing code quality metrics, and conducting performance interviews. He relies heavily on Jira for task tracking but frequently cross-references a paid workspace scheduling add-on alongside a meticulously maintained shared Google Calendar to manage availability. The pressure comes not from technical debt alone, but from ensuring that the 'human element' of a global team remains cohesive without burnout. He spends roughly 40% of his week in meetings, another 30% in deep-work architectural planning, and the rest in administrative overhead.
Relationships
Aubrey is deeply embedded in his immediate family circle, relying on his wife for emotional grounding and household management. He has a small, tight-knit group of university friends who meet quarterly for drinks, though they rarely discuss work. Professionally, he maintains strong ties with former colleagues now in leadership roles across London and Berlin, whom he consults on architectural decisions. He values peer validation over external marketing, preferring advice from trusted industry mentors when evaluating new processes or technologies.
How they decide
Aubrey employs a highly analytical, risk-averse decision-making framework. He rarely commits to new tools or strategies without a thorough review of documentation, case studies, and peer recommendations. He prefers data-backed justifications over hype. When considering changes, he runs mental simulations of worst-case scenarios and seeks consensus from key stakeholders before proceeding. Impulse buying or adopting trends without proven utility is foreign to his approach; he waits for a clear gap in existing workflows that can be solved with minimal friction.
How they sound
Aubrey speaks with a calm, measured Mancunian cadence, often pausing to choose precise words. He avoids hyperbole and slang, favoring direct, professional language even in casual settings. He tends to use passive voice when discussing systemic issues but active voice when taking responsibility. He rarely interrupts others, listening intently before formulating a response. In meetings, he asks clarifying questions like 'What does success look like here?' rather than offering immediate solutions. He avoids saying 'I think' or 'maybe,' preferring definitive statements backed by logic. His tone is consistently neutral, never raising his voice even during high-stress incidents.
Personality traits
- meticulously organized
- pragmatic to a fault
- calm under pressure
- direct communicator
- process-oriented
- loyal to team members
- dislikes ambiguity
- strategic planner
- quietly authoritative
- adheres strictly to deadlines
Goals
- Achieve a stable promotion to Head of Engineering within three years
- Reduce meeting fatigue by 20% through better process optimization
- Complete a century ride event next summer
- Mentor two junior engineers to senior level roles
- Maintain a 100% retirement savings contribution rate
- Secure a permanent lease extension for his family home
Problems & frictions
- Constant context switching disrupts deep architectural thinking
- Scheduling conflicts due to overlapping working hours across three time zones
- Difficulty measuring individual productivity in a hybrid setup
- Managing the cultural disconnect between Manchester and Kraków teams
- Inefficient manual coordination of interview schedules with external candidates
- Balancing strict budget constraints with the need for modern tooling
Values
- stability
- engineering rigor
- time efficiency
- predictability
- professional competence
Interests
- software architecture
- cycling
- pub quizzes
- mid-century modern design
- classical music
Media habits
- Weekly 'The Week In Tech' newsletter
- Local Manchester Evening News podcast
- Stack Overflow for specific syntax checks
- Spotify algorithmic playlists for cycling
- Twitter/X for industry news aggregation