HackerNoon is an open publishing platform, and anyone can create an account and submit a story, but that does not mean every story gets published. Every submission goes through an editorial review, and around 60% of articles are rejected, which means writers are competing not only for attention, but also for limited editorial time.
That makes one question especially important: **are you making your editor's job easier or harder?
\ Writers naturally focus on ideas, headlines, arguments, and prose, and all of those things matter, but editors also remember how a writer behaves throughout the publishing process. We remember the people who submit clean drafts, communicate clearly, respond well to feedback, and consistently reduce friction. These habits may seem less important than writing talent, but in practice, they can determine whether an article moves forward.
Submit a Draft, Not a Cleanup Project
A clean draft does not have to be perfect, since editors expect to edit, but there is a major difference between editing a story and rebuilding one. A publishable draft should already have a clear point, a logical structure, useful headings, credible sources, and enough context for the reader to understand why the subject matters, and it should not contain broken links, unfinished sections, placeholder text, repeated paragraphs, unsupported claims, or an introduction that takes ten minutes to reach the point.
Before submitting, read the article as though you were seeing it for the first time, and ask whether the headline accurately describes the story, whether the introduction establishes the subject quickly, whether each section adds something new, whether factual claims are supported, and whether the conclusion actually concludes the article. Editors notice when a writer has handled these basics, and we also notice when a writer has apparently pasted a first draft into the editor and expected the publication team to finish it.
A useful question to ask before submitting is whether you are giving the editor a finished story or a problem to solve.
Clear Communication Builds Confidence
Editorial communication does not need to be formal or complicated, but it does need to be clear. When an editor asks a question, answer it directly, and when you are asked to revise a section, confirm that you understand the request; if you need more time, say so instead of disappearing, because silence creates uncertainty. Editors begin wondering whether the writer has abandoned the story, misunderstood the feedback, or plans to return weeks later with an unrelated draft, and clear communication removes that uncertainty.
It is also perfectly acceptable to disagree with an editorial suggestion, since editors are not automatically correct, and writers often have technical or professional knowledge that the editor does not. The important part is how the disagreement is handled: explain what the section is doing, why the information matters, and how removing it may affect the story, while keeping the discussion focused on the article rather than turning it into a personal conflict. Editors remember writers who communicate like collaborators.
Revisions Are Not Rejection
Some writers treat every revision request as evidence that an editor disliked the article, but usually the opposite is true. When an editor asks you to improve the opening, add evidence, clarify an argument, remove promotional language, or reorganize a section, they are continuing to invest time in the story, which is often a positive signal — the article has not been rejected, it has been given a path toward publication.
How you handle that opportunity matters. Strong writers review every comment, make the necessary changes, and return a visibly improved draft, asking questions when feedback is unclear and explaining when they have addressed an issue differently, while less reliable writers fix one or two comments, ignore the rest, and resubmit the article with the same underlying problems. That creates additional review cycles and tells the editor that every future assignment may require the same level of effort.
Professional revision is not about agreeing with everything; it is about showing that you can participate seriously in the editorial process.
Do Not Make Editors Investigate Your Story
Editors should not have to perform detective work before they can evaluate a submission, so be transparent about who you are, what you know, and why you are writing about the subject. If you work for a company mentioned in the article, disclose it; if you are promoting your own product, say so; and if your argument is based on personal experience rather than independent research, make that clear.
Check every source before submitting, make sure links support the claims attached to them, and do not cite a homepage when a specific report or document is available. Avoid presenting estimates as facts, opinions as consensus, or marketing claims as independent analysis, because the easier it is for an editor to verify the article, the easier it becomes to publish.
Reliability Compounds
One clean submission will not instantly make you a trusted writer, but a pattern will. Editors remember writers who repeatedly submit thoughtful articles, follow the publishing guidelines, respond to feedback, and improve their work without creating unnecessary drama, and over time, the editor stops wondering whether the writer will handle revisions properly, stops expecting a difficult back-and-forth, and opens the next submission with more confidence.
Trust does not guarantee publication, since every story still needs to meet HackerNoon's standards, but trust reduces uncertainty, and when editors are reviewing a large queue in which most submissions will not be published, reducing uncertainty matters.
Make the Process Easy to Say Yes To
The strongest writers do more than write well; they make the entire process easier. They submit complete drafts, respect the reader's time, support their claims, communicate clearly, and handle revisions without treating every edit as an attack.
A great idea can get an editor's attention, and a clean draft can get a story published, but reliability is what makes editors remember your name the next time you submit.
Have a story you can’t wait to share right away? Take a stab at this writing template here!
Want to take this further? (HackerNoon’s Blogging Course)
HackerNoon’s Blogging Course is designed for beginners and writers who’ve published a bit and want to level up. It’s organized into 8 modules created by experienced writers and editors, and it includes topics like:
How to Find Your “Voice” and Ideal Writing Workflow SEO + Storytelling: Write Content That Ranks and Resonates How to Write Great Articles That People Will Read
Sign up for the
That’s it for today.
Until next time, Hackers!