Hi dotCMS — I’m Matías.
This mini-site is my application for the Developer Relations Engineer role at dotCMS — a static Astro site with mostly no client-side JavaScript, built in a public repo with the commit history, planning docs, and architecture decisions included. That’s how I like to work: in the open, showing the process, not just the result.
About me
I’m a hands-on DevRel engineer. I research features, issues, and tools; I build working demos; I write the docs and tutorials that explain them; and I get in front of developers — on camera, in live workshops, in short- and long-form video, and in writing.
Behind that is two decades of technical background as a developer, sysadmin, infrastructure engineer, and trainer, and more than ten years producing technical content in native-level English and Spanish.
I’ve run daily live-coding streams to a hundred concurrent viewers, taught DevOps and programming live workshops with 300+ sign-ups, and sustained a cadence of three short videos a week plus a long-form deep dive every month. I love building community with technical and non-technical audiences.
About you
dotCMS sits in an interesting space for me. For many developers, the first real interaction with a platform like this is through the API, SDKs, documentation, and starter examples, so the developer experience matters a lot.
A good developer experience has to serve different levels of intent. Newcomers need a clear path from “I’m curious” to “I have content rendering from a real repository” without having to understand the whole platform first. Senior developers need something different: accurate mental models, predictable APIs, sharp reference docs, and enough depth to evaluate tradeoffs, extend the system, and trust it in production.
That’s the kind of surface I’ve spent a lot of time working around. I’ve built, tested, and documented integrations across different CMSs — including Contentful, Sanity, Strapi, Directus, Payload, Ghost, and WordPress — and the pattern is usually the same: the hard part is rarely just calling an API. It’s understanding the content model, the rendering path, the auth flow, the edge cases, and what the developer needs to know right now versus what can wait.
I’ve been on both sides of that moment: the developer trying to make the pieces fit, and the person writing the guide, example, or explanation that helps the next developer build a clearer mental model and move a little faster.
How I work
I think in systems and like to build in the open. I document what I’m doing, capture decisions as I go, and leave useful artifacts behind for future me and my team. The goal is simple: improve continuously, preserve context, and turn the work itself into documentation the whole team can build on. Agentic workflows and LLMs help me do that faster and more deliberately.
I enjoy doing deep dives into codebases, but I also like looking for signals in less obvious places: support tickets, recurring questions, internal Slack threads, sales calls, and conversations with the engineering team. Some of the most useful content doesn’t come from a keyword list or a roadmap item; it comes from noticing where users are confused, where developers keep explaining the same thing, or where the product has capabilities that people don’t yet know how to use.
I test everything in every piece of content I ship or supervise: every environment, every command, every config.
I care about one metric above all: how fast a developer gets from “this looks interesting” to “I grok it and I’m using it effectively.”
I want to do that with you
You need someone who can own developer-facing content end to end. At DonWeb Cloud I spearheaded the developer content program: tutorials, guides, video, and demos across VPS, Linux, Docker, CI/CD, DNS/SSL, and CMS platforms, reporting directly to and working with product and marketing leadership.
- Demos and docs that actually run. Every environment, command, and config tested before it ships.
- Comfortable in front of developers. Two years of daily unscripted live-coding, twice-monthly workshops, and a steady video cadence.
- Bilingual by default. Native-level technical English and Spanish, both directions.
- Current on AI developer workflows. Claude Code, MCP servers, RAG pipelines, evals, agent-friendly documentation — the way developers will meet dotCMS next.
I’d love to show you what that looks like applied to dotCMS. Have a look at my resumé, or just hit reply on the email that brought you here.