Keno Abraham

Why this persona fits the audience

Is applying for platform and DevOps roles across Germany and the Netherlands, where remote hiring screens often involve live troubleshooting and system design. He still keeps interview prep in a text file and a notebook, and has not moved beyond manual workflows or free resources.

• Age: 31
• Location: Berlin, Germany
• Occupation: DevOps Engineer
• Income: €88k
• Education: BS in Computer Engineering
• Company size: 50-200 employees
• Years in role: 6

“The best tool is the one you understand inside and out, not the one that promises the most features.”

Born and raised in a smaller town in Brandenburg, Keno Abraham developed an early fascination with how things work, often taking apart electronics to understand their inner mechanisms. This curiosity naturally led him to pursue a Bachelor's degree in Computer Engineering in Berlin. Upon graduation, he entered the tech industry, quickly gravitating towards the challenges and responsibilities of DevOps. For the past six years, he has honed his skills, focusing on building and maintaining robust, scalable cloud infrastructure, primarily within the AWS ecosystem. He is deeply committed to open-source principles, believing that transparency and community collaboration lead to more resilient and adaptable systems. This conviction fuels his skepticism towards proprietary, 'black box' solutions, which he views as potential sources of technical debt and vendor dependency. Keno's approach to his career is characterized by a desire for stability and technical mastery; he seeks roles where he can deeply understand and optimize systems rather than constantly chasing the newest trend. He recently decided against adopting a new, expensive CI/CD platform his company was considering, opting instead to invest time in optimizing their existing Jenkins setup and integrating more open-source plugins, a decision that saved significant budget and reinforced his preference for pragmatic, well-understood tooling. He lives frugally, prioritizing long-term financial security and investing in durable goods, like his high-quality road bike, over fleeting luxuries. His current job search across Germany and the Netherlands is driven by a desire for a more challenging role and a company culture that aligns with his values of directness and technical excellence, though he finds the remote interview process, with its emphasis on live troubleshooting and system design, to be a particularly demanding hurdle. He meticulously prepares for these interviews, maintaining detailed notes in a physical notebook and a comprehensive text file, a testament to his methodical and detail-oriented nature.

Background & daily life

A day in their life

Keno's weekday typically starts around 6:30 AM. After a quick coffee, he might go for a 45-minute cycle if the weather permits, or do a short home workout. By 8:00 AM, he's at his desk, checking system dashboards and emails. The morning is usually dedicated to focused work: deploying code, optimizing infrastructure, or addressing any urgent alerts. He prefers to tackle complex tasks before lunch. After a simple, home-prepared meal, he might have a scheduled team sync or a 1:1 with his manager. The afternoon often involves code reviews, planning for upcoming sprints, or investigating performance bottlenecks. He aims to wrap up by 6:00 PM, though urgent issues can extend this. Evenings are for personal time – cooking, reading, or working on a small side project.

Lifestyle

Keno lives in a modest but well-organized two-bedroom apartment in Prenzlauer Berg, Berlin, sharing with a long-term girlfriend who works in graphic design. His routine is structured: early mornings for cycling or a quick run, followed by focused work. Evenings are for cooking, reading sci-fi novels, or tinkering with personal projects. He's careful with money, preferring to save for future stability rather than impulsive purchases, though he’ll invest in quality gear for his bike. Social life is limited to a few close friends and occasional meetups with his girlfriend's creative circle, where he often feels slightly out of his depth.

Work life

As a DevOps Engineer at a mid-sized SaaS company, Keno's days are a blend of maintaining production systems, automating deployments, and responding to incidents. He champions open-source solutions and is wary of adding proprietary tools that introduce vendor lock-in or unnecessary complexity. His team is small, and while generally collaborative, he prefers clear, direct communication and avoids excessive meetings. The pressure to keep systems stable and performant is constant, but he finds satisfaction in solving complex infrastructure challenges through well-understood, robust methods. He recently pushed back against a proposal to adopt a new, expensive monitoring suite, arguing that their current open-source stack, with some configuration tweaks, could achieve similar results more frugally.

Relationships

Keno's primary influence comes from his girlfriend, who provides a grounding perspective outside of tech. He maintains a small circle of close friends, mostly fellow engineers, with whom he discusses technical challenges and career moves. He respects senior engineers who demonstrate deep technical understanding and pragmatic decision-making, often seeking their advice on complex issues.

How they decide

Keno is a cautious and research-driven decision-maker, especially concerning work-related tools or significant life changes. He prioritizes understanding the underlying principles and evaluating long-term implications. He relies on his own technical judgment and evidence from reputable sources, often cross-referencing information before committing. For personal matters, he consults his girlfriend and trusted friends, but the final decision rests on his own thorough evaluation.

How they sound

Speaks with a measured cadence, often pausing to formulate his thoughts precisely. His tone is generally calm and direct, avoiding hyperbole or overly casual slang. He uses technical jargon naturally within professional contexts but is capable of explaining complex concepts clearly. He tends to steer conversations towards factual analysis and practical solutions, often expressing skepticism with phrases like 'I'm not convinced that's the most straightforward approach' or 'What problem does this actually solve?'