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

Malik Schlicht

Malik Schlicht

Developer advocate sharing API and CLI demos

Full-depth AI personas

Why this persona fits the audience

Creates API demos, CLI walkthroughs, and conference teaser clips for a mid-size developer tools company in Berlin. He records on a MacBook Pro M3, works with one other advocate and a designer, and publishes short clips to docs pages, X, and internal channels.

  • Age: 37
  • Location: Berlin, Germany
  • Occupation: Developer advocate
  • Income: €88k salary
  • Education: Dipl.-Ing. Informatik
  • Company size: 50-200 employees
  • Years in role: 4
“‘I spend half my time making tools easier to understand, and the other half explaining why people *think* they’re easy to understand.’”

Malik Schlicht grew up in Hamburg, where his fascination with how systems talk to each other started with disassembling his father’s Commodore 64. By 18, he was hacking together Perl scripts to automate school admin tasks, and by 22, he had his Dipl.-Ing. in Computer Science from TU Berlin. His first job at a cloud startup involved writing the kind of docs engineers love but managers ignore—a pattern that defined his early career. At 33, he moved into developer advocacy, realizing he thrived in the ‘translator’ role between engineering and end users. Now 37, he’s a senior advocate at a high-growth Berlin SaaS company, where he’s become the de facto standard for ‘how to demo a CLI’. His go-to tools are his M3 MacBook Pro (upgraded from an Intel model after a year of complaining), OBS Studio (with a ScreenGaze trial license), and a console app he built to scrape Slack for common questions. He’s famously picky about tools—but only if they affect his workflow. Recently, he’s been pushing for more automated publishing pipelines, since manual uploads to YouTube and X are eating into his ‘real work’ time. His biggest constraint is time, not budget. He’s grown frustrated with the ‘polish over clarity’ trend in dev tooling and often finds himself editing corporate demos to *remove* animations so the content comes through. He’s considering freelance consulting on the side, but his current company’s equity stake keeps him tethered. His apartment is a reflection of his work ethos: functional, slightly spartan, but with intentional upgrades (like his Eizo monitor). He’s at peace with his single status but admits to envying friends’ weekend trips—his idea of a break is a solo hike in the Harz mountains with a Kindle full of API design documents.

Background & daily life

A day in their life

Malik’s weekday starts at 6:30 AM with a cold shower and a protein shake. By 7:30, he’s at his local café, answering Slack messages and scripting that day’s demo (today: a 90-second Terraform CLI walkthrough). Back home by 9, he sets up his recording rig (M3 MacBook, Blue Yeti mic, Logi C920 camera) and films three takes before lunch. Post-lunch is editing—he’s trying to cut this part down after his team suggested ScreenGaze, but he’s skeptical. At 3 PM, he deploys the final clip to the docs site and X, then spends an hour in GitHub discussions. His day ends with a 7 PM gym session, followed by takeout sushi and a deep dive into some new CLI tool he saw on Hacker News. He’s usually in bed by 11, but not without checking his analytics dashboards one last time.

Lifestyle

Malik lives alone in a spacious two-bedroom apartment in Friedrichshain, where he’s slowly replacing IKEA furniture with secondhand finds. He’s a creature of habit—morning walks to a local café for *kaffee und mohnschnecke* (coffee and poppy-seed pastry), evening cycling along the Spree, and a standing Friday game night with a rotating group of tech industry friends. He’s health-conscious but pragmatic: yoga once a week, occasional gym sessions, and a freezer full of prepped lentil stews. His budget is tight by Berlin tech salaries but comfortable—he avoids lifestyle inflation and splurges only on his M3 MacBook Pro and a high-end microphone. Socially, he’s not a party person, but he’s always down for a long discussion about API design or open-source ethics.

Work life

As a developer advocate at a mid-size Berlin-based SaaS company, Malik’s job is 70% content creation and 30% community engagement. His workday starts with triaging API feedback from Slack and GitHub, then jumping into editing the day’s CLI demo—usually something involving Kubernetes or Terraform. He records on his M3 MacBook Pro, using a scripted but conversational style, then spends hours refining with QuickTime, iMovie, and occasionally Final Cut Pro (when the designer is available). He’s recently been pushing his team to adopt ScreenGaze for smoother workflows, but the designer prefers manual edits. His main pressure is output speed—management wants more clips, but he refuses to sacrifice clarity or accuracy. He collaborates closely with one other advocate (a former sysadmin) and a motion graphics designer, plus occasional guest appearances from engineering.

Relationships

Malik’s closest relationships are with his two best friends—both ex-engineers turned founders. They meet every other week for schnitzel and debates about ‘what’s broken in tech’. His family (parents in Hamburg, a sister in Munich) stays in touch via WhatsApp, but he visits only 2-3 times a year. He’s part of a tight Berlin tech meetup group that skews toward DevOps and cloud-native enthusiasts. His professional influences include folks like Armon Dadgar (from HashiCorp) and Julia Evans (for her teaching style). He’s single and not actively looking, though he’s started swiping again after a dry spell. His neighborhood’s expat community is his social safety net.

How they decide

Malik is a hybrid of cautious researcher and trust-in-your-gut decider. For tools, he’ll trial everything free-tier first, compare feature overlap, and then decide quickly—if it doesn’t fit his workflow in 3 days, he dumps it. His content decisions are more collaborative, though; he’ll prototype 3 versions of a demo and let feedback guide. Work-life decisions (like a new apartment) take longer, as he weighs tradeoffs meticulously.

How they sound

Malik speaks in clear, measured sentences with a slight German accent that softens but doesn’t fade. He avoids jargon unless necessary and prefers concrete examples over abstract concepts. His humor is dry—think one-liners about ‘yet another CLI that reinvents grep’. He never says things like ‘just do it’ or ‘it’s easy’; instead, he’ll say ‘It’s a 10-minute setup, but the payoff is… there, eventually’. He’s blunt in feedback but never unkind—more ‘This part drags. Can we show the error first?’ than ‘This is bad’.

Personality traits

  • Precise communicator
  • Quick but deliberate editor
  • Enjoys teaching
  • Hates vague documentation
  • Journalist-style curiosity
  • Minimalist approach to tools
  • Shares credit readily
  • Skeptical of hype
  • Thinks in workflows
  • Prefers function over flair

Goals

  • Build a personal brand as a thought leader in developer tooling
  • Contribute to at least one major open-source project this year
  • Move to a quieter Berlin neighborhood (with better WiFi)
  • Start a newsletter on ‘APIs for non-engineers’
  • Cut down on unnecessary tool subscriptions (he’s at 12 right now)
  • Run a marathon (he’s at 10K consistency so far)

Problems & frictions

  • Struggles with API changes breaking his demo scripts mid-quarter
  • Internal politics slow down tool adoption (like ScreenGaze)
  • Feels like he’s drowning in *useful* but low-signal newsletters
  • His YouTube analytics are mediocre, and he’s not sure why
  • Work-life balance is okay but could be better—weekends get messy when deadlines loom
  • Berlin rent hikes are making him reevaluate long-term housing

Values

  • technical accuracy
  • helpfulness
  • speed
  • experimentation
  • clarity
  • minimalism

Interests

  • APIs
  • command line tools
  • developer education
  • screen capture workflows
  • minimalist design
  • open-source software

Media habits

  • Tech newsletters (Stratechery, The Changelog)
  • YouTube tutorials (Larry Udell, Fireship)
  • X for industry trends
  • Indie Hackers for side projects
  • Podcasts (Syntax, Software Engineering Daily)
  • Reddit (r/programming, r/DevOps)

Questions & answers

Malik Schlicht’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://screengaze.studio/ (ScreenGaze) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    At first glance, ScreenGaze looks promising, but I'd need to see it in action before committing. The one-time €29 license is tempting, especially since I despise subscriptions, but I'm skeptical about ditching my OBS Studio setup. Key questions: Can I integrate ScreenGaze with my existing workflow? Will it handle CLI demos better than my current tools? The automatic zooming and cursor tracking seem useful, but I need to verify if those features actually save time. My main concern is the learning curve—if it disrupts my workflow, it's a non-starter. I'd trial it, but only if the free version allows proper testing of export limits and watermarking.
    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.