Home / Technical Skills / Technical Content Designer Program
Content designers who understand developer environments, tools, and mental models have greater impact. This 6-week program builds confidence through hands-on work with technical tools, AI, and the methods developers actually use.
All sessions
Meet your peers
On completion

Senior Content Designer, Microsoft
Jeremy Hoover has spent 10 years collaborating with engineers and product teams on developer-facing tools — IDEs, APIs, CLIs, MCPs, and CI/CD workflows. He leads workshops on technical fluency in content design.
Next cohort
US $1200
Applications close August 15.
JOIN THE WAITLIST
Need an invoice or PO? Let us know.
Content designers new to technical concepts.
Content designers who work closely with developers.
Content designers who want to understand how products are built.
Content professionals who want to understand repos and dev tools.
Our courses are created by experts, informed by hiring managers, and reflect industry best practice.
Students trained
Teams trained
Countries
01
Confidence navigating technical environments. Open an unfamiliar repository and find where content lives.
02
Understand how products are structured, where content decisions originate, and where content can shape product outcomes.
03
Read diffs, pull requests, make content edits in a feature branch, and participate in code review as a content designer.
04
Use AI to interpret unfamiliar code, run commands, work within tools like GitHub, and support your work directly.
A complete system for learning, practicing, and proving your skills.
Live sessions with expert instruction and guidance.
Learn by doing, and get answers to your questions.
Earn a certificate when you pass your final project.
Need help? Get support between sessions.
Don’t miss a thing. All cohort sessions are recorded.
A comprehensive education in technical skills for content designers
Understand the fundamentals of engineering environments and how products are built. Get the practice app running, find where content lives, and make your first fork.
Learn to read a repo like a map. Understand the fork model, work safely in branches, explore the AI instruction architecture, and start building your content system.
Understand how AI actually reads your context, write instruction files that work, learn the full PR workflow, and feed your content system to a real AI tool.
Share what you built, understand how your work moves through the CI/CD pipeline, and get a clear picture of where AI and content design are heading.
“Our product team made a content update using the ideas from the Fundamentals of UX Writing course. We’ve since seen a 20% increase in conversions.”

Group Content Strategist, Course Hero
“We wanted a fundamental training that provided a calibration for some basic understanding on how we do our daily work.”

Senior UX Writing Lead, HSBC
No. This cohort is designed for content designers who are new to technical environments. You don’t need coding experience, just a willingness to learn and work hands-on.
No. You won’t be writing code. The focus is on understanding how engineering environments work and how to contribute within them as a content designer.
You’ll work with tools like GitHub and VS Code, along with common workflows such as pull requests, branches, and code review. The skills you’ll learn can be applied on any team using industry-common tools.
Yes. You’ll practice in a real repository created for the cohort, designed to reflect how teams actually work.
AI is used throughout as a practical tool. You’ll learn how to use it to navigate unfamiliar code, understand repositories, and support real workflows.
Have questions? We’re here to help.
We can combine self-paced courses, workshops, or create custom sessions for your team based on unique needs. Get in touch – we’d love to speak with you.

Customer Success Manager
WEEKLY NEWSLETTERS
Stay on top of the industry. Get our weekly Dash newsletter with useful links, the jobs newsletter, news, discounts, events, and more.
"I got my job after seeing the newsletter, and I'm pretty sure I wouldn't have seen the posting otherwise."