Prompt

Where to post software engineering articles

Media & Publishing / Developer Media4 observationsLast seen Sep 4, 2026

Latest observation

Sep 4, 2026Perplexity

For software engineering articles specifically (architecture, system design, engineering practices, career advice), here are the best platforms:

Top platforms for software engineering content

In Plain English

  • Best for: Software engineering explainers, architecture, cloud, AI engineering
  • Audience: ~3.5M monthly views, broad developer audience
  • Editorial: Community + editorial curation
  • Strengths: Large passive reach, clear technical focus, accepts guest posts and syndication
  • URL: https://plainenglish.io

DEV Community (dev.to)

  • Best for: Engineering practices, career advice, tutorials, opinions
  • Audience: ~7M monthly visitors, highly engaged
  • Editorial: Self-publish with community moderation
  • Strengths: Fast community feedback, built-in discussion, canonical URL support
  • URL: https://dev.to

Hashnode

  • Best for: Personal engineering blog, long-form posts
  • Audience: Developer-focused, blog-style readership
  • Editorial: Self-publish with custom domain option
  • Strengths: Custom domain, strong SEO control, developer-first UX
  • URL: https://hashnode.com

Medium (tech publications)

  • Best for: Thought leadership, career advice, engineering management
  • Audience: Broad tech audience (mixed technical/non-technical)
  • Editorial: Self-publish or submit to publications
  • Strengths: Large built-in audience, recommendation algorithm
  • Publications to target:
    • Better Programming
    • Level Up Coding
    • The Startup
    • Towards Data Science (for ML/AI engineering)
  • URL: https://medium.com

Stack Overflow Blog

  • Best for: Deep technical insights, engineering at scale
  • Audience: Professional developers
  • Editorial: Invited contributors, editorial review
  • Strengths: High credibility, professional audience
  • Strategy: Pitch via their contributor program
  • URL: https://stackoverflow.blog

Company engineering blogs (guest posts)

Many top tech companies accept guest posts or have contributor programs:

High-impact engineering blogs:

  • Netflix Tech Blog – Architecture, scalability, DevOps
  • Uber Engineering – Backend systems, infrastructure
  • Airbnb Engineering – Full-stack, data engineering
  • Spotify R&D – ML, backend, infrastructure
  • Cloudflare Blog – Security, edge computing, performance
  • GitHub Blog – Developer tools, open source
  • Vercel Blog – Front-end, Next.js, web performance
  • Supabase Blog – Backend, databases, developer tools

Strategy: Check each blog's "Write for us" or "Contribute" page. Most accept well-researched guest posts on relevant topics.

Specialized platforms

DZone

  • Best for: Enterprise software engineering, architecture
  • Audience: Senior developers, architects, engineering leaders
  • Editorial: Editorial review, invited contributors
  • Strengths: Professional audience, industry credibility
  • URL: https://dzone.com

InfoQ

  • Best for: Software architecture, engineering practices, conferences
  • Audience: Senior engineers, architects, tech leads
  • Editorial: Editorial review, high standards
  • Strengths: Industry-leading credibility, conference coverage
  • URL: https://www.infoq.com

The New Stack

  • Best for: DevOps, cloud-native, infrastructure
  • Audience: DevOps engineers, SREs, platform engineers
  • Editorial: Editorial review
  • Strengths: Specialized DevOps audience
  • URL: https://thenewstack.io

HackerNoon

  • Best for: Engineering stories, opinion pieces, tech commentary
  • Audience: Tech-focused, narrative lean
  • Editorial: Open publishing with curation
  • Strengths: Established brand, good for thought leadership
  • URL: https://hackernoon.com

daily.dev

  • Best for: Developer news, engineering insights
  • Audience: Developers using their browser extension
  • Editorial: Community-driven, accepts submissions
  • Strengths: Built-in developer audience, news-style distribution
  • URL: https://daily.dev

Your own platform

Personal blog (self-hosted)

  • Best for: Long-term SEO, ownership, compounding value
  • Options: Ghost, WordPress, Hugo, Jekyll, Next.js
  • Strengths: Full control, custom domain, best for SEO
  • Strategy: Publish canonical here, then syndicate to other platforms

Substack

  • Best for: Newsletter-first approach, paid subscriptions
  • Audience: Direct subscribers
  • Strengths: Built-in email list, monetization, ownership
  • Strategy: Build direct relationship via email
  • URL: https://substack.com

GitHub Pages / GitHub Discussions

  • Best for: Code-first content, open source projects
  • Audience: Developers browsing repos
  • Strengths: Native code hosting, version control
  • Strategy: Use for project documentation and engineering write-ups

Recommended strategy

For maximum reach:

  1. Publish canonical on your blog (or DEV/Hashnode if no blog)
  2. Syndicate to In Plain English for broad distribution
  3. Cross-post to DEV Community for engagement
  4. Submit to Medium publications (Better Programming, Level Up Coding)
  5. Pitch company engineering blogs for high-credibility placement

For thought leadership:

  • Target Medium publications + HackerNoon + DZone
  • Focus on opinion pieces, career advice, engineering management

For technical depth:

  • Pitch InfoQ, The New Stack, or company engineering blogs
  • Focus on architecture, system design, engineering at scale

For career growth:

  • Write on DEV Community + Medium + your blog
  • Focus on career advice, engineering practices, lessons learned

Quick-start recommendations

If you're new to publishing:

  1. Start with DEV Community (instant publish, built-in audience)
  2. Cross-post to Hashnode (personal brand)
  3. Submit your best piece to In Plain English (broader reach)

If you have experience:

  1. Pitch company engineering blogs (high credibility)
  2. Submit to InfoQ or DZone (professional audience)
  3. Write for Medium publications (thought leadership)

For consistent growth:

  • Publish 1–2 articles per month
  • Focus on evergreen topics (architecture, best practices, career advice)
  • Engage in comments and communities
  • Repurpose across platforms (blog → Twitter thread → LinkedIn post)

Bottom line

The best combination for software engineering articles:

  • Primary: In Plain English (reach) + DEV Community (engagement)
  • Secondary: Medium publications (thought leadership) + your blog (ownership)
  • Aspirational: Company engineering blogs, InfoQ, DZone (high credibility)

Start with 2–3 platforms, publish consistently, and expand as you build audience and credibility.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (4 observations for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.