---
title: Ecomflow
description: Dutch e-commerce fulfilment/logistics tech company; Jan Wilmake completed second interview with Thom van Lieshout on June 25, 2026 after AI Engineer interview (June 12) and practical case study
category: Organizations
---

# Ecomflow

**Ecomflow** (`ecomflow.com`) is a Dutch e-commerce fulfilment and logistics technology company with connections to Hong Kong supply-chain operations. [[Jan_Wilmake]] completed an **AI Engineer interview** with Ecomflow on Friday, June 12, 2026.[^activity-2026-06-12]

## Company

Ecomflow builds technology for e-commerce fulfilment and logistics. Based on job listings observed during Jan's research, the company's tech stack includes Kubernetes, PostgreSQL, TypeScript, and event-driven architecture. Active openings as of June 2026 included Chief Technology Officer and Senior Infrastructure Engineer roles — suggesting a growing engineering organisation.[^activity-2026-06-12] [^activity-2026-06-10]

Key people identified during Jan's research:

- **Thom van Lieshout** — likely the interviewer or a team member; Jan reviewed his LinkedIn profile and posts multiple times across June 10–12[^activity-2026-06-12]
- **Daniel Dalen** — LinkedIn profile (based in Hong Kong) looked up during the interview itself[^activity-2026-06-12]

## Interview Timeline

| Date | Event |
|------|-------|
| June 10, 2026 | Formal interview invitation received: *"Invitation: Jan \| Wijnand Karsens (AI Engineer - Interview) @ Fri Jun 12, 2026 10:30am – 11am (CEST)"*[^activity-2026-06-10] |
| June 10, 2026 | Initial research: browsed Ecomflow company people page and job listings on LinkedIn[^activity-2026-06-10] |
| June 11, 2026 | Re-confirmed interview invitation via email[^activity-2026-06-11] |
| June 12, 2026 (07:39–08:39) | **Intensive pre-interview preparation**: reviewed LinkedIn listing 8+ times, browsed ecomflow.com/about, /jobs, CTO posting, Senior Infrastructure Engineer listing, Thom van Lieshout's LinkedIn and posts; also checked own GitHub repos filtered for "eval" and "mcp", reviewed LLMTEXT-mcp and universal-mcp-oauth repos, and read the Parallel Task MCP blog post — assembling talking points[^activity-2026-06-12] |
| June 12, 2026 (~08:40–09:22) | **AI Engineer interview completed** via Google Meet (`afv-vfgc-eoz`); ~40 minutes; during the call Jan looked up Daniel Dalen (Hong Kong) and Googled "SAP" — suggesting discussion of enterprise integrations[^activity-2026-06-12] |
| June 12, 2026 (10:13–10:17) | Post-interview deep dive: explored ecomflow.com/about, /jobs, CTO job, and Senior Infra Engineer listing[^activity-2026-06-12] |
| June 12, 2026 (10:28) | Checked an email with no subject from an Ecomflow-related sender[^activity-2026-06-12] |

### Preparation Quality

Jan's pre-interview preparation was notably thorough — the most intensive interview prep observed in the 2026 job search. He spent approximately one hour before the call reviewing the listing, researching team members, refreshing his own relevant GitHub repos (MCP projects, eval frameworks), and reading Parallel's Task MCP blog post to have concrete examples ready. This contrasts with the minimal preparation for the [[Blixt]] call (36 seconds of research) and is consistent with the more diligent approach seen in the [[Foreside]] and IMAGIN.studio preparations.[^activity-2026-06-12]

### Post-Interview Status

As of June 12 end-of-day, no thank-you email had been sent. Jan's afternoon included a second meeting (with Umid Ghimire), a Hostaway application, and leisure activities — suggesting mental decompression after an intense morning. The 35-minute deep-read of a "Product Engineer - Squads" Notion spec in the evening indicates Jan is keeping multiple options open regardless of the Ecomflow outcome.[^goals-2026-06-12]

As of June 14 — **3 days post-interview** — no thank-you or follow-up email had been sent to Thom van Lieshout or anyone at Ecomflow. June 13 was consumed entirely by the [[Hyre]] MCP assessment, and June 14 was dominated by [[World_Cup_2026|World Cup football]] — neither day included any Ecomflow-related activity.[^goals-2026-06-14]

As of **June 17 — 5 days post-interview** — the follow-up remains unactioned. The GOALS document (updated June 17) flags this as "last chance" — at 7 days the thread is statistically closed. The days since the interview have been consumed by Hyre assessment prep (June 13), World Cup (June 14), IMAGIN.studio/Hyre calendar management (June 15), the Hyre intro call (June 16), and in-person Hyre meetings (June 17). The pipeline had decisively shifted to [[Hyre]] and [[IMAGIN_studio]] as the active frontrunners.[^goals-2026-06-17]

### June 19: Practical Case Study — Pipeline Re-Opened

On **June 19**, the Ecomflow thread unexpectedly re-opened. Jan re-read the email *"Ecomflow AI Engineer: practical case study"* **three times** between 12:20 and 12:23 — a clear signal that Ecomflow had sent a take-home coding/case study assignment, likely from Thom van Lieshout. This was 8 days after the original interview — far later than the presumed dead-thread window.[^activity-2026-06-19]

The triple-read pattern without immediate action suggests Jan is weighing whether to invest time in the case study while simultaneously waiting for outcomes from [[Hyre]] and [[IMAGIN_studio]]. As of June 20, no case study submission or response is visible in browser history.[^goals-2026-06-20]

The GOALS document (updated June 20) identifies this as a **time-sensitive assignment** with a likely 3–5 day deadline, and raises the strategic question: with Hyre and IMAGIN.studio both in late-stage, should Jan invest in the Ecomflow case study as a hedge?[^goals-2026-06-20]

### June 22: Loom Onboarding and Case Study Progress

On June 22, the Ecomflow case study thread showed further signs of active engagement:[^activity-2026-06-22]

- **08:33** — Jan started **Loom onboarding** (~30 seconds) — likely setting up Loom to record a video walkthrough as part of the case study deliverable
- **10:46** — Opened an **"OrderSupport Agent Demo, Evaluation Results"** Loom video (~7 seconds) — an AI agent demo with evaluation results, likely the reference implementation or example provided by Ecomflow for the case study
- **10:45–10:51** — Re-read the *"Ecomflow AI Engineer: practical case study"* email 3 times (~4 minutes total) — continuing to study the assignment requirements

The Loom onboarding strongly suggests the case study requires a **video demonstration** of Jan's solution — a format consistent with modern AI engineer hiring where candidates must demo working systems rather than submit static code. The OrderSupport Agent Demo video appears to be Ecomflow's own product demo, provided as context for the assignment.[^activity-2026-06-22]

On **June 21**, Jan also briefly checked the Ecomflow email during a morning Fastmail session — maintaining awareness of the assignment during an otherwise quiet Sunday.[^activity-2026-06-21]

### June 25: Second Interview with Thom van Lieshout — Completed

A **calendar invite** for *"Jan <> Thom"* was confirmed for **Thursday, June 25, 2026, 1:00–1:45 PM CEST** — a meeting with **Thom van Lieshout** from Ecomflow, arranged by recruiter **Wijnand Karsens** (wijnand@karsens.com). Jan reviewed this invitation via email on June 24 at 14:42.[^activity-2026-06-24] [^activity-2026-06-25]

#### Pre-Interview Preparation

The morning of June 25 was devoted to intensive Ecomflow research:[^activity-2026-06-25]

- **08:04–08:06** — Located Ecomflow's office at **Ringwade 6, Nieuwegein** on Google Maps; checked driving directions from [[Groningen]] (~2h)
- **10:02** — YouTube search for "ecomflow"
- **10:06–10:23** — Watched *"Inside the system powering modern supply-chains"* Ecomflow video (~13 min)
- **10:13–10:23** — Watched *"This is how we build world-first features for shipping parcels worldwide"* (~10 min)
- **10:46** — Viewed an **OrderSupport Agent Demo** Loom video with evaluation results
- **10:49–10:51** — Deep-dive into ecomflow.com (about page, partners page)
- **10:52–10:56** — Researched ecommerce terminology: *"in ecommerce what's 3PL"*, *"ecomflow china"*, *"m2c ecomflow"*

#### Interview

The interview took place via **Google Meet** at approximately **11:28–11:40** (~15 minutes of recorded Meet time). Immediately after, Jan Googled *"cosine similarity"* — a quick AI/ML concept lookup likely prompted by a topic discussed during the call.[^activity-2026-06-25]

#### Housing Search Linked to Ecomflow

The morning of June 25 also saw Jan searching for **rental properties in the Utrecht area** on Funda — specifically in **Utrecht, Houten, and Nieuwegein** (≤€1,750/month). This is notable because Ecomflow's office is at **Ringwade 6, 3439 LM Nieuwegein** — the same address Jan looked up on Google Maps from [[Groningen]] on June 22. The Utrecht housing search appears directly motivated by the Ecomflow opportunity, representing the first time Jan's [[Amsterdam_Relocation|housing search]] has shifted away from the Amsterdam metropolitan area toward the Utrecht region.[^activity-2026-06-25]

Specific apartments viewed on Funda:
- **Olivierdreef 35, 3562 LJ Utrecht** (~1m 46s viewing)
- **Hoola van Nootenstraat 251, 3521 HB Utrecht** (~11s viewing)

#### June 26: Housing Pivots Back to Amsterdam

Notably, the day after the Ecomflow interview, Jan's housing search **pivoted back to Amsterdam** — browsing rentals in the €2,200–3,000/month range on Funda and Pararius (Eerste Jan Steenstraat €2,500, Rustenburgerstraat €2,800, Sint Willibrordusstraat €2,700). The higher budget range compared to the Nieuwegein search may reflect recalibration based on the interview outcome or a recognition that Amsterdam remains the primary target for other pipeline opportunities ([[Hyre]], [[IMAGIN_studio]]).[^activity-2026-06-26]

### Post-Interview Deep-Dive

On the evening of June 12, Jan watched Ecomflow YouTube content about Hong Kong logistics and supply chains for approximately 25 minutes — suggesting genuine intellectual engagement with the company's domain. This is one of Jan's stronger post-interview signals; however, the engagement has not been translated into outbound communication.[^activity-2026-06-12]

## Fit with Jan Wilmake's Profile

The AI Engineer role aligns well with Jan's profile:

- **TypeScript/AI stack** — Jan's core expertise matches Ecomflow's tech requirements
- **MCP and agent infrastructure** — Jan's extensive work on [[LLMTEXT]], [[uithub]], and [[Parallel_AI]] MCP integrations provides directly relevant experience
- **Remote** — the role is listed as remote, compatible with Jan's current [[Groningen]] base and [[Amsterdam_Relocation|planned Amsterdam move]]

## See Also

- [[Career_Plan_2026]]
- [[Jan_Wilmake]]
- [[Parallel_AI]]
- [[LLMTEXT]]
- [[Foreside]]
- [[Tibber]]
- [[Van_Dorp]]

[^activity-2026-06-10]: Activity summary: `x-archive/raw/activity-summary/2026-06-10.md`
[^activity-2026-06-11]: Activity summary: `x-archive/raw/activity-summary/2026-06-11.md`
[^activity-2026-06-12]: Activity summary: `x-archive/raw/activity-summary/2026-06-12.md`
[^goals-2026-06-12]: Goals document: `x-archive/entries/GOALS.md` (updated 2026-06-12)
[^goals-2026-06-14]: Goals document: `x-archive/entries/GOALS.md` (updated 2026-06-14)
[^goals-2026-06-17]: Goals document: `x-archive/entries/GOALS.md` (updated 2026-06-17)
[^activity-2026-06-19]: Activity summary: `x-archive/raw/activity-summary/2026-06-19.md`
[^goals-2026-06-20]: Goals document: `x-archive/entries/GOALS.md` (updated 2026-06-20)
[^activity-2026-06-21]: Activity summary: `x-archive/raw/activity-summary/2026-06-21.md`
[^activity-2026-06-22]: Activity summary: `x-archive/raw/activity-summary/2026-06-22.md`
[^activity-2026-06-24]: Activity summary: `x-archive/raw/activity-summary/2026-06-24.md`
[^activity-2026-06-25]: Activity summary: `x-archive/raw/activity-summary/2026-06-25.md`
[^activity-2026-06-26]: Activity summary: `x-archive/raw/activity-summary/2026-06-26.md`