A Show HN post succeeds when it is specific, honest, and technically interesting. The Hacker News community is primarily engineers and technical founders who read dozens of Show HN posts per week and have a highly calibrated sense for which products are genuinely useful versus which are just noise. The posts that reach the front page consistently have three characteristics: they explain exactly what the product does and why the author built it, they acknowledge trade-offs and limitations honestly, and the author is present and willing to discuss technical details in the comments. Posts that fail almost always fail for the same reasons: marketing language, vague value propositions, or an author who disappears after posting.
I have posted to Hacker News multiple times for Zlyqor and related projects. Here is the complete guide.
What HN Readers Respond To
Technical specificity. HN readers are engineers. If your product does something technically interesting, explain it. "We built a task scheduler that uses a modified version of the deadline-monotonic algorithm to prioritize time-sensitive work items" is more interesting to HN than "we built a smart task manager."
Honest trade-offs. The HN community respects founders who acknowledge what their product does not do well. "This works great for teams under 20 people. Above that, the real-time sync architecture starts showing latency issues we are still working on" is the kind of honesty that HN readers respect and will upvote.
Real numbers. Any time you can provide actual performance data, usage numbers, or concrete results, include them. "We reduced our API response time from 800ms to 120ms by switching from N+1 queries to a single aggregation pipeline" is more credible than "we optimized our backend."
The builder's perspective. HN readers like to know why you built the thing. Not the marketing version of "why" (a problem statement designed to make the product sound essential) but the actual reason. "I built this because I was doing manual time tracking in a spreadsheet and kept forgetting to log hours until Friday afternoon" is more compelling than "teams waste 20% of their time on administrative tasks."
Technical depth in the comments. Some of the most successful Show HN posts gain traction not from the post itself but from the author's responses in comments. When someone asks a hard technical question and you give a thorough, honest answer, other readers upvote both the question and the answer, which drives the post higher.
What Kills Posts
Marketing language. Words like "powerful," "intuitive," "seamless," and "game-changing" are processed by HN readers as noise. The moment your post sounds like a press release, readers move on.
Vague value propositions. "A better way to manage your projects" tells a HN reader nothing. What specific problem does it solve? For whom? How does it solve it differently from the 50 other project management tools?
Asking for feedback but not wanting it. HN readers will critique your product, your technical decisions, and your business model. If you post "looking for feedback" but then respond defensively to every critical comment, the post will get downvoted.
Poor timing. HN traffic peaks on weekday mornings US time. Posts submitted at 2 PM PST on a Friday get buried quickly. The best time to post is 7-9 AM PST on Tuesday, Wednesday, or Thursday.
Over-formatting. Long markdown-heavy posts with headers and bullet points are unusual on HN and sometimes read as corporate. HN posts are traditionally plain prose. A well-written three-paragraph post often performs better than an exhaustively structured five-section post.
No author presence. HN rewards discussion. If you post and do not engage with comments in the first few hours, the post will not trend. Plan to be available for 3-4 hours after posting to respond to every comment.
