Skip to content

Latest commit

 

History

History
91 lines (70 loc) · 4.25 KB

PRODUCT.md

File metadata and controls

91 lines (70 loc) · 4.25 KB

Product

Platform

web

Users

  • Primary: technical decision-makers (CTO, VP Engineering, engineering lead) at startups and scale-ups, mostly in the DACH region. They arrive through a referral, LinkedIn or the blog and are deciding whether to bring in a hands-on freelancer. Their question: can this person fix our delivery, platform or product problem with us, and leave the team self-sufficient?
  • Secondary: engineers reading the blog and the gems.
  • Undecided: whether recruiters and freelance agencies are an audience to serve.

Product Purpose

Personal site and blog of Jan-Philip Loos, Freelance Platform & Product Engineer in Hamburg. It exists to win engagements: success is a technical decision-maker booking a call (the author's calendar booking link). The blog and gems demonstrate depth and earn trust and inbound interest.

Positioning

  • Product Engineering, end to end: the guiding principle. One person who covers the whole path, from infrastructure and platform to UI, and from modern product practice (small increments, fast feedback from real users) to engineering and team processes (trunk-based development, continuous delivery, teams that own outcomes and are strong in strategic problem solving, not just ticket work).
  • Hands-on, and the knowledge stays: builds alongside the team rather than advising from the side, so the team owns and sustains what was built after the engagement ends.
  • Functional programming + DevOps: a rare combination, part of the claim.
  • Proven at scale, founder's perspective: from startup co-founder to systems at 100M+ requests a day.
  • Not: cheap offshore capacity, a pure advisor, or an architect who doesn't code.
  • Industries (e-commerce, healthcare, B2B SaaS, fintech so far) describe past and current work, not a binding focus.

Operating Context

  • Visitors evaluate a person, not a product: they scan the home page, check proof and past work, read a post or two, then book a call or come back later.
  • Home page in German on maxdaten.de (/) and English on www.maxdaten.io (/en); blog, gems, posts and author pages are English only.
  • Content (posts, gems, authors, tags, series) lives in Sanity; the site is prerendered, so new content appears after a redeploy.

Capabilities and Constraints

  • Home page (pitch, services, selected work, recent posts), blog with series and tags, gems ("Gems of Precious Friends": recommended resources), author page, RSS, llms.txt, legal pages (Impressum, Datenschutz).
  • Job title is "Freelance Platform & Product Engineer" everywhere, in both languages.
  • Services as currently named, in this order: Modern Product Engineering, Continuous Delivery, Platform Engineering.
  • German legal requirements (Impressum, Datenschutzerklärung); analytics are Plausible, which any privacy text must mention.

Brand Commitments

  • Name and identity: Jan-Philip Loos, maxdaten (maxdaten.de / maxdaten.io).
  • Voice: WRITING.md — concise, active, intellectually rigorous without jargon; claims backed by evidence.
  • Outreach and copy may be German or English depending on the audience; the German and English home page pitches mirror each other.

Evidence on Hand

  • 15+ years in product development, platform architecture and tech leadership.
  • Klingel Gruppe (e-commerce): platform and delivery at 100M+ requests a day, 20M product updates daily without incidents. May be named.
  • Fielmann: tech lead for an optometric measurement product used to fit spectacle lenses, rolled out to 700+ retail stores.
  • Papego: co-founder; German Design Award 2018.
  • No client names are off-limits.
  • Absent — do not fabricate: testimonials, case studies, talks, client logos, metrics beyond those listed.

Product Principles

  1. Proof over promises: every claim traces to the evidence above.
  2. End to end is the offer: show the whole path from infrastructure to product and team, not a single specialism.
  3. Self-sufficiency is the outcome: the client's team owning the result is the point, not ongoing dependency.
  4. Hands-on credibility: the site itself, its writing and its engineering demonstrate the craft.

Accessibility & Inclusion

WCAG 2.2 AA is the required standard for every surface, in both languages.