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

Lennie Jeorga

Lennie Jeorga

Engineering lead hiring immersive frontend talent

Full-depth AI personas

Why this persona fits the audience

He leads a five-person frontend team at a SaaS company in Berlin and is currently hiring one developer with three.js and React Three Fiber experience for an interactive product initiative. He manages candidate tracking in Greenhouse and a spreadsheet, and reviews openings from niche job boards and LinkedIn.

  • Age: 35
  • Location: Berlin, Germany
  • Occupation: Engineering lead
  • Income: €80k–€110k
  • Education: MSc Computer Science
  • Company size: 50-100 employees
  • Years in role: 4
“'I could tell you exactly how many candidate applications I've rejected for saying 'I'm good with React Three Fiber' without explaining clutch optimizations. The sync gap between what people claim and what they can actually deliver is minesweeper code.'”

Lennie Jeorga's career trajectory has been precisely what he planned as a student—a straight line from Bucharest's top CS program to Berlin's tech scene. His move to Germany at 24 was purely calculated: better salaries, more interesting problems, and a cycling infrastructure that satisfied his borderline-obsessive commuting needs. The SaaS startup he joined as a mid-level engineer four years ago was his first real gamble, but the gamble paid off when they pivoted to immersive analytics. Now leading a team of five, he's most proud of building a frontend system that handles 500KB+ of WebGL data without a single frame drop. His current hiring project is particularly thorny—he needs someone fluent in GPU-accelerated rendering for volumetric data sets, but most candidates stop at basic shader programming. His spreadsheet tracking system has evolved into a six-tab monster that somehow works perfectly, though his manager gently suggested looking for better solutions. Lennie resists change unless forced—his current setup (Greenhouse for pipeline, Excel for metrics, manual outreach) works well enough, and he's skeptical about the ROI of fancier tools until he sees concrete evidence. Outside work, his personal projects often involve exploring the boundaries of Three.js—like the time he built a live-collaborative 3D whiteboard that his team now uses for architecture planning. He's fiercely independent in his decision-making, but will quietly change his position if presented with irrefutable data. Financial security is important to him, but he measures his success more in technical impact than salary—though he does keep a spreadsheet tracking his net worth for academic interest. His current stress is the work-life balance: he can't decide whether to push for a headcount increase or keep struggling with the current team size.

Background & daily life

A day in their life

Lennie wakes at 6:00, checks his sleep stats, and immediately starts coffee while reviewing Slack messages. By 7:15, he's cycling to the office, reviewing LinkedIn engineer profiles on his phone. His first work block is spent in Greenhouse evaluating three.js test tasks submissions. At 11:00, the team's async standup doc appears in his Slack—a detailed spreadsheet of what everyone worked on, blocked on, and plans to tackle. Lunchtime is coding alone with a prepped meal, listening to tech podcasts at 1.5x speed. Afternoon brings a 45-minute 1:1 with a senior engineer about architectural tradeoffs, followed by two hours of hands-on debugging. He leaves by 19:00, stops at the organic grocery for the week's meals, then spends evenings cycling or tweaking personal projects before bedtime at 23:00.

Lifestyle

Lennie lives in a minimalist two-room apartment near Tempelhof, where he cycles to work even in Berlin's harshest winters. His Saturdays are sacred: he starts with a 50km ride along the Spree, then spends evenings tweaking AR demos in his home workspace. He budgets meticulously, but splurges on high-end cycling gear and rarely-used audio equipment. His social circle is small but tight-knit—mostly former coworkers and a few fellow tech enthusiasts. He eats out only for social reasons, preferring meal-prepped salads and fermented foods. Health-wise, he's hyper-aware of his resting heart rate and sleep cycles, tracking them with wearables he chooses after extensive research.

Work life

At a Berlin SaaS startup building interactive data visualization tools, Lennie's team specializes in cutting-edge WebGL implementations. His workday starts reviewing candidate submissions in Greenhouse while sipping matcha, then dives into 3-hour Focus Time blocks where he codes directly in their monorepo. His spreadsheet tracking system is absurdly complex but works perfectly. He loathes meetings but attends them with brutal efficiency, cutting discussions with data points rather than opinions. His current hiring pain point is distinguishing between true Three.js experts and candidates who've just completed tutorials. The team culture is collaborative but output-driven, with a weekly async progress doc they all contribute to.

Relationships

Lennie's closest relationships are with two former teammates who now work at different companies—they meet monthly for illegal board game nights. His parents, both academics in Bucharest, call weekly but struggle to understand his work. His ex-wife (amicable split three years ago) still consults him about kitchen tech upgrades. At work, he's respected but not particularly close with teammates, preferring professional boundaries. His only real 'influence' comes from technical forums where anonymous experts share three.js implementation hacks.

How they decide

Lennie makes decisions methodically through research, peer validation, and small experiments. He prefers gathering data over asking opinions, and will spend hours testing alternative approaches before choosing. Once decided, he commits fully but remains open to reversing course if new evidence emerges. He dislikes authority-driven decisions and questions directives that aren't technically justified.

How they sound

Lennie speaks in concise, technical sentences with precise terminology. He avoids metaphors, prefers exact measurements ('That shadow rendering took 32 seconds at 1440p'). His tone is matter-of-fact with slight impatience when people generalize technical concepts. He uses German occasionally but defaults to English in professional contexts. When excited about tech, his cadence quickens with almost clinical enthusiasm. He never says 'probably'—only 'the 95% confidence interval suggests...'

Personality traits

  • detail-obsessed but pragmatic
  • quietly competitive
  • values directness
  • avoids small talk
  • prefers asynchronous communication
  • stores exact calendar blocks for focused work
  • double-checks everything critical
  • skeptical of trendy tools without clear ROI
  • reuses solutions when possible
  • demands high standards but forgives reasonable mistakes

Goals

  • Build Berlin's most innovative AR data visualization product in the next 18 months
  • Mentor at least one junior developer to senior level by 2025
  • Complete a solo-cycling trip from Berlin to Prague next summer
  • Reduce team's technical debt without slowing feature delivery
  • Learn enough Rust to make informed architectural decisions
  • Move to a larger apartment with proper guest space by 2024

Problems & frictions

  • Finding candidates who truly understand Three.js optimization for production-scale applications
  • Balancing rapid prototyping needs with long-term code maintainability
  • Convincing product managers that some AR/VR features require 3x the time they expect
  • Maintaining consistent documentation when the team is constantly immersed in novel web technologies
  • Keeping his cycling habit from encroaching on sleep during high-pressure sprints
  • Finding time to evaluate emerging tools when his current tech stack works well enough

Values

  • reliability
  • systems thinking
  • team accountability
  • autonomy in workflow

Interests

  • product engineering
  • AR/VR
  • cycling
  • design systems
  • Berlin tech meetups

Media habits

  • Google Alerts for Three.js news
  • Hacker News
  • YouTube technical talks
  • LinkedIn for professional networking
  • Medium articles on engineering leadership

Questions & answers

Lennie Jeorga’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of CreativeDevJobs (https://www.creativedevjobs.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make CreativeDevJobs better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I manage hiring through a combination of Greenhouse for candidate tracking and a meticulously organized spreadsheet for deeper metrics. The spreadsheet has six tabs that track everything from initial outreach to technical assessment scores. I also review niche job boards and LinkedIn regularly. Compared to my current setup, CreativeDevJobs might streamline the process by consolidating relevant job listings, but I'm skeptical if it can replace my detailed tracking system. The newsletter seems useful, but I don't have a clear sense of how it improves over manual LinkedIn searches. I wouldn't switch unless I see concrete evidence of better-fit candidates. My current budget for hiring tools is tight, so I wouldn't pay more than $20 per month. The only way I'd reconsider is if CreativeDevJobs integrates with Greenhouse or significantly reduces time wasted on unqualified candidates.
    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.