Why this persona fits the audience
Engineering manager at a 6-person robotics startup in Boston, still close to the technical stack and using flashcards to track math formulas, sensor terms, and internal onboarding notes for the team.
- Age: 37
- Location: Boston, Massachusetts, USA
- Occupation: engineering manager
- Income: $145k
- Education: MS in electrical engineering
- Company size: 6
- Years in role: 4
““Every line of code, every sensor reading, has to serve a purpose. If it doesn't, it's just noise we have to manage, and managing noise is the enemy of progress.””
Harold Hettinger, 37, has dedicated the last decade to the intricate world of robotics. After completing his MS in Electrical Engineering at MIT, he was drawn to the fast-paced, innovative environment of startups. He spent a few years as a senior embedded systems engineer at a drone company before joining his current venture, a six-person robotics startup in Boston, as the Engineering Manager four years ago. This role allows him to remain deeply connected to the technical challenges, a necessity he embraces. Harold still maintains a physical and digital collection of flashcards, meticulously updated, to keep track of complex mathematical formulas crucial for control systems, obscure sensor terminology unique to their hardware, and detailed notes for onboarding new team members. He believes this active recall method reinforces foundational knowledge and ensures consistency across the small, but highly skilled, team. His income of $145k allows for a comfortable life, though he and his wife Sarah are diligently saving for a house, prioritizing financial stability over extravagant spending. Harold is driven by a desire to build robust, efficient robotic systems and foster a team environment where technical depth and clear documentation are paramount. He recently spearheaded a significant refactor of the robot's navigation stack, a decision driven by the need to improve pathfinding reliability under diverse environmental conditions, a process that involved extensive simulation and rigorous code reviews. This technical deep-dive, while time-consuming, directly contributes to his core value of ensuring the team's technical velocity is built on solid, well-understood foundations.
Background & daily life
A day in their life
Harold's typical weekday begins around 6:30 AM with a quick check of urgent emails and Slack messages. After a brief workout or a walk with Sarah, he’s at his desk by 8:00 AM. His morning is often consumed by team stand-ups, one-on-one syncs with his engineers, and tackling critical bugs that surfaced overnight. Lunch is usually a quick affair, often at his desk while reviewing a pull request or sketching out a new system design. The afternoon involves more in-depth work: debugging complex sensor integration issues, documenting API changes, or planning the next sprint. He tries to leave by 7:00 PM, but late-night coding sessions or urgent client calls sometimes extend his day.
Lifestyle
Harold lives in a modest two-bedroom apartment in Somerville with his wife, Sarah, a graphic designer. Their weekends are a mix of catching up on chores, exploring local parks, and occasional visits to friends. He’s diligent about his health, hitting the gym three times a week and trying to cook healthy meals at home, though takeout is an occasional necessity after late nights at the office. Financially, they are comfortable but not extravagant, focusing on saving for a down payment on a house. Social life is important but often secondary to work demands during crunch times.
Work life
As the Engineering Manager at a nimble robotics startup, Harold is constantly balancing strategic oversight with hands-on technical involvement. His team of five engineers tackles complex challenges in motion control and sensor fusion for industrial automation. He spends his days in code reviews, debugging stubborn firmware issues, guiding junior engineers, and meticulously documenting system architecture decisions. The pressure to deliver functional prototypes for investors and early clients is immense, requiring tight deadlines and rapid iteration. He often finds himself deep in algorithmic details, ensuring the robot’s perception system is robust.
Relationships
Harold is married to Sarah, who is supportive of his demanding career but also encourages him to disconnect. He has a small circle of close friends, mostly fellow engineers he met during his MS program, with whom he discusses technical challenges and life outside work. His parents, both retired teachers, are proud of his career but don't fully grasp the intricacies of robotics. His team members respect his technical acumen and mentorship.
How they decide
Harold is a highly analytical and research-driven decision-maker. He thoroughly evaluates options, weighs pros and cons, consults relevant documentation or data, and often seeks input from trusted technical colleagues before committing. He prioritizes solutions that offer long-term stability and maintainability, even if they require more upfront effort. He is not impulsive and tends to be cautious with significant choices, especially those impacting the team's workflow or project timelines.
How they sound
Harold speaks clearly and deliberately, with a measured cadence. He avoids jargon unless he’s certain his audience understands it, preferring precise technical language when necessary. He often uses analogies to explain complex concepts. His tone is generally calm and encouraging, but can become more direct when addressing critical issues or technical inaccuracies. He rarely uses slang and maintains a professional, yet approachable, demeanor.
Personality traits
- methodical
- detail-oriented
- patient mentor
- pragmatic
- analytical
- driven
- calm under pressure
- resourceful
Goals
- Successfully launch the company's first commercial product.
- Build a high-performing, cohesive engineering team.
- Achieve a deeper understanding of advanced AI for robotics.
- Purchase a home within the next five years.
- Contribute to open-source robotics projects.
Problems & frictions
- Limited resources and tight budgets at the startup.
- The constant need to stay ahead of rapidly evolving robotics technology.
- Onboarding new engineers quickly and effectively to the complex codebase.
- Balancing the desire for deep technical solutions with aggressive product timelines.
- Finding time for deep, uninterrupted technical work amidst management duties.
Values
- team velocity
- technical depth
- documentation
- efficiency
- continuous learning
Interests
- robotics
- embedded systems
- mentoring
- competitive programming
- signal processing
Media habits
- Reads Hacker News daily
- Listens to embedded systems podcasts during commute
- Follows key robotics researchers on Twitter
- Occasionally browses Stack Overflow for specific problems
- Skims technical blogs from major tech companies