Hire a technical content writer
Technical content written by an engineer who actually shipped the thing
I'm a software architect with 15+ years in production systems, writing freelance technical content for DevTool and SaaS teams — bylined, first-hand, and built to rank and get cited by AI. In a market drowning in generated copy, that practitioner credibility is the part you can't fake.
What I write
For your engineering blog, developer marketing site, docs, or publication — original, experience-backed, and written from first principles, not recycled from what's already ranking.
- Software Architecture
- Technical Leadership
- Developer Productivity
- Career & Life Design
- Quality & Craft
Technical deep-dives & tutorials
Long-form articles that walk through a concept, pattern, or technology end-to-end — with real examples, trade-offs, and the decisions behind them. No filler.
Technology comparisons
Side-by-side evaluations of frameworks, tools, or architectural approaches — written from production experience, not spec sheets. I name winners, losers, and the context where each belongs.
Architectural decision records
Narratives around real design decisions: what the problem was, what options were on the table, what was chosen, and what it cost. The kind of reasoning that rarely gets written down.
Case studies
Concrete stories from building and scaling systems — migration paths, scaling crises, org redesigns, and the engineering lessons that came out the other side.
Opinion & perspective pieces
Contrarian or forward-looking takes on engineering culture, tooling trends, AI adoption, and how teams actually work. Grounded in 15+ years of practice, not hype cycles.
Leadership & career articles
For developer-facing publications: what staff+ engineering looks like, how to move into leadership without losing craft, and the gaps no engineering manager course covers.
Writing samples
Published, full-length pieces on this site — the same depth and voice you'd get on yours. Read one end-to-end before you brief me.
Hundreds more across every category in the full archive.
Why hire a practitioner, not a content mill
Real E-E-A-T
A named engineer's byline and first-hand experience — the signals Google now rewards and generated content can't manufacture.
Built to be cited by AI
Structured, extractable, answer-first writing designed to surface in ChatGPT, Perplexity, and Google AI answers — not just rank.
No hand-holding
I understand your product and the technical subject matter, so you brief once and get a draft that needs editing, not a rewrite.
How we can work together
Three ways to start. Pricing depends on scope, length, and cadence — email me with what you need and I'll send a quote.
Single article
One bylined, long-form technical piece — start here or use it as a paid trial.
- Topic research and outline for sign-off
- 1,500–3,000 words, original and experience-backed
- SEO + AEO structure (built to rank and be cited)
- Diagrams or code where they earn their place
- Two revision rounds
Content retainer
A steady stream of articles each month for teams with an ongoing calendar.
- 2–6 articles per month, your mix of formats
- Lighter briefs once we're in rhythm
- Topic and angle suggestions from your gaps
- Priority turnaround and a predictable cadence
- Quarterly review of what's landing
Product review or evaluation
Hands-on, honest write-up of your tool, SDK, book, or platform from a real workload.
- I use the product against a realistic scenario
- Honest assessment — strengths, trade-offs, fit
- Developer-credible, not a press release
- Optional comparison against alternatives
- Requires access to the tool or material
How it works
Send a brief
Topic or angle, audience, where it'll publish, target length, deadline, and budget range. Bylined to me or ghostwritten — your call.
Fit check & quote
I reply within a day on whether it's a genuine fit and send a scoped quote. If it's not my wheelhouse, I'll say so.
Outline for sign-off
You approve the angle and structure before I write a word — no surprises, no wasted drafts.
Draft & revise
An edit-ready draft, then two revision rounds. Honest, accurate, and built to rank and get cited.
Honest content that won't backfire
Everything I write reflects an honest technical assessment — which is exactly what earns developer trust and survives scrutiny. I name trade-offs and won't produce anything that reads like a press release. That credibility is what makes the content convert; the one thing I can't do is write to a predetermined conclusion. Read the editorial policy.
Brief me on your project
Send the topic, audience, length, and budget. I'll tell you within a day whether it's a fit. Prefer LinkedIn? That works too.
Looking for free engineering mentorship instead? See the mentorship page.