The best engineers share what they learn.
InfoQ provides the platform, support, and global audience.
Report on emerging software trends weekly.
Or write articles about what you learned in production.
Daniel Bryant
InfoQ News Manager, Author, Java Champion, and Head of Product Marketing @Syntasso
Srini Penchikala
InfoQ AI/ML/DE Lead Editor, and
Senior Software Architect
Two ways to contribute
Both help senior engineers, architects, technical leads, and their
teams adopt
new technologies and practices.
Report on innovations.
InfoQ Editors write weekly news about emerging patterns, new use cases, and essential product updates in software development.
Apply to be an Editor
Share your own lessons.
InfoQ Authors write deep-dive articles about
real-world production challenges they've solved.
Stay curious. Write weekly.
InfoQ Editor
Cover what's new in your technical area. Interview maintainers and architects. Report on emerging patterns, insights from conference talks, and significant product updates.
Editors receive a quarterly revenue share plus the opportunity to apply to cover QCon conferences that give you direct access to the people shaping your technical domain.
What you get:
Quarterly revenue share for your contributions
Options to apply for QCon conference passes
Journalism training and editorial support
Press credentials to reach engineers who'd otherwise ignore cold outreach
Joining InfoQ has been an amazing learning experience: the onboarding program is excellent, and it helped me understand how to write news. Writing regularly helps me stay up to date with new frameworks and understand the challenges companies face at scale.
Leela Kumili
InfoQ Architecture and Design Editor, and Lead Engineer @Starbucks
Sharpen your writing with 1:1 training, connect with peers, and stay on the cutting edge.
Thomas Betts
InfoQ Architecture & Design Lead Editor, Senior Laureate Software Engineer & Architect @Blackbaud
Share what you learned.
InfoQ Author
Write about an architecture decision that surprised you. A migration that taught you something. An incident that changed how your team works.
Your article is reviewed by an experienced engineer and published to 1.5 million senior developers. One article. Years of compounding visibility.
What you get:
Your work in front of 1.5M monthly readers across 5 languages
Editorial support from an engineer-editor who'll make your article better
Full copyright ownership: your article, your portfolio
A credential that compounds: shows up in searches and AI overviews, gets shared in Slack channels, and opens doors you didn't know existed
InfoQ's peer-review system elevates your article and boosts your credibility.
Roland Meertens
InfoQ AI/ML/DE Editor, Host of Generally AI - InfoQ Podcast, and ML Engineer @Wayve
Transitioning from my personal blog to InfoQ was a career-defining choice. The incredible editorial support sharpened my storytelling skills as the platform gave my work a global stage. Writing for InfoQ has been instrumental in teaching me to communicate with influence and approachability, both of which are essential for growing as an engineering leader.
Mourjo Sen
InfoQ Author and Staff Software Engineer @Booking.com
Why senior engineers write for InfoQ
How InfoQ can help you advance your career
InfoQ Editors
Access you can't get otherwise.
"I'm writing about your project for InfoQ." opens doors that cold outreach never will. Interview maintainers, architects, and engineering leaders shaping your domain.
It makes you better at your job.
Covering emerging patterns weekly keeps you sharp. Editors consistently say the role accelerated their own technical growth.
InfoQ Authors
You've already done the hard part.
You solved the production problem. You made the architectural bet. Writing is just packaging what you already know. InfoQ handles editing, distribution, and translation into 5 languages .
Your work compounds.
A single article keeps working for years. It surfaces in searches. Gets shared in Slack channels. Shows up in AI overviews.
Joining the InfoQ editorial team allowed me to interact with world-class peers and interview industry legends. Also, it encouraged me to step out of my comfort zone by exploring different areas and technologies to ensure my coverage is relevant.
Olimpiu Pop
InfoQ Java Editor, co-host of the InfoQ podcast, and CTO @Remote Tech
Access a large audience, join an inclusive community, and grow your personal brand.
Daniel Bryant
InfoQ News Manager, Author, Java Champion, and Head of Product Marketing @Syntasso
Editors and Authors.
How it works
Both help senior engineers, architects, technical leads, and their
teams adopt
new technologies and practices.
Editors
Apply in 10 minutes.
Tell us about your background. We review within 5 working
days.
If it's a match, we'll reach out to book a call.
Brief call to check fit.
30 minutes. We answer your questions. Decision within 48 hours.
Authors
Proposal
Submit an article proposal. We review within 5 - 7 working
days.
Our editors check fit and ask for a draft or decline.
Draft, review, publication
Accepted drafts move to technical review and publication.
The InfoQ team is incredibly supportive and provides fantastic resources to help you get up and running as an editor. If you enjoy sharing knowledge, I highly recommend contributing to InfoQ.
Nsikan Essien
InfoQ Cloud Editor, and Head of Platform Engineering & Cybersecurity @Field
InfoQ supports you from your first draft to joining QCon as a dedicated reporter.
Roland Meertens
InfoQ AI/ML/DE Editor, Host of Generally AI - InfoQ Podcast, and ML Engineer @Wayve
Steef-Jan Wiggers
InfoQ Cloud Lead Editor and Domain Architect @Coöperatie VGZ
From practitioners like you
Get inspired and start sharing knowledge on InfoQ
I started writing for the InfoQ .NET queue to keep up to date with technology, and I got so much more! I met knowledgeable people, I improved my writing skills, and I got global visibility.
Edin Kapić
InfoQ .NET Editor, and Lead Software Engineer @Vista
Writing for InfoQ has opened many doors for me. I was able to interview experts and thought leaders to learn more about the topics I covered. I can share my learnings with the tech community and understand how the technologies are used in the real world.
Vivian Hu
InfoQ WebDev Editor, and Director of Products @Second State
Writing for InfoQ gives me the opportunity to contribute to a community that helps architects, developers, and tech leads every day with quality content. Writing for InfoQ is improving my technical writing and helping me keep up with industry news. It is a super stimulating experience with a lot of visibility, allowing me to combine my work as a Solution Architect with my passion for technology.
Matteo Rossi
InfoQ Author, Senior Solution Architect @Assicurazioni Generali
I've always been focused on emerging tech releases and industry movements, and being an InfoQ editor gives me the ability to share my findings with the community. It's pushing me to keep researching and stay current. The team are welcoming, knowledgeable, and helpful, creating a genuinely collaborative environment. It's a pleasure working with everyone, and I'm excited to continue sharing content with the InfoQ readers.
Dan Curtis
InfoQ WebDev Editor, and UI Development Manager @Griffiths Waite
InfoQ's peer-review system has significantly improved my writing. If you're searching for a place to share your software expertise, start contributing to InfoQ.
Oghenevwede Emeni
InfoQ Author, and Software Developer @Bawse
Writing for InfoQ has helped me stay consistently up to date with trends in software engineering and applied AI. Through the news mentorship, I improved how I analyze technical developments and turn them into clear, practitioner-focused insights. It's especially rewarding to share emerging technologies and engineering trends with the InfoQ community.
Robert Krzaczyński
InfoQ Editor, Senior Software Engineer & AI Specialist
Becoming an editor for InfoQ was one of the best decisions of my career. It has challenged me and helped me grow in so many ways. We'd love to have more people join our team.
Thomas Betts
InfoQ Software Architecture & Design Lead Editor, and Senior Laureate Software Engineer & Architect @Blackbaud
Frequently Asked Questions
Is this paid?
InfoQ Editors: Yes. Editors receive a quarterly revenue share for their contributions, plus they can apply to cover QCon as a dedicated reporter to get a QCon conference pass worth $3,000+.
InfoQ Authors: No. The value is editorial support, distribution to 1.5M readers, and a byline that builds your professional reputation. You retain full copyright.
Do I need writing experience?
No. Most contributors are engineers, not writers. Editors get journalism training. Authors work with an engineer-editor who reviews for technical accuracy and clarity.
What can I write about?
InfoQ Editors: Emerging trends, new use cases shared by senior practitioners, essential product updates, insights from conference talks in AI/ML, DevOps, Cloud, Architecture, or Java.
InfoQ Authors: Production problems you solved, technical decisions you made, migrations you ran, incidents you handled, key learnings to help a global community of software developers. The Innovator and Early Adopter topics in the InfoQ Trends Reports drive our editorial strategy.
Can I use AI tools?
For research and grammar, yes. For writing your content, no. We reject primarily AI-generated work. Read our full AI policy.
Who owns the copyright?
InfoQ Authors retain full copyright and grant InfoQ distribution rights. InfoQ Editors create news as part of the editorial team. Read our full copyright policy.
Can I do both?
Yes. Some contributors switch between roles over time.
Join us.
Ready to write?
Report on what's new weekly.
Share real-world learnings.
Questions? contribute@infoq.com