{
  "profile": {
    "name": "Jiří Semmler",
    "role": "Product Engineer",
    "now": "Engineering Manager & Product Engineer at Keboola — I lead a backend team and still write code.",
    "tagline": "I'm a product builder: end-to-end and AI first. I take problems from the first customer conversation through to a working product.",
    "domain": "jirisemmler.eu",
    "linkedin": "https://www.linkedin.com/in/jirisemmler/",
    "email": "mailto:jirka.semmler@gmail.com",
    "location": "Brno, Czech Republic",
    "summary": "I turn complex customer and platform problems into shipped product. At Keboola, I lead a backend team while contributing code across data warehouses, security and integrations. I connect customer discovery, technical decisions and rollout, and use AI in analysis, implementation and review."
  },
  "nav": [
    {
      "id": "profile",
      "label": "Profile"
    },
    {
      "id": "play",
      "label": "Play"
    },
    {
      "id": "ai",
      "label": "AI stack"
    },
    {
      "id": "cases",
      "label": "Case studies"
    }
  ],
  "ai": {
    "nodes": [
      {
        "id": "kryton",
        "label": "Kryton",
        "use": "Code review",
        "zone": "work",
        "detail": "Semi-automatic code review and approvals, orchestrated by Hermes, with my own review desk for monitoring. The team's merged-PR throughput tripled. Getting close to a dark factory.",
        "how": "Hermes orchestration · job queue · Slack · review desk"
      },
      {
        "id": "holly",
        "label": "Holly",
        "use": "Running the house",
        "zone": "home",
        "detail": "Runs the household.",
        "how": "Hermes agent · Home Assistant · Nabu voice module · Slack"
      },
      {
        "id": "grokbot",
        "label": "Grokbot",
        "use": "Proactive personal assistant",
        "zone": "knowledge",
        "detail": "Dedicated agents running my agenda.",
        "how": "Main day-to-day assistant"
      },
      {
        "id": "claude",
        "label": "Claude",
        "use": "Delivery work in code",
        "zone": "work",
        "detail": "Coding agent for day-to-day delivery. It also runs the scheduled Scout sessions above.",
        "how": "Claude Code on my laptop"
      },
      {
        "id": "codex",
        "label": "Codex",
        "use": "Second opinion on the setup",
        "zone": "work",
        "detail": "A second coding agent: it audits and improves the setup itself, works with my notes and builds supporting tools.",
        "how": "Codex on my laptop"
      }
    ],
    "edges": [
      [
        "kryton",
        "review"
      ],
      [
        "holly",
        "home"
      ],
      [
        "grokbot",
        "assist"
      ],
      [
        "claude",
        "code"
      ],
      [
        "codex",
        "organize"
      ]
    ],
    "footnotes": [
      "Trpaslík",
      "Nova5 VM",
      "Home Assistant on Pi"
    ],
    "holister": "Holister — private monitoring view (not a metrics dump).",
    "note": "v1 uses screenshots / short clips only — no live demos.",
    "intro": "I run a small personal AI setup across three parts of my life: home, work and my own knowledge. Each use case has its own assistant with a clear job and a point where I decide.",
    "principles": [
      {
        "title": "Tightly scoped tools",
        "text": "Each agent has one job and only the permissions that job needs."
      },
      {
        "title": "Human in the loop",
        "text": "Agents prepare and propose; the consequential steps stay with a person."
      },
      {
        "title": "Isolation between contexts",
        "text": "The work agent runs in a firewalled virtual machine with no access to my home network."
      },
      {
        "title": "Monitoring from day one",
        "text": "A read-only page shows whether every agent, device and review job is healthy — I watch the system instead of guessing."
      }
    ],
    "zones": [
      {
        "id": "home",
        "label": "Home"
      },
      {
        "id": "work",
        "label": "Work (isolated)"
      },
      {
        "id": "knowledge",
        "label": "Assistance"
      }
    ],
    "workflow": {
      "title": "From meetings to memory",
      "intro": "Most of a working day leaves a trail: meetings, Slack threads, tickets, pull requests. Three tools turn that trail into a task list I can trust and into long-term notes. Wherever a mistake would cost something, the decision stays with me.",
      "stages": [
        {
          "kicker": "capture",
          "label": "Meetings and work signals",
          "text": "Meetings are transcribed locally on my laptop; no bot joins the call. The rest comes from tools I already use.",
          "items": [
            "Meeting transcripts (Transcripted)",
            "Slack and e-mail",
            "Calendar",
            "Linear and GitHub"
          ]
        },
        {
          "kicker": "work assistant",
          "label": "Scout",
          "text": "Scheduled sessions read what is new and reconcile it with what is already known.",
          "items": [
            "Routes each transcript to its meeting and writes a summary",
            "Pulls out decisions and candidate tasks; a candidate is not a commitment until confirmed",
            "Keeps one running list of action items",
            "Maintains a work knowledge base",
            "Writes the morning briefing, meeting prep and the weekly report"
          ]
        },
        {
          "gate": true,
          "kicker": "boundary",
          "label": "Sanitised harvest",
          "text": "Work and private memory are separate. Only lasting lessons cross, and only as proposals.",
          "items": [
            "Picks what stays useful: transferable experience, my own contribution, outcomes",
            "Leaves out internal metrics, prices, quotes, contacts and anything under NDA",
            "Clear items are filed; unclear or sensitive ones wait for me"
          ]
        },
        {
          "kicker": "second brain",
          "label": "Picard",
          "text": "A private Markdown vault that I and my coding agents read before starting work.",
          "items": [
            "Sources kept unchanged",
            "A maintained wiki of concepts, patterns and decisions, each linked to its source",
            "Projects, goals and career notes",
            "Shared skills for Claude Code and Codex"
          ]
        }
      ],
      "loop": {
        "label": "Me: the decisions stay with a person",
        "items": [
          "I confirm which extracted tasks are real commitments",
          "Unclear or sensitive notes reach me as questions; they are never filed silently",
          "A source that goes dark is reported as an outage, never silently skipped"
        ]
      },
      "dayLabel": "A working day, as scheduled",
      "day": [
        {
          "time": "Morning",
          "title": "Briefing",
          "text": "Today's focus, open items and prep for the day's meetings."
        },
        {
          "time": "After standup",
          "title": "Standup notes",
          "text": "Notes and action items from the recording, plus a check of yesterday's open ones."
        },
        {
          "time": "Every hour",
          "title": "Transcript triage",
          "text": "New meeting transcripts are routed and summarised within the hour."
        },
        {
          "time": "Four times a day",
          "title": "Delta scans",
          "text": "What changed in chat, e-mail, tickets and code since the last run."
        },
        {
          "time": "Afternoon",
          "title": "Harvest and triage",
          "text": "Sanitised lessons are proposed to the second brain, then sorted."
        },
        {
          "time": "Night",
          "title": "Reflection",
          "text": "The assistant tidies its knowledge base and proposes changes to its own rules."
        },
        {
          "time": "Friday",
          "title": "Weekly report",
          "text": "Wins, troubles and priorities for next week."
        }
      ]
    },
    "casesLabel": "Other use cases",
    "toolsLabel": "Tools",
    "tools": [
      "Warp",
      "OpenCode",
      "Obsidian",
      "Scout",
      "Transcripted",
      "Slack",
      "Notion",
      "Tailscale",
      "Linear",
      "GitHub",
      "Cursor",
      "Raycast",
      "Typeless / Wispr Flow",
      "Home Assistant",
      "OrbStack",
      "Agnes"
    ]
  },
  "cases": {
    "intro": "Case studies — each with its own structure. Not a blog.",
    "items": [
      {
        "title": "Snowflake key-pair migration",
        "blurb": "A multi-year, platform-wide security migration under external pressure: phased rollout, product replacements instead of feature removal, and one incident treated as a lesson — not a zero-downtime claim.",
        "headline": "When a vendor turns off passwords, it must not turn off customers.",
        "meta": "Keboola · 2024–2026 · technical owner",
        "summary": "Snowflake announced the end of single-factor passwords for service accounts. For a data platform that connects to Snowflake in dozens of places, that meant rewriting authentication across the whole platform without customers' pipelines stopping. I took it on as technical owner: from the first \"this is red\", through design, phased rollout and my own code, to enforcement on all our accounts two years later. Along the way: one incident, one lesson about communication, and three new product capabilities instead of simply removing the old ones.",
        "facts": [
          {
            "label": "Scope",
            "value": "5k+ projects, 200k+ Snowflake users and 30+ large customers with their own Snowflake accounts; 14 production environments in 3 clouds, 200+ tasks across 9 teams"
          },
          {
            "label": "My role",
            "value": "Technical owner of the programme; assignee of roughly a third of the tasks; author of the design, migration tooling and customer changelogs"
          },
          {
            "label": "Result",
            "value": "Platform side finished and password login switched off on all accounts we operate (September 2026)"
          }
        ],
        "sections": [
          {
            "heading": "The problem",
            "body": [
              "In autumn 2024 Snowflake published a plan to block password sign-in without a second factor. For people that means MFA; for service accounts it means a key pair or another passwordless method.",
              "The platform connected to Snowflake on many levels: root accounts per environment, project users, workspaces for transformations and for people, components, user management in customers' own accounts, test and CI environments. Historically all of it ran on a username and password. At the same time the vendor tightened the rules for people's direct access to a shared database, which hit ways of working customers liked: SQL clients connected straight to a workspace, and BI tools connected through a writer.",
              "No single piece was hard. What was hard: most of the business ran on Snowflake, the deadline was set by the vendor and moved several times, and any mistake meant customer pipelines stopping without warning."
            ]
          },
          {
            "heading": "Decisions and alternatives",
            "body": [
              "In December 2024 I flagged it internally as top priority and set up a regular war room. A handful of decisions then shaped the next two years."
            ],
            "items": [
              {
                "title": "Phased rollout by risk, not big-bang",
                "text": "Internal projects, then pay-as-you-go, larger customers, customers' own accounts, single-tenant — and within each phase environment by environment, by traffic. One platform-wide switch was not an option with zero tolerance for impact."
              },
              {
                "title": "Two-step account migration",
                "text": "Step one only adds a certificate; the password stays. Step two removes the password and switches the user type. There is a fallback between the steps, and step one could be rehearsed on every environment without risk."
              },
              {
                "title": "A switch per component",
                "text": "Every component got a feature flag for the new authentication. More expensive than a hard switch in code, but it let us turn things on in pieces and, above all, turn them back without a release."
              },
              {
                "title": "Replace, don't remove",
                "text": "When direct access to the shared database was banned, the simplest move was to take the access away. Instead three replacements shipped: a component for safely sharing data with BI tools, a SQL editor inside the platform, and a lighter dedicated-account option for customers who wanted to keep their own tools."
              },
              {
                "title": "Negotiate the dates with the vendor",
                "text": "Only during the incident did we learn the vendor could set an enforcement schedule per account. From then on we steered the dates ourselves."
              }
            ]
          },
          {
            "heading": "My role",
            "body": [
              "I was the technical owner of the programme, not only its coordinator. I wrote the design (a matrix of use case × authentication × environment type), the rollout roadmaps, and the migration commands and application migrations that switched project users on every environment. I removed the last way to register an environment with a password from the internal API, moved the platform's end-to-end tests to certificates, added key support to the user-management tooling and a bring-your-own-key option for customers with their own key policy. I wrote the customer changelogs and internal campaigns, approved releases and did the closing audit of environments.",
              "The product and communication side was owned by a colleague from product; it would not have worked without that tandem. The rest was the team: key parts of the first phase, certificate rotation, the migration tool's UI, components and SRE provisioning."
            ]
          },
          {
            "heading": "Delivery with the team",
            "items": [
              {
                "title": "February 2025 — phase 1",
                "text": "Key pairs for root accounts, SSO into workspaces and a backfill of user types on our shared accounts. The internal reaction was sharp: late communication and unclear commercial impact. That was the first big lesson."
              },
              {
                "title": "June–August 2025",
                "text": "New project users are created without a password; the two-step migration of existing users runs environment by environment, single-tenants included."
              },
              {
                "title": "Autumn 2025",
                "text": "A public timeline, key pair as the default for workspaces, a migration tool for customers, the BI replacement component and the SQL editor in production, and the end of direct access on shared accounts."
              },
              {
                "title": "Spring 2026",
                "text": "Clean-up of user objects that did not meet the requirements, certificate rotation as a regular process, no more password-based workspaces."
              },
              {
                "title": "May 2026 — the incident",
                "text": "The vendor started enforcing earlier, and on different accounts, than we expected. In an otherwise finished migration one default parameter in a client library had not been switched. Impact: hundreds of failed jobs in about twenty projects over five hours. I found the root cause within half an hour of escalation; mitigation was switching on a prepared feature flag, with no release. I wrote the post-mortem for customers."
              },
              {
                "title": "May–August 2026 — the campaign",
                "text": "Fewer than a fifth of customer configurations were ready. This time communication ran in four layers: a public changelog with a how-to, a warning in the product on every affected configuration, an overview with per-customer numbers for account managers, and targeted e-mails. Adoption roughly doubled in two months."
              },
              {
                "title": "September 2026 — enforcement",
                "text": "Password authentication switched off on all our accounts, on three dates."
              }
            ]
          },
          {
            "heading": "The result",
            "items": [
              {
                "title": "Whole platform moved",
                "text": "From passwords to key pairs and SSO: root, project and workspace accounts, components, user management, tests and CI."
              },
              {
                "title": "Enforcement without a new incident",
                "text": "Enforcement happened on all accounts we operate; customer impact was handled as ordinary support tickets."
              },
              {
                "title": "Replacements, not just a ban",
                "text": "Customers got replacements for the removed capabilities."
              },
              {
                "title": "One incident, owned",
                "text": "Root cause, mitigation and fix on the same day — and a public post-mortem."
              }
            ]
          },
          {
            "heading": "What I took from it",
            "items": [
              {
                "title": "Closing a migration is an audit, not an announcement",
                "text": "\"Done\" means walking environment by environment, measuring leftover traffic on the old path and writing down the exceptions with reasons. One forgotten TODO was enough for an incident."
              },
              {
                "title": "Customer communication is a product",
                "text": "One line in a changelog is not enough. What worked was the combination of a how-to, a warning in the product, data for the people who talk to customers, and addressed e-mails."
              },
              {
                "title": "A switch is cheaper than a rollback",
                "text": "A feature flag per component paid for itself in a single day."
              },
              {
                "title": "Ask the vendor",
                "text": "The enforcement schedule was negotiable. Knowing that a year earlier would have saved a lot of nerves."
              },
              {
                "title": "Don't migrate with a tool that needs the old way",
                "text": "A migration script that signed in with a password could not migrate an environment without one. The fix was tooling that prepares and verifies the key without a live password connection."
              }
            ]
          }
        ]
      }
    ],
    "coming": "More cases coming."
  },
  "play": {
    "title": "Optional play",
    "blurb": "Corridor — a tiny turn-based grid puzzle. Nothing essential is locked behind it; entertainment only.",
    "unlockJoke": "You unlocked… a rubber duck debugger. It says nothing essential. Quack."
  },
  "pillars": [
    {
      "title": "End-to-end ownership",
      "text": "From an unclear problem through discovery, technical design and rollout — to whether it actually works for the customer."
    },
    {
      "title": "Hands-on technical leadership",
      "text": "I lead a backend team and still design, write and review code. Small things I build myself; bigger ones I deliver through the team."
    },
    {
      "title": "Product–engineering bridge",
      "text": "I translate between customers, product and engineering, and I make the trade-offs explicit."
    },
    {
      "title": "AI as leverage",
      "text": "AI helps me cover more of the path in analysis, implementation and review. The decisions and the quality stay my responsibility."
    }
  ],
  "experience": [
    {
      "company": "Keboola",
      "role": "Engineering Manager & Product Engineer",
      "from": "2024",
      "to": "present",
      "highlights": [
        "Lead a backend team and work hands-on from customer discovery through implementation and rollout across authorization, data warehouses and integrations.",
        "Owned the Snowflake authentication migration across the platform (5k+ projects, 200k+ Snowflake users, 30+ large customers with their own accounts): planned the phased rollout, contributed backend changes and coordinated customer communication with the team.",
        "Introduced AI-assisted analysis, miniRFCs, multi-agent coding and automated code reviews; merged-PR throughput in the team tripled once review was semi-delegated to agents.",
        "Ran a \"Product vibecoding\" workshop for 20 engineers: how to use AI to move faster without wrecking the codebase."
      ]
    },
    {
      "company": "Keboola",
      "role": "Senior Backend Engineer",
      "from": "2021",
      "to": "2023",
      "highlights": [
        "Built integrations for Snowflake, BigQuery, Teradata, Exasol, Synapse and Redshift.",
        "Co-designed and coordinated SOX-related controls required by Groupon: approval workflows, separation of duties and audit trails. The work unlocked a major data platform partnership."
      ]
    },
    {
      "company": "Dactyl Group",
      "role": "Lead Web Developer",
      "from": "2019",
      "to": "2020",
      "highlights": [
        "Led approximately eight web developers while building and delivering client applications hands-on with PHP and JavaScript."
      ]
    },
    {
      "company": "Amadeus IT Group · Nice, France",
      "role": "Web Developer",
      "from": "2017",
      "to": "2018",
      "highlights": [
        "Developed PHP/Silex and AngularJS applications in an international team, helped migrate legacy software and took over team leadership.",
        "The team delivered about 95% of its sprint commitments."
      ]
    }
  ],
  "education": [
    {
      "school": "Brno University of Technology",
      "degree": "MSc, Information Technology",
      "from": "2015",
      "to": "2017"
    },
    {
      "school": "Brno University of Technology",
      "degree": "BSc, Information Technology",
      "from": "2012",
      "to": "2015"
    }
  ],
  "skills": [
    {
      "label": "Engineering",
      "items": [
        "PHP",
        "Python",
        "JavaScript",
        "Backend APIs",
        "Integrations"
      ]
    },
    {
      "label": "Data & cloud",
      "items": [
        "Snowflake",
        "BigQuery",
        "Docker",
        "Terraform",
        "AWS",
        "Google Cloud",
        "Azure"
      ]
    },
    {
      "label": "Ways of working",
      "items": [
        "Product discovery",
        "Engineering leadership",
        "AI-assisted development"
      ]
    }
  ],
  "contact": {
    "line": "The best way to reach me is a short message — what you are working on and where I might fit.",
    "items": [
      {
        "label": "Email",
        "text": "jirka.semmler@gmail.com",
        "href": "mailto:jirka.semmler@gmail.com"
      },
      {
        "label": "LinkedIn",
        "text": "linkedin.com/in/jirisemmler",
        "href": "https://www.linkedin.com/in/jirisemmler/"
      }
    ]
  },
  "recruiters": {
    "title": "For recruiters",
    "intro": "Short answers to the questions that usually come first.",
    "items": [
      {
        "label": "Current role",
        "text": "Engineering Manager & Product Engineer at Keboola. I am actively looking for a new role as a Product Engineer or Engineering Manager."
      },
      {
        "label": "Roles that fit",
        "text": "Product Engineer or hands-on engineering lead in a product-driven company: close to customers, close to the code, with AI as a normal part of how the team builds."
      },
      {
        "label": "Where",
        "text": "Based in Brno, Czech Republic. Remote-first within European time zones, with travel when it has a purpose."
      },
      {
        "label": "Languages",
        "text": "Czech (native), English (professional)."
      },
      {
        "label": "Best first step",
        "text": "A short e-mail with what you are working on and where I might fit."
      }
    ]
  }
}
