Kent C. Dodds Portfolio
Full-time Educator
The homepage spells out "blog → / courses / podcasts" as one literal visual block, backed by a 17-course catalog that now includes an AI-specific title alongside long-standing bestsellers — a content-and-course business built on top of real engineering credibility.
Location
Location: classified. Send a pigeon.
Companies
Credentials
- Master of Science in Information Systems, Brigham Young University (BYU), 2014
Skills
Notable
- Google Developer Expert (GDE)
- Microsoft MVP
- Represented PayPal on the TC-39 committee that standardizes JavaScript
What makes it work
A breakdown of the choices that make this portfolio stand out.
Blog, courses, and podcasts presented as one literal unit
The homepage has a section that spells out the three-legged pitch visually — "blog →", "courses", "podcasts" stacked together as a single block, not three separate mentions buried in different pages. The site structure itself makes the "building + teaching + community" argument before any copy does.
A growing, explicitly current course catalog
The flagship grid leads with Epic Product Engineer and includes Epic AI ("build AI-powered applications") alongside long-standing titles like Epic React and Testing JavaScript. Adding an AI-specific course rather than resting on older bestsellers signals the catalog is actively maintained, not a set-and-forget product line from years ago.
Personal photography reused as a trust signal, not just a headshot
The same warm, approachable photo of Kent appears both in the "Get to know Kent C. Dodds" video thumbnail and again inside the Discord community card. Repeating a real photo, rather than a single sterile headshot, makes the "join the community" ask feel like meeting a person, not signing up for a funnel.
Career evolution stated as the value proposition, not hidden
The hero copy leads with "Helping people make the world a better place through quality software" — a mission statement, not a job title. It frames him by scope rather than by a single technology, matching a decade-plus pivot from IC engineer to full-time educator.
What Frontend Developers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
If you offer content in more than one format (writing, courses, audio), show them together as one visual unit on your homepage instead of splitting them into separate nav items a visitor has to discover.
Keep at least one offering visibly current (a recent date, a trending topic) so the whole catalog doesn't read as abandoned.
Reuse a real, warm photo of yourself across different sections rather than one stiff headshot — familiarity builds trust faster than polish.
Lead your homepage with a mission sentence, not a job title, once your work has evolved past a single narrow role.
Combine building, teaching, and community into a package — each leg makes the others more credible and harder for a competitor to replicate.
Projects
EpicReact's exercises are checked by tests, Testing Library set how much of the industry writes them, and even the personal site is open source with an end-to-end suite. Kent C. Dodds's course catalog and engineering portfolio are the same argument, made three ways.
Epic React Workshops
Self-paced, code-first React training: 7 workshops, 240 bite-sized lessons and 243 interactive exercises, all React 19 and 100% TypeScript, from JSX basics through performance and React Server Components. Exercises run in the learner's own local environment through the Epic Workshop app. One click sets up a fresh playground for your IDE, progress is tracked across sessions, and work is checked instantly with solution diffs and built-in tests.
The workshop tooling is the impressive part: a local app that scaffolds each exercise, runs tests against it, and diffs it against the solution. Building that means owning developer experience end to end — the gap between a staff-level frontend engineer and someone who writes tutorials.
Exercises run locally in the learner's own editor — the workshop app sets up each exercise and verifies it with built-in tests and solution diffs
7 workshops / 243 interactive exercises, rewritten for React 19 and fully TypeScript
Simulated team context (a project manager and a coworker persona set specs) makes exercises closer to real work than isolated katas
A family of user-centric testing utilities, led by React Testing Library, that query the DOM the way users find elements (by role, label and text) instead of by implementation details. Kent is the listed author of react-testing-library's npm package.
Setting a testing standard that other major tools adopt is open-source leadership at ecosystem scale. It shows API design judgment ('test the way users use it') that changed how a large part of the industry writes tests.
Query-by-role/label/text API adopted by Playwright and Vitest, per his resume
GitNation OS Awards: Most Impactful Contribution to the community
State of JS 2020: highest satisfaction (97%)
kentcdodds.com (Open Source)
Kent's personal site, with its full source public on GitHub. It runs on React Router v7 and Cloudflare Workers with D1, KV and R2, and SQL migrations are kept as flat files. External APIs are mocked by default in local dev, and one setup script installs dependencies, resets the local D1 database, and runs end-to-end tests. The site hosts his blog, courses, talks, Call Kent podcast and a reader 'teams' feature.
A personal site built like a production app — typed, tested end to end, mock-first in development, and deployed to the edge — shows the same full-stack standards he teaches, applied to his own code in public.
Open source, 2.5k stars — anyone can read how a real content-and-commerce site is built
Vitest + Playwright test suite; the setup script runs end-to-end tests on first install
Live read counts on the homepage (964k+ reads) instead of static claims
More Frontend Developer portfolios
Ready to build your portfolio?
Follow the Frontend Developer roadmap — skills, projects, and timeline to get hired.