# Jens Neuse

CEO & Co-Founder at WunderGraph

## Bio

Jens Neuse is the CEO and one of the co-founders of WunderGraph, where he builds scalable API infrastructure with a focus on federation and AI-native workflows. Formerly an engineer at Tyk Technologies, he created graphql-go-tools, now widely used in the open source community. Jens designed the original WunderGraph SDK and led its evolution into Cosmo, an open-source federation platform adopted by global enterprises. He writes about systems design, organizational structure, and how Conway's Law shapes API architecture.

[Twitter](https://twitter.com/TheWorstFounder)  [LinkedIn](https://www.linkedin.com/in/jens-neuse-706673195/)  [GitHub @jensneuse](https://github.com/jensneuse)

## Blog Posts

### [The Three Bottlenecks AI Can't Code Away](/content/blog/ai-coding-bottlenecks/index.html)
*Blog*
*April 22, 2026*

AI writes 42% of code, but engineering teams aren't shipping faster. The bottleneck moved to coordination, governance, and review. Here's how GraphQL Federation fixes all three.

### [GraphQL vs REST: 18 Claims Fact-Checked with Primary Sources (2026)](/content/blog/fact-checking-graphql-vs-rest/index.html)
*Blog*
*April 13, 2026*

We fact-checked 18 claims comparing GraphQL and REST against peer-reviewed research, official docs, and security reports. Only 3 held up. Here's what the evidence actually says.

### [How the Fission Algorithm Works for Top‑Down GraphQL Federation Schema Design](/content/blog/fission-algorithm-deep-dive/index.html)
*Blog*
*April 5, 2026*

A technical deep dive into the Fission algorithm, how it decomposes a consumer-facing supergraph into subgraph responsibilities, automating the hardest part of GraphQL Federation at scale.

### [GraphQL Federation Schema Changes: From Months to Days with Hub](/content/blog/graphql-federation-schema-collaboration-case-study/index.html)
*Blog*
*March 30, 2026*

Schema changes went from 9 weeks to days after this enterprise team adopted Hub for their 60+ subgraph federation setup.

### [Microservice Dependencies: How @requires Makes Them Explicit](/content/blog/microservice-dependencies-graphql-federation-requires-provides/index.html)
*Blog*
*March 22, 2026*

Learn the different types of microservice coupling and how GraphQL Federation's @requires directive makes cross-service dependencies explicit, visible, and validated at build time.

### [GraphQL Is the API Layer AI Agents Actually Need](/content/blog/graphql-api-layer-for-ai-agents/index.html)
*Blog*
*March 19, 2026*

AI agents need to discover and call APIs with minimal tokens. The GraphQL supergraph gives them a typed, navigable schema across your entire organization.

### [The Dream Query: Consumer-First GraphQL API Design](/content/blog/dream-query-design-apis-from-consumer-out/index.html)
*Blog*
*March 15, 2026*

Start with the query your consumer would write if there were no constraints, then work backwards. A practical guide to consumer-first GraphQL schema design.

### [Design Like a Monolith, Implement as Microservices](/content/blog/design-like-monolith-implement-as-microservices/index.html)
*Blog*
*March 12, 2026*

The monolith vs. microservices debate is a false choice. Learn how to design a coherent API surface while distributing implementation across teams with GraphQL Federation.

### [Why Platform Engineering Teams Become Bottlenecks at Scale](/content/blog/platform-engineering-team-bottleneck/index.html)
*Blog*
*March 10, 2026*

Platform engineering teams are drowning in requests. Not because they are understaffed, but because every API change in the organization flows through them. Here is how to fix the bottleneck without adding headcount.