Writing a Guest Post

UI Engineering Excellence is the #1 source for practical systems thinking in frontend. The publication cover topics relevant for those interested in every layer of UI from subatomic design tokens to distributed micro-frontend architectures.

I (Rob) am always looking for guest writers to cover interesting topics, coming from their hard-earned experience and expertise.

What we publish

  • Helpful resources, short and surgical: guides, patterns, workflows, prompts, sub-agents, code mockups.

  • Research-based and definitive, high-signal deep dives that shift thinking and help readers stay current.

The profile of the "typical" reader:

  • ~80% of readers are experienced UI Engineers or Designers

  • ~70% of readers work in either a product or foundations team

Take a look at past guest posts to get a sense of what published guest posts look like in depth and content.

Why you should apply

  1. It’s a win for our readers.
    They get to learn from your experience. Nobody knows exactly what you know.

  2. It’s a win for you, the writer.
    We have a budget to pay you for your work. And the exposure you get ain’t bad.

  3. It’s a win for UI Engineering Excellence.
    The more valuable content we publish, the more often people drop by to visit.

Examples of folks who have been great fits for guest writers include:

  • In the process of writing a book. Engineers in the process of writing a book on a topic.

  • Starting to write more regularly. People starting to write more regularly on topics they know well.

  • Sharing years of experience on a topic. People wanting to share significant experience they gathered with a broader group.

... this is not an extensive list. If your experience and expertise could be interesting for Senior+ UI Engineers/Designers to read about, send us a pitch!

Compensation

We pay contributors for accepted, published work unless explicitly requested. Rates vary by depth and scope. Revenue sharing is available for posts with paid add-ons (worksheets, diagrams, extended examples). We’ll confirm terms on acceptance.

Topics we’re interested in

Here are some things we’d love to share your expertise on:

  • Enterprise UI engineering that doesn’t go stale: architecture, governance, multi-branding and themeability at scale.

  • UI composition for graceful developer experience.

  • Workflows for AI pair-engineering: code mockups, guardrails, review prompts.

  • Accessibility as architecture: system-level a11y, not bolt-ons.

  • Page performance when the browser fights back: concurrency, streaming, partial hydration.

  • Migration playbooks: design-system rewrites with zero downtime.

  • Testable UI patterns: state charts, contracts, and DOM-level invariants.

Write the article you wish you found when you googled something.

What we’ll pass on

Beginner intros, generic “how to React,” listicles without proof, SEO bait, and posts that read like ads. If it wouldn’t help a Staff Engineer/Designer this week, it’s not a fit.

Originality, AI, and disclosures

  • Original ideas only. If adapted, state what’s new and what’s reused.

  • AI assistance is fine. Disclose tools and include prompts that materially shaped code or diagrams. You remain responsible for accuracy and licenses.

  • Disclose conflicts of interest, affiliations, or vendor relationships.

Rights and distribution

  • You retain copyright. We require first publication and a canonical link.

  • You may republish after 30 days with a “Originally published at UI Engineering Excellence” link back.

  • Code samples default to MIT unless you specify otherwise.

Editorial process

  1. Pitch review for fit and scope.

  2. Outline tighten to lock objectives and examples.

  3. Draft + tech edit for correctness and clarity.

  4. Line edit for voice and density.

  5. Publish to free or paid tiers, with optional add-ons.

Typical turnaround from accepted pitch to publish is 2–4 weeks depending on scope.

Submission checklist

☑️ Clear thesis and target reader.
☑️ Trade-offs named, not implied.
☑️ Runnable code and one meaningful example.
☑️ Diagram(s) where they beat prose.
☑️ Links to proofs: PRs, RFCs, benchmarks, or standards.
☑️ Alt text, captions, and captions that earn their keep.
☑️ Disclosure and AI note, if applicable.


Apply as a Guest Author