10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Lea Kochan

Lea Kochan

Engineering manager at an IoT startup

Full-depth AI personas

Why this persona fits the audience

She leads a 12-person firmware and cloud team at a smart-sensor startup in Berlin. Device profiles, test payloads, and rollout config JSON are currently kept in a paid cloud datastore and mirrored in Git for audit trails.

  • Age: 42
  • Location: Berlin, Germany
  • Occupation: Engineering manager
  • Income: €92k
  • Education: MSc Embedded Systems
  • Company size: Startup (approx. 50 employees)
  • Years in role: 4
“The elegance of a system isn't in its complexity, but in how reliably and efficiently it solves a problem.”

Lea Kochan, 42, is a seasoned Engineering Manager at a burgeoning IoT startup in Berlin, a role she's held for the past four years. Her journey into embedded systems began during her MSc in Embedded Systems, where she developed a deep appreciation for the intricate dance between hardware and software. This academic foundation, coupled with a natural inclination towards precision and order, has shaped her professional ethos. She leads a diverse team of twelve engineers, split between firmware development and cloud infrastructure, tasked with building and maintaining the backbone of the company's smart-sensor technology. Her current focus is on refining the processes for managing device profiles, test payloads, and crucial rollout configuration JSON files. These critical data structures are currently housed in a paid cloud datastore, a decision made to ensure robust versioning and access control, with Git serving as a vital mirror for audit trails and historical tracking. This setup, while functional, represents a significant operational cost and a point of ongoing evaluation for Lea, who is constantly seeking more streamlined and cost-effective solutions. She lives by the principles of accountability and meticulous documentation, believing that well-defined processes are the bedrock of scalable technology. Her personal life reflects this organized approach; she's a dedicated cyclist, often exploring the outskirts of Berlin, and enjoys the tactile satisfaction of hardware prototyping in her limited free time. Financially, Lea is a pragmatic saver, prioritizing long-term security over immediate gratification, a trait that extends to her professional decision-making, where she favors proven, reliable technologies and well-researched solutions over trendy, unproven ones. She views time as a valuable, finite resource, which fuels her drive for efficiency in both her work and personal life, always seeking ways to optimize workflows and minimize wasted effort.

Background & daily life

A day in their life

Lea's typical weekday begins around 6:30 AM with coffee and news. By 8:00 AM, she's on her bike, heading to the startup's office in Friedrichshain. The morning is usually packed with stand-ups, reviewing pull requests, and addressing urgent technical blockers for her firmware team. After a quick lunch, often a packed meal from home, she dedicates the afternoon to more strategic tasks: sprint planning, architectural discussions with the cloud team, or deep dives into performance metrics. She might spend an hour troubleshooting a tricky deployment issue or researching new testing methodologies. By 6:00 PM, she cycles home, often stopping at a local market, before starting her evening routine of dinner and some light work or personal project time.

Lifestyle

Lea lives in a well-organized, minimalist apartment in Prenzlauer Berg, shared with her partner, a software architect. Weekday mornings start early with a strong coffee and a quick scan of tech news before cycling to work. Evenings are often spent reviewing code, planning sprints, or occasionally tinkering with a personal hardware project. Weekends are a mix of longer cycling trips through Brandenburg, visiting local flea markets for vintage electronics, and catching up with a small circle of close friends over dinner. She's financially prudent, saving consistently for future travel and potential home ownership, but enjoys investing in quality tools and experiences that enhance her work and hobbies.

Work life

As an Engineering Manager, Lea's days are a constant juggle between strategic planning, team support, and hands-on problem-solving. She spends a significant portion of her time in sprint planning, code reviews, and one-on-one meetings with her firmware and cloud engineers. The pressure to deliver reliable, scalable IoT solutions on a tight startup budget is ever-present. She champions rigorous testing and comprehensive documentation, often finding herself mediating technical debates and ensuring alignment between hardware capabilities and software implementation. Her team relies on a mix of Jira for task management, Confluence for documentation, and their current paid cloud datastore for critical configuration data, which she's always evaluating for efficiency and cost.

Relationships

Lea maintains a close relationship with her partner, who understands the demands of her tech career. Her core social circle consists of a few long-term friends, mostly from her university days, who share similar professional backgrounds or outdoor interests. Within her company, she's respected by her team for her technical acumen and fair management style, though she keeps a professional distance. Her former MSc supervisor occasionally provides informal mentorship.

How they decide

Lea approaches decisions methodically, weighing pros and cons carefully. She prioritizes solutions that offer long-term stability and maintainability, often conducting thorough research and consulting documentation before committing. While she values peer input, especially from her senior engineers, the final decision rests on a pragmatic assessment of technical feasibility, cost-effectiveness, and alignment with strategic goals. She is not prone to impulsive choices and prefers well-defined processes.

How they sound

Lea speaks with a clear, measured cadence, her German accent subtly present. She uses precise technical language when discussing work, avoiding excessive slang or overly casual phrasing. Her tone is generally calm and professional, even when discussing challenging issues. She tends to understate problems and focus on solutions, rarely engaging in gossip or complaining. When explaining complex topics, she's patient and thorough.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • reserved
  • diligent
  • analytical
  • patient
  • organized
  • calm under pressure

Goals

  • Successfully scale the company's sensor network to one million devices.
  • Mentor junior engineers and foster a culture of continuous learning within her team.
  • Achieve a better work-life balance, dedicating more time to personal projects and family.
  • Contribute to open-source projects related to embedded systems.
  • Eventually transition into a more senior technical leadership role, perhaps an architect position.

Problems & frictions

  • Managing the complexity of device configurations and firmware rollouts across a growing fleet.
  • Ensuring data integrity and security for sensitive device telemetry and control parameters.
  • Balancing the need for rapid development with maintaining high code quality and robust testing.
  • The overhead and cost associated with managing configuration data in a separate, paid service.
  • Keeping up with the rapid pace of technological advancements in both hardware and cloud infrastructure.

Values

  • precision
  • accountability
  • documentation
  • efficiency
  • reliability

Interests

  • hardware prototyping
  • industrial IoT
  • cycling
  • embedded Linux
  • data visualization

Media habits

  • Reads Hacker News and LWN.net daily
  • Listens to tech podcasts during commutes
  • Follows key figures in embedded systems on Mastodon
  • Subscribes to industry newsletters (e.g., Embedded.com)
  • Occasional browsing of German tech forums

Questions & answers

Lea Kochan’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Myjson (https://myjson.online/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    My current setup uses a paid cloud datastore, mirrored in Git, for our device profiles and rollout configurations. The main hurdle to trying Myjson this month would be the integration effort and ensuring it meets our specific audit trail and versioning requirements, especially since our current solution is well-established. I'd need to assess if the versioning capability, which seems limited to 10 versions, is sufficient for our long-term needs. If the pay-as-you-go model works out to be more cost-effective than our current solution, I might consider it. The advertised pricing starts at $9 for 25,000 credits, which translates to about $25 for 100,000 credits, a comparable cost to what we might be paying now, depending on our usage. I would be willing to pay up to $30 per month if it proves to be a more efficient and reliable solution.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.