How to Get Published in InfoWorld: A Guide for Software Architects and Engineering Leaders

By Tom Popomaronis • Updated March 2026

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.

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. If that describes your experience, InfoWorld is one of the most valuable publications in your target media portfolio—because its readers are the technical evaluators who influence enterprise software purchasing decisions from the bottom up.

Why InfoWorld Matters for Engineering and Software Leaders

InfoWorld's 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 the internal technology evaluation documents, who advocate for or against specific platforms in architectural review meetings, and who build the proof-of-concept systems that determine whether an enterprise technology purchase proceeds. Reaching them with credible peer-level insight is a category of influence that executive-oriented business publications simply cannot provide.

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, frameworks, or architectural approaches, InfoWorld pieces appear regularly in their citation sets. Given that technical practitioners are increasingly using AI coding assistants and research tools that pull from this publication, a well-written InfoWorld piece can reach developers at the exact moment they are evaluating a technical approach.

For CTOs, VPs of Engineering, and principal engineers at enterprise software companies, an InfoWorld byline signals something specific: that you can communicate at the practitioner level, not just at the strategy level. This creates credibility with technical audiences that typical business publication bylines do not.

What InfoWorld Looks For

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. Their strongest content has one consistent characteristic: it comes from practitioners who have actually done the work they are writing about.

Coverage areas with consistent editorial interest:

• 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

The format that works best: Practitioner case studies and implementation analysis—pieces where the author shares what they actually did, what they actually learned, and what they would do differently. InfoWorld readers consume this content as professional development, not entertainment. They want to be able to apply what they read.

Word count: Feature articles typically run 1,200–2,000 words. Technical depth is expected; padding is not. InfoWorld readers will notice if a piece is long without being substantive.

Step-by-Step Approach to Getting Published in InfoWorld

Step 1: Identify the specific implementation story you can tell

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 "how we redesigned our real-time data pipeline to reduce inference latency from 340ms to 45ms using X approach, and what that required us to change upstream." Specificity is what separates InfoWorld content from generic cloud vendor blog posts.

Step 2: Ensure code-level credibility even in leadership-perspective pieces

You do not need to include code samples in every InfoWorld piece, but the argument should be grounded at a level that 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.

Step 3: Pitch InfoWorld editors with a clear practitioner angle

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 that the piece delivers, and the author's direct technical experience with the subject. Keep pitches to 200–300 words. InfoWorld editors are looking for evidence that you have built the thing you are writing about—make that evidence explicit in the pitch.

Step 4: Build your technical credibility profile

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.

Step 5: Avoid the vendor framing trap

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. If the only path to the article's conclusion runs through your product, it is a vendor case study, not an InfoWorld piece.

Common Mistakes Executives Make Pitching InfoWorld

Writing from a strategy perspective when the audience wants practitioner perspective. A VP of Engineering piece about "why we are investing in AI/ML" is a business story. A VP of Engineering piece about "the specific technical debt we had to resolve before our ML pipeline could operate reliably in production" is an InfoWorld story. The distinction is whether the reader learns something they can apply technically.

Avoiding specificity to protect competitive information. Many executives want to write about their technical work but are reluctant to share specific details for competitive reasons. InfoWorld readers detect this hedging and discount the piece accordingly. If you cannot share the specific implementation details, either work with your legal and communications teams 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 a range from senior engineers to technical executives. Pitches that aim too low (writing for developers when the author's experience is at the architecture level) or too high (writing for boards when the audience is engineering teams) miss the target. Read the specific section you are pitching for—the voice and level of each section within InfoWorld differs.

How Phantom IQ Helps With InfoWorld Placement

InfoWorld requires the rarest combination in executive thought leadership: deep technical credibility and editorial craft in the specific voice that practitioner audiences respond to. Most executives either have the technical depth but write in a corporate style that does not land with developers, or they have strong editorial skills but lack the specific operational detail that InfoWorld's editors require.

Phantom IQ's extraction process is designed to pull the specific technical implementation stories out of executives' experience and shape them into the practitioner-facing format that InfoWorld editors accept. We work with engineering leaders to identify the specific technical decisions and outcomes that anchor publishable pieces, structure the argument at the right technical level, and route through IDG editorial relationships. First placements typically happen within 60–90 days of program start.