Curtis D'Amore-Connelly

Why this persona fits the audience

He leads a 6-person backend team at a Manchester SaaS startup whose customer portal and internal admin tools run on Kubernetes. He is the person who usually chases production errors, rotates logs, and coordinates root-cause notes; the team still relies on spreadsheets, shell commands, and cloud console views rather than a dedicated paid log platform.

• Age: 29
• Location: Manchester, UK
• Occupation: Backend engineering lead
• Income: £84k base
• Education: Bachelor's in computer science
• Company size: Startup (approx. 30 employees)
• Years in role: 3

“The real challenge isn't just building it; it's keeping it running smoothly when nobody's looking.”

Curtis D'Amore-Connelly, a 29-year-old backend engineering lead, has carved out a significant role within Manchester's vibrant tech startup scene. Holding a Bachelor's in Computer Science from a reputable UK university, he quickly gravitated towards the fast-paced world of SaaS development. His career trajectory led him to his current position at a growing startup, where he oversees a team of six backend engineers responsible for the core customer portal and internal administrative tools. The company's infrastructure is built around Kubernetes, a technology Curtis finds both challenging and rewarding. He's the go-to person when production issues inevitably surface, a role that demands constant vigilance and a deep understanding of the system's intricacies. This often involves him manually sifting through logs, orchestrating log rotation, and meticulously documenting root causes – a process he acknowledges is far from ideal. He's acutely aware of the limitations imposed by their current tooling, which relies heavily on spreadsheets, shell commands, and direct cloud console interaction, a stark contrast to more integrated, paid solutions. This hands-on approach, while effective in the short term, consumes valuable time that could be spent on proactive development or architectural improvements. Curtis is driven by a desire for craftsmanship and efficiency, valuing the speed at which his team can deliver features but equally concerned with the long-term stability and maintainability of their codebase. He's pragmatic about his finances, earning a solid £84k base salary, which allows for comfortable living and some savings, but he's mindful of the startup's budget constraints when considering new tools or infrastructure upgrades. His personal life is a deliberate balance, with evenings often dedicated to his passion for playing the guitar or following his beloved football club, ensuring he has outlets beyond the demanding technical landscape he navigates daily. He sees the current operational setup as a temporary hurdle, a problem to be solved through careful planning and strategic implementation, rather than an insurmountable barrier.

Background & daily life

A day in their life

Curtis's typical weekday starts around 7:30 AM with a quick scan of overnight alerts and emails before heading to the office. His commute involves a podcast and a coffee. The morning is usually dedicated to team stand-ups, code reviews, and tackling urgent production issues. Lunch is often a quick affair at his desk while reading tech articles. Afternoons are a mix of planning upcoming sprints, deep dives into specific technical challenges, and collaborating with other teams. He often stays until 6:30 or 7:00 PM, especially if there's a critical bug or a deployment to monitor. Evenings are for unwinding, often with his guitar or catching up with friends.

Lifestyle

Curtis lives a fairly routine life in a shared flat in Chorlton, Manchester, balancing his demanding job with personal interests. His evenings often involve either strumming his electric guitar, trying to master a new riff, or catching up on the latest football scores. He enjoys exploring Manchester's growing craft beer scene with his flatmate or a couple of close friends from university. While not extravagant, he's comfortable financially, saving a portion of his salary but also investing in his hobbies and occasional tech gadget upgrades. He prioritizes efficiency in his personal life, often meal-prepping on Sundays to save time during the week.

Work life

As the backend engineering lead, Curtis is deeply involved in the day-to-day operations of the company's SaaS platform. His team of six relies on him to navigate the complexities of their Kubernetes cluster, especially when production issues arise. He spends a significant portion of his time troubleshooting, analysing logs (often via shell scripts and manual console checks), and coordinating post-mortems. The pressure to maintain uptime and deliver new features quickly is constant, often leading to late nights or weekend work when critical bugs surface. He's constantly evaluating how to streamline processes, but the startup environment means resources are tight.

Relationships

Curtis maintains close ties with his university friends, many of whom are also in tech, providing a sounding board for technical challenges. He lives with a graphic designer flatmate, with whom he shares a friendly, low-drama dynamic. His parents, who live in a village outside Leeds, are proud of his career but don't fully grasp the technical details. He's not actively dating but is open to meeting someone.

How they decide

Curtis is a pragmatic decision-maker. He values evidence and data, preferring to research options thoroughly before committing. He's influenced by the opinions of trusted peers and senior engineers he respects, and he's always looking for the most efficient, low-friction solution that aligns with long-term stability and maintainability. He's not impulsive and will weigh pros and cons carefully, especially when it involves new tools or significant changes to existing infrastructure.

How they sound

Speaks with a clear, measured tone, often using precise technical language. He avoids excessive slang but might use mild UK colloquialisms like 'bit of a faff' or 'sorted'. His cadence is steady, reflecting his analytical nature. He tends to be direct when discussing technical problems but can be more reserved in casual conversation. He's not one for hyperbole and prefers factual statements.