Marlon Bergnaum

Why this persona fits the audience

Leads a two-person tooling effort at a Seattle indie game studio that uses one dedicated Mac for signing, upload automation, and test builds; the asset list lives in Notion and the team rotates access by calendar.

• Age: 37
• Location: Seattle, Washington, USA
• Occupation: Build and tooling engineer
• Income: USD 132k-155k
• Education: Bachelor's degree in computer engineering
• Company size: Small indie studio (20-30 employees)
• Years in role: 5

“If the pipeline is clean, the team can focus on making the game great. My job is to make sure that foundation is solid, no matter what.”

Marlon Bergnaum, 37, has carved out a niche for himself as a dedicated build and tooling engineer within Seattle's vibrant indie game development scene. Holding a Bachelor's degree in Computer Engineering, his career path has been marked by a consistent drive for efficiency and reliability, traits that have served him exceptionally well in the fast-paced, often resource-constrained environment of small studios. For the past five years, he's been instrumental at his current employer, a studio of about 25 people, leading a small but critical two-person tooling team. His role isn't glamorous, but it's foundational: he ensures that the complex machinery of game development runs smoothly. This often means wrestling with the studio's single, aging Mac Mini, which serves as the linchpin for signing releases, automating uploads to various platforms, and running crucial test builds. He's meticulously organized the studio's asset tracking within Notion, a system that, while functional, requires careful calendar coordination for team access, reflecting a pragmatic approach to shared resources. Marlon's income places him comfortably in the upper middle class for the Seattle area, a level he's achieved through steady career progression and a deep specialization rather than aggressive career climbing. He views his work not just as a job, but as a craft where technical rigor and a profound sense of ownership are paramount. His decisions are guided by a desire for long-term stability and throughput, often leading him to invest time in robust, if not always the flashiest, solutions. He recently spent two weeks optimizing the asset pipeline for their upcoming title, a project that involved deep dives into asset compression algorithms and scripting custom import routines, ultimately shaving hours off the build processing time. This dedication stems from a personal value system that prioritizes team reliability and the quiet satisfaction of a system that just *works*, allowing the creative teams to focus on their art without technical impediments.

Background & daily life

A day in their life

Marlon's weekday typically begins around 6:30 AM with a strong cup of coffee and a quick scan of overnight build logs and any urgent emails. He arrives at the studio by 8:30 AM, immediately checking the status of the main build server and addressing any issues that arose overnight. The morning is often spent working on planned improvements, like optimizing a build script or refining the test automation suite. After a brief lunch, he dedicates time to supporting the art and programming teams, answering questions about asset pipelines or resolving build integration problems. The afternoon might involve a sync-up with his junior colleague, code reviews, or further system development, always with an eye on the clock to ensure a stable build goes out by end of day. He usually leaves around 5:30 PM.

Lifestyle

Marlon lives with his wife in a modest but well-maintained bungalow in a quieter Seattle neighborhood. They prioritize experiences over material possessions, though he does have a curated collection of vintage synthesizers. His routine is structured, with early mornings for coffee and news before heading to the studio. Evenings are often spent tinkering with his home network, playing board games with his wife, or catching up on music. He's financially responsible, saving consistently for future home improvements and travel, and generally avoids impulse purchases. Socially, he prefers smaller gatherings with close friends over large parties.

Work life

As the lead for a two-person tooling team at a small indie studio, Marlon's days are a balancing act between proactive system improvement and reactive troubleshooting. His primary focus is maintaining and enhancing the build pipeline, ensuring smooth deployments for their latest project. The studio's reliance on a single Mac Mini for critical tasks like signing, upload automation, and test builds creates a concentrated point of failure he’s constantly monitoring. Managing shared access to Notion for asset lists and coordinating with the game development teams requires constant communication and meticulous planning to avoid bottlenecks. He feels a strong sense of ownership over the stability and efficiency of the studio's production infrastructure.

Relationships

Marlon is married to Sarah, a graphic designer, with whom he shares a calm, collaborative relationship. His immediate team consists of one junior engineer he's mentoring, who he trusts but needs to keep on track. He communicates regularly with the leads of the art and programming departments, often on an as-needed basis to resolve build-related issues. His influence comes from his proven reliability and deep understanding of the studio's technical infrastructure.

How they decide

Marlon is a highly analytical and research-driven decision-maker. He thoroughly investigates options, weighing pros and cons based on technical merit, long-term stability, and resource availability. He often seeks input from trusted peers or online communities but ultimately relies on his own rigorous assessment before committing. He is risk-averse when it comes to critical infrastructure, preferring proven solutions over bleeding-edge technologies unless a clear, substantial benefit is demonstrated.

How they sound

Marlon speaks with a measured, calm cadence, articulating his thoughts clearly and precisely. He uses technical jargon naturally when discussing work but can simplify explanations for non-technical colleagues. He avoids hyperbole and emotional language, preferring factual statements. His tone is generally even and reassuring, even when discussing complex or stressful issues. He's not one for office banter but engages readily in technical discussions.