This is our jam: app development and management at scale, and all the software and services that support this task. We want to know how everything works, from a sysadmin or dev angle.
Contributors have always been a vital component to The New Stack. Since the site’s inception in 2014, we have had an open door policy for those who wanted to share their own views in a contributed post about what is happening in their corner of the tech community — be they a Fortune 500 company or a single hacker feverishly working on the weekends.
If you want to submit something, you can hit us up here. Please allow two to three weeks for us to evaluate the proposal or post.
But if you want to make it more certain your contribution will appear on our site and be widely read, read on.
People like TNS because it analyzes and explains technology, with a voice that is positive, forward-thinking and cuts through the nonsense. We don’t talk down to the reader; we know our readers are intelligent.
Contributed stories are, at heart, an exercise in mutual exploitation. We want stories that offer our readers a little something for their time. Busy people, they are. They’re CTOs, project managers, developers, administrators and other technically-inclined IT pros who do not appreciate having their time frittered away on artfully-disguised marketing copy.
To clarify, we are NOT interested in generic “unbiased” thought-leadership posts, crafted by your marketing department. There are other outlets for those pieces. We expect you to biased about your own work — why wouldn’t you be? — as long as what you write is accurate as well.
We’re also not interested in AI-generated posts. We don’t publish them, and we don’t like to read them. So don’t bother sending us those, please.
Story Ideas
We get it. Sometimes it’s hard to come up with story ideas beyond product announcements and promotions. But IT people tend not to read these articles – they want insights from other technologists. This is first and foremost our goal at The New Stack: to help readers do their jobs and make smart decisions. Finding where that aligns with your expertise will help position you to readers as a trusted resource.
These articles might help you write articles that appeal to The New Stack’s audience:
Writing for Software Engineers: Read Me First
Writing for Software Engineers: Beyond the Basics
Here’s a checklist to help you identify with fresh ideas and on-staff expertise that will resonate with The New Stack readers.
- Talk with your developer relationship advocates and IT project leaders. The best way to find out what readers want to learn is to talk with your IT team, particularly developer advocates who hear firsthand from your users about their concerns and what they need from you to do their jobs well. IT project leaders are also another great resource – what problems are they solving that would help readers? Even if it’s not directly related to your offering, posts such as these help readers identify your company as experts they can turn to.
- If you are a TNS sponsor, bring your developer relationship advocates to the sponsor meetings with The New Stack. This allows them to be part of the process and assist in the brainstorming of new topics.