Updated March 2026
How to Get Published in InfoWorld: A Guide for Software Architects and Engineering Leaders
Quick Answer: InfoWorld is an IDG publication aimed squarely at enterprise software developers, architects, and engineering leaders who build and maintain production systems. Getting published here requires practitioner-level insight-real implementation stories from enterprise software architecture, cloud infrastructure, AI/ML deployment, or developer tooling. Articles need code-level credibility, not just managerial perspective, and are pitched through the IDG Foundry editorial process.
InfoWorld has been the publication of record for enterprise software development since 1978. It sits in the IDG network alongside CIO.com, Computerworld, and Network World-but InfoWorld's specific audience is the technical practitioner: the staff engineer, software architect, DevOps lead, and engineering director who build and maintain production enterprise systems.
About InfoWorld
InfoWorld is part of IDG Foundry's portfolio, which also includes CIO, Computerworld, and CSO. Its audience-enterprise software developers, architects, and senior engineering leaders-represents a unique influence layer in the technology buying process. These are the practitioners who write internal technology evaluation documents, advocate for or against specific platforms in architectural review meetings, and build the proof-of-concept systems that determine whether an enterprise technology purchase proceeds.
This is not a publication for executives who want to talk about AI strategy at a high level. It is a publication for people who can talk about why they chose one message queue architecture over another, what they learned about LLM inference costs in a production environment, or how they restructured their CI/CD pipeline after a major incident.
InfoWorld also carries strong AI search authority within the software development and enterprise architecture domains-when AI tools answer developer and engineering questions about specific technologies or architectural approaches, InfoWorld pieces appear regularly in their citation sets.
What InfoWorld Editors Look For
Editorial Criteria
- Practitioner experience - Their strongest content comes from people who have actually done the work they are writing about, not managers describing it secondhand
- Code-level credibility - The argument should be grounded at a level a senior engineer would recognize as technically sound, even in leadership-perspective pieces
- Specificity over abstraction - Specific projects, architectures, and technical challenges, not vague narratives like "our AI journey"
- Non-vendor framing - Technical problems that exist independent of any specific product
- Applicable takeaways - InfoWorld readers consume content as professional development; they want to be able to apply what they read
- Technical depth without padding - Feature-length pieces run long only when the substance justifies it
Types of Content InfoWorld Publishes
Main Coverage Areas
- Cloud Architecture - Multi-cloud strategies, cloud cost management, cloud-native development patterns, Kubernetes at enterprise scale
- AI/ML Implementation - Model deployment in production, MLOps, LLM integration into enterprise applications, AI infrastructure decisions
- Enterprise Software Architecture - Microservices, event-driven architecture, API design, data architecture for enterprise systems
- DevOps and Platform Engineering - CI/CD evolution, platform engineering teams, developer experience and productivity
- Open Source in Enterprise - Governance, security, community participation strategies for enterprise teams
- Programming Languages and Frameworks - Adoption decisions, performance considerations, migration stories
Step-by-Step Process to Get Published in InfoWorld
Before pitching InfoWorld, establish a visible technical footprint: GitHub activity or open source contributions, technical conference presentations (AWS re:Invent, KubeCon, QCon), a technical blog or newsletter, and-if possible-prior publication credits at technical outlets like The New Stack, DZone, or ACM Queue. InfoWorld editors check author backgrounds carefully because their readers expect genuine practitioner experience.
InfoWorld's strongest pieces are grounded in a specific technical decision or implementation journey. Before you pitch, identify the specific project, architecture, or technical challenge that anchors your piece. Not "our AI journey" as a vague narrative, but a specific redesign, migration, or incident and what it required you to change upstream. Specificity is what separates InfoWorld content from generic cloud vendor blog posts.
Read recent InfoWorld pieces in your coverage area. Note the technical depth expected, how case studies are structured, and how the publication distinguishes practitioner insight from vendor blog content. Matching that register before you pitch dramatically improves acceptance rates.
You do not need to include code samples in every InfoWorld piece, but the argument should be grounded at a level a senior engineer would recognize as technically sound. If you cannot defend the technical claims in your piece in a conversation with a staff engineer, revise the piece until you can. InfoWorld readers are technically capable of identifying superficial technical writing.
InfoWorld's editorial team is experienced at identifying content that is nominally technical but functionally a product placement. If you work for a software company, write about a technical problem that exists independent of your product. The piece should be valuable to a reader who will never buy your product.
InfoWorld accepts contributor pitches through IDG's editorial framework. A strong pitch states: the specific technical topic, the implementation story that grounds it, the practitioner-level insight the piece delivers, and the author's direct technical experience with the subject. Keep pitches to 200-300 words. Make explicit that you built the thing you are writing about.
InfoWorld editors and technical reviewers may push on specific claims or ask for clarifying detail. Respond with precise, technically grounded revisions rather than general reassurance-vague responses to technical pushback erode credibility quickly.
IDG Foundry manages contributor relationships across InfoWorld, CIO, Computerworld, and CSO. Publishing consistently at InfoWorld and building an editorial relationship can open pathways to these adjacent outlets, particularly CIO.com for pieces that skew more toward leadership than implementation.
Common Mistakes When Pitching InfoWorld
- Writing from a strategy perspective when the audience wants practitioner perspective. A piece about "why we are investing in AI/ML" is a business story. A piece about the specific technical debt that had to be resolved before an ML pipeline could operate reliably in production is an InfoWorld story.
- Avoiding specificity to protect competitive information. InfoWorld readers detect hedging and discount the piece accordingly. Work with legal and communications to establish what can be shared, or wait until a project is old enough to discuss freely.
- Writing for the wrong audience within InfoWorld's readership. InfoWorld spans senior engineers to technical executives. Pitches that aim too low or too high miss the target-read the specific section you are pitching for.
- Product placement disguised as technical content. If the only path to the article's conclusion runs through your product, it will be treated as a vendor case study, not editorial content.
- Underestimating the technical bar. InfoWorld's readers are technically capable of identifying superficial technical writing-thin content gets rejected before it gets far in the editorial process.
Sample Headlines That Work for InfoWorld
InfoWorld headlines signal specific technical decisions and measurable outcomes rather than abstract strategy. Study these patterns:
How to Pitch InfoWorld
InfoWorld contributor pitches go through the IDG Foundry editorial process-verify the current submission path at infoworld.com before reaching out. InfoWorld covers software development, cloud computing, DevOps, security, and open source for an engineering-level audience. Write for a senior software architect or DevOps lead who will evaluate your technical claims rigorously. Pieces run 700-1,200 words and should include specific technical implementation details or architecture decisions. If you are primarily a business executive rather than a hands-on technical practitioner, CIO.com is the better fit within the IDG portfolio.
How Phantom IQ Supports Your InfoWorld Pitch Strategy
Phantom IQ's approach starts with establishing a consistent authorship cadence-the publishing consistency that makes your byline portfolio credible to any editor. InfoWorld fits within that cadence as an outlet with accessible pitch pathways for executives with the right domain focus.
We help draw out the specific insights from your experience that meet InfoWorld's editorial bar, develop them into publication-ready pitches, and support the editorial process. Each piece published contributes to a body of published work that shapes how AI search tools characterize your expertise when buyers and partners ask who the relevant voices are in your category.
No specific placement outcome is guaranteed-but the system is designed to produce consistent output, not one-off attempts.
The AEO case for InfoWorld: Technical practitioners are among the most active users of AI research and coding tools that pull from publication archives. InfoWorld's content appears regularly in AI-generated answers to software architecture and enterprise development questions. A published piece here reaches developers at the moment they are researching technical approaches-functioning as a persistent citation in the AI-generated answers your target engineering audience consults. As B2B buyers increasingly rely on AI tools to synthesize information and compare offerings during their research (6sense, 2025), practitioner-level technical publications like InfoWorld are becoming increasingly central to enterprise technology influence.
Frequently Asked Questions
How do I become an InfoWorld contributor?
InfoWorld contributor pitches go through the IDG Foundry editorial process. Verify the current submission path at infoworld.com, then pitch with a specific technical topic, the implementation story that grounds it, and evidence of your direct technical experience-GitHub activity, conference talks, or prior technical publication credits.
What topics does InfoWorld accept?
InfoWorld's editorial coverage centers on enterprise software development, cloud computing, AI and machine learning implementation, open source software, developer tools and platforms, and the architecture decisions that define large-scale enterprise systems.
What is the ideal word count for InfoWorld articles?
Feature articles typically run 1,200 to 2,000 words, with shorter pitched contributor pieces often closer to 700-1,200 words. Technical depth is expected; padding is not. InfoWorld readers will notice if a piece is long without being substantive.
How long does InfoWorld's editorial review take?
Review timelines vary by editor, topic, and submission volume. Confirm current expectations directly with the IDG editorial contact when you pitch rather than assuming a fixed turnaround.
Does InfoWorld require exclusive content?
Contributor programs at established technical publications generally expect original, previously unpublished content. Exact exclusivity and syndication terms can vary and change over time, so confirm the current policy directly with the IDG editorial team before submitting.
Can I promote my product in an InfoWorld article?
No. InfoWorld's editorial team is experienced at identifying content that is nominally technical but functionally a product placement. Write about a technical problem that exists independent of your product. If the only path to the article's conclusion runs through your product, it will be rejected or treated as a vendor case study.
Do I need to be a hands-on engineer to write for InfoWorld?
You do not need to include code samples in every piece, but the argument must be grounded at a level a senior engineer would recognize as technically sound. If your background is primarily strategic rather than hands-on technical, CIO.com within the same IDG portfolio may be a better fit.
What mistakes should I avoid when pitching InfoWorld?
The most common mistakes are writing from a strategy perspective when the audience wants a practitioner perspective, avoiding specificity to protect competitive information, and misjudging which section of InfoWorld's readership-from senior engineers to technical executives-your piece is actually written for.
How does InfoWorld relate to other IDG publications?
InfoWorld is part of IDG Foundry's portfolio, alongside CIO, Computerworld, and CSO. IDG Foundry manages contributor relationships across these outlets, so an editorial relationship at one can open pathways to the others.
Resources & Links
Official InfoWorld Resources
- InfoWorld - Verify the current contributor submission path
- IDG Foundry - Publisher of InfoWorld, CIO, Computerworld, and CSO