Skip to main content
Jimmy Jansen

Experience

Download PDF

I like turning messy systems into something that actually works and ships.

TL;DR

  • Principal Engineer at Storyteq. Led platform consolidation across three products and twelve teams, then took the unified system to global rollout.
  • Established the architecture decision practice (ADRs, RFCs, design reviews). Most teams ship with it now.
  • Three years on Rangle's support squad across 30+ client engagements, dropped into systems I didn't build, in domains I didn't know, and found the load-bearing problem.
  • Shipped customer-facing products: video personalization at high-throughput scale, mobile apps, and client product builds across startups, scaleups, and enterprises.
  • Across web, mobile, video, IoT, and consultancy. Engineering depth in product, performance, and platform.

Principal Engineer

– Current
Storyteq B.V. website ↗

I work on our video platform, which is really several products stitched together over the years. My job is making them work as one platform for the customers using them, the teams building them, and the people keeping them running. The work spans teams, systems, and leadership levels, connecting technical direction with delivery reality.

Rendering architecture

High-volume templated video where one creative fans out into many platform and market variants in long-running bursts across tenants.

The hard parts are fair scheduling, template-level reuse, and deadline-aware queueing under load that goes from idle to 50k+ requests in a second.

Legacy stabilization

A tightly-coupled estate where shared databases, chained services, and deploy coupling meant one team's change could break another team's product.

Redrawing service and data boundaries so teams can ship independently, and pulling deploy coupling out of the critical path.

Platform consolidation

Three product platforms merging into one. The hard part was the data: three models that had to keep talking to each other while old customers stayed on the old systems and new ones came up on the unified surface.

Twelve teams, five months, and architecture decisions that couldn't break any account, especially the big ones sales was watching. Then took the unified system to global rollout.

Architecture practice

Establishing the decision practices the org now runs on: ADRs, RFCs, and design reviews adopted across most teams.

Pushing end-to-end ownership of each domain into the teams that build it, with feature flags and CI/CD as the default delivery posture.

Technical strategy

Helping shape the technical side of every roadmap at quarterly planning, with each domain's lead carrying the deep work.

Keeping twelve teams aligned on direction as the platform comes together, so the calls made in one domain don't break the others.

How I work
  • I treat decisions as artefacts. If it's worth doing, it's worth an ADR. And if no one can find the ADR later, the decision didn't really happen.
  • I'd rather make a domain boundary clear than perfect. Most architecture pain comes from fuzzy ownership, not bad code.
  • I work hardest on the parts of a system that only a few people understand. Knowledge concentrated in heads is a load-bearing dependency, and I'd rather pay it down than route around it.
  • I connect technical direction with delivery reality. Which mostly means saying no to clean architectures that won't survive contact with how teams actually ship.

Staff Software Engineer

–
Rangle.io website ↗

Three years on Rangle's support squad. The engineer brought in when a client team was behind, stuck, or coming back from a difficult engagement. Across 30+ projects, the work ranged from short delivery boosts when a team needed to make a date, to large architectural recoveries after a build had gone sideways. Modernization, performance, design systems, mentoring, workshops. Whatever the load-bearing problem was that week. Came in, found it, left the team able to keep going.

Key Achievements

  • – Helped modernize a 10M+ line legacy codebase, working on the architecture seams that let teams ship without breaking each other.
  • – Architected and reviewed across stacks I did not build, in domains I did not know two weeks earlier: e-commerce, B2B SaaS, marketplace, retail, and workspace platforms.
  • – Ran workshops, paired heavily, and mentored developers as part of nearly every engagement. Some of those workshops were opened Rangle-wide so engineers on other assignments could join. The team-enablement piece was usually what made the technical work hold after I left.
  • – Built a greenfield platform for a startup that crossed a million in revenue in its first eight weeks.

Approach & Impact

  • – Comfortable being dropped into systems I did not build, in domains I did not know, and finding the real problem under the surface complaint.
  • – Aligned business, design, and engineering by making the trade-offs visible rather than hidden in tickets. The rooms where consultants stop being useful are the ones where they keep their opinions to themselves.
Notable clients

Endy · Emburse · Staples · Varis · Flexday · MoveBuddy

Senior Software Engineer

–
Albelli website ↗

Five and a half years on the mobile app for iOS and Android. I joined after an outside consultancy had built the initial PoC in Cordova, and left it as a serious mobile revenue channel doing thirty-five million a year, with its own team, its own framework, and a release cadence the rest of the business could plan around. Engineering depth on product flows, performance, and the platform underneath.

Key Achievements

  • – Led the migration from Cordova to a custom hybrid framework, recovering the performance budget the app needed to keep growing.
  • – Built core product flows for books, calendars, mugs, and wall decor, including a 3D mug customization feature.
  • – Rebuilt the CI/CD pipeline so builds went from slow and flaky to fast and reliable, which changed how the team shipped.

Approach & Impact

  • – Mentored junior developers through regular pairing, and set up the testing posture that kept production bugs down as the app scaled.
  • – Optimized startup, memory, and patterns other teams could reuse, so improvements compounded instead of staying local.

Early Career

Software Engineer

–
Quby website ↗

R&D on the Toon Smart Energy Meter. Early product engineering across mobile, smartwatch, and IoT, including one of the first smartwatch apps to control a home thermostat. The engineering foundation underneath everything that came later.

Student Assistant

Hogeschool van Amsterdam
–

Intern

Vattenfall
–

Junior Software Engineer

Javaland
–

Junior Software Engineer

Securityalert4you
–