Becoming truly proficient in software development requires continuous learning at a deeper level—not just knowing how to use tools, but also understanding when and why to apply them, the design decisions behind a technology, and the concepts it is built upon.
We at inDepth firmly believe that writing technical articles is one of the most powerful ways to master a subject. Crafting a thorough, in-depth piece pushes you through discovery and research that fills gaps and adds structure to your mental model of a topic.
The payoff extends far beyond learning, though. Deep research and public writing can boost your visibility in the community and significantly impact your career. Your peers—including potential employers, clients, or publishers—will read your work. The knowledge you share can help hundreds of thousands of developers around the world become better engineers. And the process itself teaches you how to communicate ideas, write clearly, and promote your work through social media.
Investing your time in gaining valuable knowledge and sharing it openly is one of the most rewarding paths to professional development. We invite you to join our community of writers—submit an article or pitch one if you have an idea.
To be upfront: writing for inDepth is not a casual endeavor. Our mission is to provide developers with insights that are hard to find elsewhere—content that solves real technical problems and helps them grow. Your work should teach something non-trivial, something readers can apply in their daily work. We will push you to make your article the best it can be.
Why choose inDepth?
There are many platforms out there—Medium, DEVto, or your own blog—so why publish with us? Here are a few compelling reasons.
1. A supportive writer community
Writing is tough. Writing articles that people genuinely want to read and share is even tougher. We aim to make the process more enjoyable and less lonely. Over the years, inDepth has built a community of writers who are ready to help. Stuck on a topic? Ask for help. Unsure how to structure your piece or what to cut? Get guidance and constructive feedback from fellow writers.
2. A highly technical readership
Our readers are mostly senior engineers and technical leads with years of front-end experience. They know the web platform well and are fluent in major frameworks. This is the perfect audience for deep technical content. They come to inDepth to solve challenging problems or to deepen their understanding of specific topics. They are the ones most likely to appreciate the effort you put into a long, detailed article.
3. Rich analytics
Unless you run your own blog with Google Analytics, you rarely see real data on how your posts perform. Most platforms show only views or reads, often without clear definitions. We give you much more. Beyond view counts, you get traffic sources, unique visitors, social media engagement numbers, and geographic data on your readers.
4. A dedicated designer
Social media is a powerful way to drive traffic, but it is crowded. Visuals help you stand out—posts with images get about ten times more engagement. But generic stock photos are not enough. To capture attention, you need a relevant image, ideally with a technology logo integrated into it. That's where our in-house designer steps in. No need to search for visuals or edit images yourself. We handle it for you.
5. Trusted by search engines
inDepth has been publishing for over three years, building credibility with Google. While our domain authority may not yet rival giants like Medium or DEV, it is still significant. This credibility influences search rankings. A post on inDepth is typically indexed within 24 hours and often ranks high on the first page of search results.
How to submit
Fill out this form and we'll get back to you. If your article is already written, send the draft and we’ll review it. We prefer Google Docs so editors can leave feedback and guidance directly in the text.
If you’re still at the idea stage, send a one-paragraph abstract and a brief outline of the points you intend to cover. These shouldn’t be polished—just enough detail for us to evaluate the idea.
Once your proposal is accepted, we’ll invite you to our internal Slack community, where our writers will help review your piece and give iterative feedback to get it ready for publication.