Blixt

From Jan Wilmake's personal knowledge base

Blixt

Blixt is an early-stage startup building AI-driven automated integration testing, founded by Floris Weers. Jan_Wilmake completed an introductory call with Floris on May 20, 2026 as part of his 2026 job search.[1]

Product

Blixt builds an AI-powered system for automatic integration testing — featuring multiplayer flows, live user switching, real browser clicks, payment simulation, email interactions, and file uploads. Floris Weers described the product in an X post on May 20 as a browser-based integration test system that can simulate complex, multi-user interactions on social network demos and payment flows.[1]

A related post from the @blixt X account described the system as using AI-driven automated tests with a forked database and multiplayer simulation — positioning it as end-to-end testing infrastructure that goes beyond traditional unit or integration test approaches.[1]

Interview Timeline

DateEvent
May 14, 2026Calendar invite received: "Jan/Floris/Blixt @ Wed May 20, 2026 3pm - 3:30pm (CEST)"[2]
May 15–19, 2026No research into Blixt observed in browser history, X, or email[3]
May 20, 2026 (morning)Last-minute preparation: Jan read Floris Weers' and Blixt's X posts about the integration testing product (~36 seconds combined) just before the call[1]
May 20, 2026 (~13:00–13:30)Intro call completed via Google Meet with Floris Weers; Jan showed the OpenPolsia dashboard during the call[1]
May 21–26, 2026No post-call follow-up sent — 6 days overdue as of May 26[4] [5] [6]

May 20: Intro Call Completed

The Blixt intro call took place on May 20, 2026 — running from approximately 13:00 to 13:30 CEST (earlier than the originally scheduled 15:00 slot). The call was conducted via Google Meet. Just before the call (~12:59–13:00), Jan performed last-minute research, reading Floris Weers' X post about browser-based automatic integration tests and Blixt's post about AI-driven automated testing with forked databases.[1]

During the call, Jan briefly visited the OpenPolsia dashboard at ~13:14 — demonstrating his autonomous business-agent work as a portfolio piece. He also briefly checked the OpenPolsia GitHub source code (janwilmake/openpolsia/src/pages) at ~13:16.[1]

Preparation Gap

Prior to the last-minute X research on the morning of May 20, zero research into Blixt had been observed in Jan's browser or X activity across the six days since the invite arrived. This contrasts with Jan's approach to other pipeline targets — he researched Moyai's blog extensively, prepared a full PDF slide deck, spent 6 minutes on Ives_van_Hoorne's X profile before the Biscuit meeting, and researched Arsen Ibragimov's LinkedIn before the Topliner call.[3]

Post-Call Follow-Up (Overdue)

As of May 28, 2026 — eight days after the call — no post-call follow-up email or message to Floris Weers has been observed. The intervening days were dominated by leisure activities: May 21 was consumed by Color Block Jam (~6 hours) and JRE #2503 (Eric Weinstein); May 22 by Graham Hancock videos, Color Block Jam, and JRE #2504 (Skylar Grey); May 23 was a marathon ~75-level Color Block Jam session followed by watching Mickey 17 on Netflix; May 24 continued with more Color Block Jam (level 631+) and YouTube geography content; May 25 introduced wildcamping trip planning and gear purchases; May 26 was dominated by the MCP 2026-07-28 release candidate spec, LinkedIn messaging, and documentaries; May 27 was an ancient Mesoamerican history rabbit hole culminating in watching The Other Conquest (1999) in full.[7] [8] [9] [5] [10]

On May 28 — the morning of the HACKADAM meetup — Jan resumed active job browsing on LinkedIn (09:46–10:30+), scrolling through 100+ recommended positions and applying to new roles, but sent no Blixt-related communication.[11]

May 29–30 continued the forward-looking job search pattern: Jan applied to an Itproposal Front-end Engineer role, browsed CIMSOLUTIONS vacancies, updated his LinkedIn profile, and received a calendar invite for an intro call with Foreside on June 2. No Blixt-related activity was recorded.[12]

As of May 30, the Blixt post-call follow-up is 10 days overdue. The GOALS document (updated May 23) identified this follow-up as urgent with critical-to-cold status across the board. At 10 days with no communication from either side, this opportunity is dead.[4]

Fit with Jan Wilmake's Profile

Blixt's focus on automated integration testing in the browser overlaps with Jan's experience building ProductSim (AI-powered E2E browser testing on PR preview deploys, launched April 15, 2026). Jan's full-stack "build-from-scratch" profile — validated by @MShaiz9 on X as exactly what early-stage startups need — aligns well with Blixt's early-stage, founder-led nature.[13]

See Also

References

  1. Activity summary: x-archive/raw/activity-summary/2026-05-20.md 
  2. Activity summary: x-archive/raw/activity-summary/2026-05-14.md 
  3. Goals document: x-archive/entries/GOALS.md (updated 2026-05-20) 
  4. Goals document: x-archive/entries/GOALS.md (updated 2026-05-23) 
  5. Activity summary: x-archive/raw/activity-summary/2026-05-25.md 
  6. Activity summary: x-archive/raw/activity-summary/2026-05-26.md 
  7. Activity summary: x-archive/raw/activity-summary/2026-05-22.md 
  8. Activity summary: x-archive/raw/activity-summary/2026-05-23.md 
  9. Activity summary: x-archive/raw/activity-summary/2026-05-24.md 
  10. Activity summary: x-archive/raw/activity-summary/2026-05-27.md 
  11. Activity summary: x-archive/raw/activity-summary/2026-05-28.md 
  12. Activity summary: x-archive/raw/activity-summary/2026-05-29.md 
  13. Activity summary: x-archive/raw/activity-summary/2026-05-18.md