Brad Bins

Why this persona fits the audience

Backend engineer on an 8-person Manchester devtools team. He owns the internal code-assistant workflow, with prompt templates, evals, and release checks spread across CLI scripts, local notebooks, and free-tier APIs.

• Age: 28
• Location: Manchester, UK
• Occupation: Backend Engineer
• Income: £61k + equity
• Education: BSc in Software Engineering
• Company size: 8
• Years in role: 3

“It's not about the fanciest tool, it's about making the tools you have work as efficiently as possible.”

Brad Bins, 28, is a backend engineer at a burgeoning devtools startup in Manchester, UK. Holding a BSc in Software Engineering, he's carved out a niche for himself within the company's lean, eight-person team. His primary responsibility is the internal code-assistant workflow, a complex system he's built and continues to refine using a patchwork of CLI scripts, local Jupyter notebooks, and judiciously chosen free-tier APIs. This role perfectly aligns with his core values: a deep appreciation for the craft of software development, a belief in learning through hands-on building, and a stringent adherence to cost discipline. He sees the potential for AI to revolutionise development but is wary of the hype, preferring to focus on practical, demonstrable improvements. His current focus is on optimising prompt templates and standardising evaluation metrics for the code-assistant, a task complicated by the limitations of free services and the need for robust, reproducible results. He recently spent two weeks refactoring the release check scripts to improve their speed and reliability, a project born from a desire to reduce friction in the deployment pipeline. Brad is driven by a desire for technical mastery and efficiency, seeing elegant solutions to complex problems as a form of art. He's not motivated by status or overt recognition, but by the quiet satisfaction of building something robust and effective. His income of £61k, supplemented by equity, allows for a comfortable but not extravagant lifestyle, reinforcing his pragmatic approach to spending and investment. He views his career as a continuous learning journey, with each challenge presenting an opportunity to deepen his understanding and hone his skills. The autonomy he enjoys in defining and implementing the code-assistant workflow is a key factor in his job satisfaction, though it also brings the pressure of sole ownership.

Background & daily life

A day in their life

Brad's day typically starts around 6:30 AM with a run, followed by breakfast and a quick scan of Hacker News. He cycles to the office by 8:30 AM, grabbing a coffee on the way. The morning is usually dedicated to focused coding, tackling the most complex tasks related to the code-assistant workflow – perhaps refining prompt templates or debugging a new evaluation script. Lunch is a packed meal eaten at his desk while catching up on Slack. The afternoon involves more collaborative work, code reviews, and meetings, often interspersed with troubleshooting issues that arise from the current setup. He aims to leave by 5:30 PM, often spending an hour or two in the evening on personal projects or learning a new technology.

Lifestyle

Brad lives in a rented two-bedroom flat in Chorlton, Manchester, sharing with a friend from university who works in data science. He's a creature of habit, waking early for a 5k run most mornings before cycling to the office. His evenings are often spent tinkering with personal projects or diving deep into technical documentation. He's careful with money, favouring free or open-source tools and cooking most meals at home, though he'll occasionally splurge on a good craft beer at a local pub with colleagues. Socially, he's more of a listener than a talker, preferring smaller, more intimate gatherings.

Work life

As the backend engineer responsible for the internal code-assistant workflow at his devtools startup, Brad's days are a constant juggle of optimisation and integration. He's currently wrestling with the latency of a free-tier LLM API for prompt generation and trying to standardise evaluation metrics across disparate local notebooks and CLI scripts. The pressure is on to demonstrate tangible improvements in developer productivity without incurring significant costs. He collaborates closely with the two frontend engineers and the product manager, but often feels like he's the sole architect of the backend infrastructure, which can be both empowering and isolating.

Relationships

Brad's closest relationships are with his university friends, including his flatmate, who share his analytical mindset. He respects his CTO's technical acumen but finds the CEO's focus on rapid growth slightly detached from the day-to-day engineering realities. His parents, both teachers, are proud of his career but don't fully grasp the technical details.

How they decide

Brad is a methodical researcher. He'll spend time evaluating different approaches, reading documentation, and often prototyping solutions before committing. He values evidence and practical results over flashy marketing. He's not afraid to try new things but prefers to understand the underlying mechanics and potential trade-offs thoroughly. Peer recommendations from trusted technical sources carry weight, but he ultimately relies on his own analysis.

How they sound

Speaks with a clear, measured cadence, often using precise technical language. Avoids hyperbole and overly casual slang. His tone is generally calm and analytical, even when discussing frustrating issues. He tends to pause to formulate his thoughts carefully. You won't hear him making grand pronouncements or expressing strong emotional opinions about technology; it's more about the 'how' and 'why' it works.