Mayson Brouwer

Why this persona fits the audience

Works on a 6-person product team that shares temporary HTTPS links for QA, design review, and webhook callbacks while a feature is in development. The team currently pays for an alternative tunnel service and keeps access details in a project board.

• Age: 30
• Location: Amsterdam, Netherlands
• Occupation: Frontend engineer
• Income: €62k-€82k
• Education: Bachelor's degree
• Company size: Mid-sized tech company (approx. 200 employees)
• Years in role: 5

“It's all about making the complex feel simple, both for the user and for us building it.”

Mayson Brouwer, 30, is a dedicated frontend engineer based in Amsterdam, Netherlands, holding a Bachelor's degree in Computer Science. He's been working as a frontend engineer for five years, currently contributing to a product team of six at a mid-sized tech company. His professional life is deeply intertwined with his passion for building efficient and user-friendly interfaces, particularly within the React ecosystem. Mayson's current role involves significant collaboration, where the team frequently shares work-in-progress features using temporary HTTPS links. This process, essential for QA and design reviews, currently relies on a paid tunneling service whose access details are meticulously tracked on their project board. Mayson often finds himself navigating the intricacies of this system, ensuring smooth handoffs and troubleshooting any connectivity hiccups. This experience has made him acutely aware of the friction points in development workflows. He values speed and teamwork, believing that streamlined processes directly contribute to faster delivery of high-quality features. His interest in product analytics stems from a desire to understand user behavior and iterate effectively. Mayson's financial habits are pragmatic; he saves diligently but doesn't shy away from enjoying life's pleasures, like good food and travel. He sees his career as a path of continuous learning, aiming to deepen his expertise in JavaScript performance and contribute meaningfully to the developer community. He's driven by a desire to solve problems, both in code and in workflow, and is always on the lookout for elegant solutions that enhance productivity and collaboration within his team.

Background & daily life

A day in their life

Mayson's typical weekday starts around 8:00 AM with a quick breakfast and checking personal emails. He cycles to work, arriving by 9:00 AM. The morning is usually dedicated to focused coding on his current sprint tasks, often involving building new UI components or integrating APIs. After a team stand-up at 10:30 AM, he might spend an hour on code reviews for his colleagues. Lunch is a simple sandwich at his desk while browsing tech news. The afternoon involves more coding, debugging, and collaborating with the product manager or designer, often requiring him to generate temporary links for them to review. He usually leaves the office around 5:30 PM, heading home to cook dinner and unwind, perhaps with a personal coding project or a tech podcast.

Lifestyle

Mayson lives a fairly routine life in Amsterdam, prioritizing his work and personal development. He enjoys cycling to his office in the city center, often grabbing a quick coffee and stroopwafel from a local vendor. Evenings are typically spent either coding personal projects, exploring new JavaScript libraries, or catching up with friends over a beer at a 'bruin café'. He's conscious about his finances, saving a portion of his income for future travel and potential investments, but isn't overly frugal, enjoying good food and occasional weekend trips within the Netherlands. He values his independence and quiet evenings to recharge.

Work life

As a frontend engineer on a product team, Mayson's days are a blend of coding, code reviews, and collaborative problem-solving. His team of six works on a core feature set, and the current development workflow involves frequent sharing of work-in-progress builds. They rely heavily on temporary HTTPS links for various stakeholders, which has led to a somewhat ad-hoc system of managing access details on their project board. While they currently use a paid tunneling service, Mayson often finds himself troubleshooting connection issues or ensuring the right people have the correct, time-limited access, which can be a drain on his focus. He values clear communication and efficient processes.

Relationships

Mayson maintains a close-knit circle of friends, mostly fellow developers he met during university or at previous jobs. They often discuss technical challenges and share insights. He has a good rapport with his immediate team members, valuing their technical expertise and collaborative spirit. His family lives in a smaller town in the north of the Netherlands, and he visits them a few times a year.

How they decide

Mayson is a research-heavy decision-maker when it comes to tools and processes. He'll read documentation, compare alternatives, and often consult with trusted colleagues or online communities before committing to a solution. He values practicality and evidence of effectiveness over hype. For team-level decisions, he relies on consensus and data, preferring solutions that demonstrably improve workflow efficiency.

How they sound

Speaks with a clear, moderate pace, often using precise technical terms. His Dutch accent is subtle but present. He tends to be direct and avoids overly casual slang in professional settings, but can be more relaxed with close colleagues. He's not afraid to admit when he doesn't know something but will follow up with how he'd find out. He often uses phrases like 'Basically,' 'The thing is,' or 'What we're seeing is.'