GraphQL training for teams
Our GraphQL, Hot Chocolate, and Fusion curriculum teaches in depth and works really well. It also isn't set in stone, so we shape every engagement to the team in the room.
Where is your team today?
The curriculum is the same set of building blocks. The order, the depth, and the exercises change for the room.
Heard of GraphQL. Maybe shipped a toy server.
We start from REST instincts and rebuild them. By the end of week one your team can read a schema, write resolvers with confidence, and stop confusing fields with arguments.
What we cover
Half the team has shipped. Half the team is bluffing.
The most common shape we see. We split sessions into shared foundations plus parallel tracks, so nobody is bored and nobody is lost. Everyone leaves on the same page.
What we cover
Schemas in production. Now the corners get sharp.
For teams already shipping GraphQL who want to go deeper. We focus on the parts that hurt at scale: schema design, performance, federation with Fusion, and operating Hot Chocolate in anger.
What we cover
Two ways to run it
Both engagements use the same curriculum and trainers. They differ in how much hands-on project work sits at the center of the engagement.
Flexible curriculum, shaped to your team
Combine instruction, examples, and exercises across GraphQL, Hot Chocolate, Fusion, Nitro, and client development. We adjust the depth to the team in the room.
What is in the box
Hands on, with a real project at the end
Work through an agreed project using ASP.NET Core and Hot Chocolate, with optional Fusion or client topics. The emphasis is on applying the patterns, not copying a finished sample.
What is in the box
By the end of the training
No certificate-printer outcomes. These are the things your team walks away able to do, wherever they started.
Navigate a large GraphQL schema, recognize the common shapes, and explain why a type is modeled the way it is.
Move from simple fields to data loaders and pagination with patterns that scale instead of snippets that bite later.
Use fragments, variables, and error handling to structure a Relay or Apollo client the next person on the team can maintain.
Open a trace, read the plan, find the N+1, and know which Hot Chocolate patterns to reach for before turning to hacks.
Know when to split a schema, when not to, and how Hot Chocolate Fusion fits with the platform you already run.
Give backend, frontend, and platform engineers one shared vocabulary, so the next design review is faster and friendlier.
Delivery format
We have run training in all three formats. Pick the one that fits your calendar and your office, not the other way around.
A trainer joins your team in a room with a whiteboard and proper coffee. Best when you want the focused energy of being out of inboxes for a week.
Best for a single co-located team that can clear the calendar.
Live sessions over your call tool of choice, with shared notebooks, breakout rooms, and homework between days so timezones do not become a wall.
Best for distributed teams or when travel does not make business sense.
Deliberate breakout design and exercises that work for the people in the room and the people on the call, with a good A/V setup so nobody is half-present.
Best when part of the team can fly in and part cannot.
Training that nobody enjoys does not stick. We run sessions like the workshops we wish we had been to: hands on, slightly informal, no slide marathons, room for questions that start with “this is probably stupid but...” (it is not).
What we will not do
Common questions
Send the team size, current GraphQL level, topics you want to cover, preferred format, and a few dates that work. We will reply with a concrete proposal, not another form to fill in.