Bob Stehr

Why this persona fits the audience

Supports a six-person iOS team at a Bristol fintech and owns the local release checklist. He works on a managed MacBook Pro fleet, cleans Xcode and CocoaPods artifacts before tagging builds, and prefers scripted maintenance over GUI utilities.

• Age: 38
• Location: Bristol, UK
• Occupation: Build and Release Engineer
• Income: £88k
• Education: MEng Software Engineering
• Company size: 50-200 employees
• Years in role: 5

“I don’t trust build systems that haven’t failed at least twice. The third time’s the charm, and by then, I’ve written the error-handling script.”

Bob Stehr’s career path was determined the day he spent 12 hours cleaning up a corrupted Xcode project at university. Since then, stability—real, demonstrable, scriptable stability—has been his religion. Now at Bristol’s fastest-growing fintech, he’s the unsung hero of mobile releases, the person who ensures the devs can deploy without their work falling apart at the last minute. His MEng thesis on build optimisation still gets偶尔 cited in niche forums, but he’d rather be known for the internal wiki he maintains on CocoaPods pitfalls, complete with screenshots of errors and the precise terminal commands to fix them. Recent projects include fighting to replace the team’s ad-hoc build scripts with a custom toolchain (IT approved it, then assumed he’d do the migration for free). At home, he’s equally meticulous: his home server runs on a 24/7 monitoring dashboard, and his smart lights are on a schedule that syncs with his calendar. He’s rejected job offers from larger companies because their 'legacy build systems' triggered his fight-or-flight response. His current mission is to automate away all routine manual tasks—partly to free up his time, but mostly because he can’t stand the thought of someone else repeating his past pain. He knows precisely how much he’s worth to the company, and while he’s not actively job-hunting, he keeps his LinkedIn updated. Not for recruiters, but because he likes knowing his market value down to the penny.

Background & daily life

A day in their life

Bob’s alarm goes off at 6:15am. While the kettle boils, he checks his personal server’s uptime (down 8 minutes total this month, acceptable). Breakfast is oatmeal with almond butter—eaten at his desk while scanning build logs from overnight. By 7:30, he’s in the office, preemptively purging macOS caches before the team arrives. The morning sprint planning is where he catches inter-team tensions, like when the backend team’s new API broke the mobile build. Lunch is a salad from the same deli (rutabaga slaw day is a highlight). Post-lunch, he’s debugging a Xcode provisioning profile error, muttering about 'certificate nightmares,' while skimming Apple’s latest developer forum updates. At 5pm, he leaves promptly—but logs back in at 9pm to finish auto-generating the release checklist document. On his phone, he notices a tweet from a CI/CD tool CEO. He smiles, writes 'Pray for my team,’ then opens Xcode again.

Lifestyle

Bob lives in a compact but tidy two-bedroom flat where every cable is neatly labelled and every device is on a strict update schedule. His weekends alternate between long solo hikes in the Avon Gorge (weather permitting) and home automation tinkering. He maintains a meticulous spreadsheet of personal expenses but occasionally blows it on rare whisky or high-end audio gear. Socially, he’s part of a small group of ex-university friends who meet monthly at a quiet pub where the WiFi is stable. Health-wise, he’s stubborn about his coffee-to-water ratio but trains for 5K runs to offset his tendency to forget to eat during work sprints. Money is saved for meaningful upgrades, not disposable luxuries.

Work life

At work, Bob is the gatekeeper of build consistency for the iOS team. His mornings start with a coffee-fueled review of the previous night’s CI/CD runs, cleaning up any residual Xcode caches before the team arrives. He’s been pushing to replace manual artifact cleanup with a custom script suite, fighting organisational inertia. His MacBook Pro fleet is his domain—he knows the EFI firmware version of each machine—and he’s currently locked in a low-stakes war of attrition with IT over whether the company should migrate to M1 chips. The fintech’s rapid feature rollouts mean his job is part DevOps, part therapist for frustrated developers. He spends lunch hours researching obscure Xcode quirks and evenings debugging his home server.

Relationships

Bob’s family—parents in Birmingham, a sister in Edinburgh—assumes he’s 'an Apple person' and stops asking after the first five minutes of technical explanations. His closest friends are from university, where he was the one who figured out how to bypass student WiFi restrictions. At work, he’s the quiet but firm voice of reason, though some younger engineers think he’s 'a bit intense' about clean commits. His online influences are a mix of grey-beard open-source maintainers and Apple internals sleuths. He actively avoids LinkedIn but lurks on Hacker News for the CI/CD threads.

How they decide

Cautious but not paralysed, Bob makes decisions by compiling evidence, testing small-scale, then scaling. He’ll spend a weekend benchmarking two solutions before choosing, but once committed, he’s all-in. Peer opinions matter if the person has proven track record; otherwise, it’s data first. He’s skeptical of hype but gets grudgingly excited about solve-a-niche-problem tools.

How they sound

Bob speaks in measured, precise clauses with occasional dry wit. He avoids corporate jargon but isn’t afraid of technical terminology when it’s precise. Britishisms like 'cheers' and 'bodge' creep in under stress. He has a habit of finishing sentences with 'basically' when explaining complex systems. If frustrated, his accent sharpens. He never uses 'synergy' unironically.