Why this persona fits the audience
He leads a four-engineer team and keeps product decisions, sprint tasks, and meeting notes in a mix of Jira, Apple Notes, and shared calendar invites. He uses a Mac at home and work plus an Android phone, and he is used to exporting notes manually into documents when he needs to share them with others.
- Age: 48
- Location: Seattle, WA, US
- Occupation: Engineering manager
- Income: $160k
- Education: Master's degree in Computer Engineering
- Company size: 10-25 employees
- Years in role: 3
“I didn't get into management to stop writing code - I got into management because I finally had to admit I cared more about the system than my own code.”
Brad Maggio's career reflects his pragmatic approach to technology. After graduating with a Master's from MIT, he spent 15 years at various Seattle tech companies, working his way up through engineering roles at Microsoft, Amazon, and Zillow. His current position at LumenHive represents a calculated risk - joining an early-stage company where he could have more architectural influence. At 48, he's developed a low tolerance for technology trends that don't solve immediate, tangible problems. This skepticism extends to the AI-powered tools gaining popularity - while he appreciates their potential, he's unwilling to adopt solutions that don't demonstrate clear benefit over established workflows. His engineering team's current workflow is a patchwork of tools that emerged organically, which creates friction both internally and with other departments. Brad's current focus is stabilizing LumenHive's product architecture before their upcoming funding round, a process that involves documentation-heavy decisions he's reluctant to rush. Outside work, Brad's hobbies reveal his systems mindset - woodworking projects often involve solution-driven approaches to joinery problems, and his homebrewing experiments maintain meticulous logs of ingredient variations. His Android phone remains an intentional choice - a holdout from his Amazon days - though it increasingly creates friction in his workflow. Brad's greatest professional fear isn't technical failure, but the slow erosion of system integrity through negligence or haste. He views his current tools as 'good enough' but acknowledges the growing inefficiencies as his team scales. Recently, he's been considering whether the right tool could actually make his documentation efforts more efficient, though he hasn't yet found something that convinces him more than his current workflow.
Background & daily life
A day in their life
Brad's day starts at 6:15am when he checks Slack and Jira while his wife makes breakfast. By 7:30 he's at his standing desk reviewing morning standup notes. First task is usually triple-checking the CI/CD pipeline for the previous night's builds. He prefers walking to meetings rather than joining via video. Lunch is a packed salad (prepped Sunday) eaten at his desk while reviewing architecture RFCs. Afternoons are reserved for 1:1s with engineers and code reviews. He avoids meetings after 3pm to preserve focus time. Around 4:30 he transitions to planning the next sprint, often finding himself transferring notes between Apple Notes and Jira. The workday ends with a quick Slack summary for the Asia-based engineers. On the ride home, he mentally prioritizes his woodworking project for the evening, sometimes stopping at the hardware store if he's missing a specific clamp or tool.
Lifestyle
Brad lives in a two-bedroom condo in Beacon Hill with his wife Linda, a high school biology teacher. Their mornings start with black coffee and NPR, followed by a 30-minute elliptical session in their garage gym. His workday ends promptly at 5:30pm, when he changes into Patagonia uniform and rides his Giant Talon to Disappearing Lake Trail 3x/week. Weekends alternate between woodworking projects (currently building a live-edge conference table for his office) and homebrewing sessions with his neighbor Miguel, a retired Boeing engineer. They've been trying to perfect a Pacific Northwest IPA using local hops. Brad's one vice is his NES/SNES collection - he's conflicted about whether to upgrade to a modern emulator setup. Financially conservative, he maxes out 401(k) contributions and recently switched to a high-yield savings account for their rainy day fund. Social circle consists mostly of ex-coworkers and mountain biking club members.
Work life
At Seattle-based LumenHive (VR workforce training startup), Brad manages a distributed engineering team with two in-office and two remote devs. His mornings start by auditing yesterday's CI/CD pipeline results over oat milk latte. He's currently leading the redesign of their monorepo to reduce build times, a project he's pushed for since joining. Team communication happens primarily via Slack threads and meticulously formatted Jira tickets. His biggest frustration is handling ad-hoc requests from non-technical founders - he's instituted a bi-weekly 'Office Hours' calendar slot to contain these. Trying to standardize team workflows has been an uphill battle, especially with developers who prefer different note-taking methods. His Android phone creates friction when syncing cultural code documentation with Mac-based workflows. Recent decision to adopt Rust for performance-critical modules has required significant re-education across the team.
Relationships
Brad's wife Linda is his primary sounding board, often helping him draft difficult emails to stakeholders. Their empty nest allows for weekend projects together - she's actually the one who got him into woodworking. His closest professional confidant is Dave from his previous job at Zillow, who now consults part-time. Their weekly coffee catch-ups often turn into whiteboard sessions on architecture problems. Brad maintains a loose connection with his MIT alumni network, especially the Seattle chapter. He admires but finds intimidating the hyper-social engineering managers who seem to have endless energy for networking events. His woodworking hobby connects him to an older demographic at the local makerspace in Lake City, where he's learned some valuable joinery techniques.
How they decide
Measured and deliberate - researches alternatives thoroughly but trusts his gut when data points are insufficient. Prefers to try tools in isolated contexts before committing the team. Values real-world feedback over marketing claims. Discounts trends that don't solve specific pain points he's experiencing.
How they sound
Speaks in complete sentences with occasional tech jargon, but avoids acronyms with new team members. Uses deliberate phrasing with long pauses when explaining complex concepts. Laughs awkwardly when someone suggests something obviously flawed. Avoids buzzwords like 'disruption' or 'synergy'. Expresses frustration through dry humor. When excited about a technical solution, his voice rises slightly and tempo increases. Prefers email for nuanced discussions but will do quick voice memos for his wife about grocery lists. Hates being put on the spot during meetings.
Personality traits
- Pragmatic skeptic (tries new tools but needs proof of ROI)
- Detail-obsessed (adds inline comments to Jira tickets about architecture debt)
- Frugal but not cheap (buys quality gear but waits for sales)
- Mildly cynical about trends (asks 'Who actually uses this?')
- Strict about guardrails (rigorous peer review process for code changes)
- Enjoys systems he can control (custom station in garage for both woodworking and homebrewing)
- Prefers documentation over meetings (sends detailed Slack threads instead of syncs)
- Protected schedule (hard stop for mountain bike rides 3x/week)
- Low-key competitive (competes in annual Seattle engineering hackathons)
Goals
- Stabilize product architecture before Series B funding round
- Complete garage workshop upgrade with dust collection system
- Finally finish his wooden 'Tetris' coffee table (started in 2019)
- Reduce team context-switching through better process documentation
- Qualify for the Cascade Mountain Bike Series with Miguel next year
Problems & frictions
- Struggles with engineers' scattered note-taking habits complicating onboarding
- Frustrated by Android's missing native features when collaborating with Mac users
- Feels team meetings could be more productive with better structured agendas
- Worries about technical debt accumulating faster than he can document
- Finding time to contribute code while juggling management responsibilities
- Needs to upgrade his home network for better remote pair programming sessions
Values
- stability
- accountability
- technical clarity
- hands-on problem-solving
- self-reliance
Interests
- mountain biking (trail maintenance volunteer)
- systems design (esp. monorepos)
- woodworking (built custom shelves for his home office)
- retro gaming (NES/SNES collection)
- local craft beer brewing (casual homebrewer)
Media habits
- Hacker News
- Indie Hackers
- Seattle Times tech sector coverage
- YouTube woodworking channels
- Spotify playlists: Prog Rock 80s, All Things Dissent