building and leading software products
Record 001 Developer Relations Engineer
I make complex developer products easier to understand—and harder to ignore.
I’m Alex Noel. I bring a decade of software engineering to developer education, ecosystem partnerships, technical content, and product feedback.

enabled across the developer ecosystem
of users served by products shipped
Evidence archive
Selected case files
Developer relations is most convincing when the work can be inspected. These records span ecosystem building, product scale, and technical leadership.
Ecosystem enablement
Making integrations useful—not merely available.
Developer relations work connecting Plasmic with the tools developers already use, backed by documentation, education, and direct community feedback.
Engineering leadership
Scaling a product—and the team responsible for it.
Four years leading engineering through product growth, performance work, technical modernization, and team development.
Education platform
Building for millions of students and their teachers.
Technical leadership on a large education platform with SSO, reporting, assessment workflows, and PDF generation.
High-load commerce
A product catalog built for serious volume.
A React and Python B2B platform for a premium ceramics manufacturer, designed around a large catalog and sustained daily traffic.
Operating method
Engineering depth. DevRel range.
The work moves between code, content, community, partners, and product teams—without losing the thread between them.
Explain
Documentation, tutorials, demos, and technical narratives that give developers a durable mental model.
Connect
Partner integrations that join product strategy, implementation, education, and adoption.
Listen
Public community support that turns repeated friction into product and engineering feedback.
Build
Hands-on React, Node.js, Python, data, cloud, and technical leadership experience.
Latest transmissions
Field notes
Short essays on developer experience, documentation, technical ecosystems, and the patterns hiding inside public support.
Documentation is a product surface.
Good documentation is not a description of the product after the fact. It is one of the places where the product becomes understandable.
Integrations are relationships before they are code.
The API connection may be the artifact, but shared understanding is what makes an ecosystem integration durable.
Public support is product intelligence.
A resolved question helps one developer. A recognized pattern can improve the product for everyone who follows.
Signal received
Have a complicated product and a developer audience?
Let’s make the path between them clearer.
Open a channel ↗