Answer a few journalistic questions. Get published on HackerNoon.
Tell us what you do or what just happened. We'll match you with one of 273 interviews written by HackerNoon editors. Answer on your own time, by voice or by typing.
- AnswerAbout 13 questions, by voice or text, whenever you want
- DraftYour answers land in a Chowa draft with your byline
- EditA HackerNoon editor reviews it to the Editing Protocol
- DistributePublished on HackerNoon and syndicated across the web
Curated Technology Interview Templates
Each is a set of about 13 questions written by HackerNoon editors. Pick one and answer at your own pace.
Interviews worth reading
Published interviews from across HackerNoon, from Google and OpenAI to Startups of the Year nominees. Each links to the interview you'd answer to write one like it.
Reads are HackerNoon pageviews as of October 2026.
### 01 WHY INTERVIEWS
“Interviews are expertise that wouldn't exist without an interviewer and an interviewee. By documenting your expertise, you're contributing to the internet's accessible knowledge base and growing your reputation, your stake in that expertise. And now you can get published just by talking to your phone. That's pretty cool.”
The next person who searches for the problem you solved finds your answer, with your name on it.
journalistic.tech supplies the person asking. HackerNoon editors wrote 273 interviews of about 13 questions each, for job titles, company news, milestones, career moves and the events you attend. You answer on your own time, by voice or by typing.
Get interviewed
Questions written by HackerNoon editors for your role or your news. No pitching a reporter.
Share your insight
Answer by voice or text into a Chowa draft. The questions draw out the decisions and lessons other builders want to read.
Get featured
Edited to the Editing Protocol and published on HackerNoon under your byline.
Grow your reputation
Distributed across the web, so people and search engines find it when they look you up. Browse the example library.
### 02 HOW IT WORKS
Journalistic questions, on your schedule.
- ### STEP ONE
Tell us what's going on
Your job title, something you shipped, a milestone, a career move, or the conference you're at. We match it to the right interview.
- ### STEP TWO
Answer about 13 questions
One at a time, by voice or by typing. Skip what doesn't fit and come back later.
- ### STEP THREE
Review your draft
Your answers become a draft in Chowa, HackerNoon's editor. Tighten anything before you submit.
- ### STEP FOUR
An editor reviews it
A HackerNoon editor checks it against the Editing Protocol. Nothing is published without that approval.
- ### STEP FIVE
It's published and distributed
Your interview goes live on HackerNoon and is distributed across the web.
| A press interview | journalistic.tech | |
|---|---|---|
| Timing | On the reporter's schedule | Async, whenever you have 20 minutes |
| Questions | Chosen for the reporter's angle | Written and vetted in advance by HackerNoon editors |
| Your words | Quoted in someone else's story | Published in full, under your byline |
| Review | The outlet's call | Edited to a public standard, the Editing Protocol |
### 03 WHO HAS ANSWERED
Googlers, Amazonians, Metamates, Microsofties, and thousands of builders.
People at these companies have been interviewed on HackerNoon, from Google's Head of Data Commons to first-time founders. Each name links to the interview.
### 04 WHEN
Whenever you have 20 minutes, and whenever something happens.
It's async, so there's no call to schedule. Start answering on your phone from a conference floor and finish at your desk. The best time is right after something happens, while the details are fresh:
### 05 WHERE
Drafted in Chowa. Published on HackerNoon. Read across the web.
Your answers become a draft in Chowa, HackerNoon's editor. After a HackerNoon editor approves it to the Editing Protocol, it's published on HackerNoon under your byline and distributed across the web.
journalistic.tech is run by HackerNoon. Using it is covered by our Terms of Use and Privacy Policy, together with HackerNoon's Terms and Privacy Policy. Voice input uses your browser's built-in speech recognition, which in some browsers sends audio to the browser maker for transcription. Read counts are HackerNoon pageviews as of October 2026. Icons are from HackerNoon's Pixel Icon Library, licensed under CC BY 4.0; the microphone icon was drawn to match.
Terms of Use
Effective November 4, 2026
journalistic.tech (the "Site") is operated by ArtMap, Inc., doing business as HackerNoon ("HackerNoon", "we", "us"). By using the Site you agree to these Terms of Use and to HackerNoon's Terms of Service and Privacy Policy, which are part of these terms. If these terms and HackerNoon's Terms of Service conflict, HackerNoon's Terms of Service control. If you don't agree, please don't use the Site.
1. What the Site does
The Site helps you find an interview question set written by HackerNoon editors and links you to HackerNoon to answer it. Answering, drafting, editing and publishing all happen on hackernoon.com and are governed by HackerNoon's Terms of Service and editorial standards, including the Editing Protocol.
2. No guarantee of publication
Submitting answers does not guarantee publication. HackerNoon editors decide, at their sole discretion, whether, when and in what edited form a story is published, and may decline or remove any story.
3. Your content and your responsibilities
You keep ownership of what you write. Content you submit to HackerNoon is licensed to HackerNoon as described in its Terms of Service. You are responsible for your answers. Please make sure they are truthful, that you have the right to share them, and that they don't disclose confidential information, trade secrets or personal data belonging to your employer, clients or anyone else. Don't impersonate another person or misrepresent your role or affiliation.
4. Acceptable use
Don't use the Site to break the law, infringe anyone's rights, send spam, or interfere with the Site's operation or security, including by excessive automated requests or attempts to gain unauthorized access.
5. Site content
Interview questions, text, design and code on the Site belong to HackerNoon or its licensors. Example interviews link to stories published on HackerNoon by their authors. Read counts are HackerNoon pageviews at the date stated on the Site and may be out of date. Icons are from HackerNoon's Pixel Icon Library under CC BY 4.0.
6. Third-party services and links
The Site links to and relies on services we don't control, such as your browser's speech recognition and hosted web fonts. Your use of those services is governed by their own terms, and we aren't responsible for them.
7. Disclaimers
The Site is provided "as is" and "as available", without warranties of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose and non-infringement. We don't promise the Site will be uninterrupted, error-free or that its suggestions will suit you.
8. Limitation of liability
To the fullest extent permitted by law, HackerNoon and its officers, employees and contributors won't be liable for any indirect, incidental, special, consequential or punitive damages, or for lost profits, data or goodwill, arising from your use of the Site. HackerNoon's total liability for any claim relating to the Site is limited to one hundred US dollars (US$100).
9. Indemnity
You agree to indemnify and hold HackerNoon harmless from claims arising out of content you submit or your violation of these terms.
10. Changes and termination
We may change or discontinue the Site, or update these terms, at any time. The effective date above shows when they last changed. Continuing to use the Site after a change means you accept the updated terms.
11. Governing law and disputes
Governing law and dispute resolution are as set out in HackerNoon's Terms of Service.
12. Contact
Questions? Reach HackerNoon through the HackerNoon Help Center.
Privacy Policy
Effective November 4, 2026
This policy covers journalistic.tech (the "Site"), operated by ArtMap, Inc., doing business as HackerNoon. It adds to HackerNoon's Privacy Policy, which applies to everything you do on hackernoon.com, including answering an interview, creating an account and publishing.
1. What you type on the Site
The Site matches you to an interview in your browser. The text you type into the Site's chat box is not sent to HackerNoon's servers or stored by us. The Site has no accounts and does not ask for your name or email.
2. Voice input
If you use the microphone, the Site uses your browser's built-in speech recognition. Depending on your browser, your audio may be sent to the browser maker (for example Google or Apple) for transcription, under that company's privacy policy. HackerNoon does not receive or store your audio.
3. Cookies and storage
The Site does not set advertising or tracking cookies.
4. Information collected automatically
Like any website, the Site's hosting and security providers (such as Vercel and Cloudflare) process technical information when you visit, including your IP address, browser type, the pages you request and timestamps, to deliver the Site, keep it secure and measure aggregate traffic. Fonts are loaded from Google Fonts, which receives your IP address when your browser requests them.
5. When you go to HackerNoon
Buttons such as "Get interviewed" and "Write from scratch" take you to hackernoon.com. From there, anything you submit, including your answers, drafts and account details, is handled under HackerNoon's Privacy Policy.
6. How we use information
We use the limited technical information above to operate, secure and improve the Site. We don't sell personal information.
7. Children
The Site is not directed to children under 13 and we do not knowingly collect information from them.
8. Your choices and rights
You can use the Site without the microphone and without an account. To exercise privacy rights available to you under applicable law, follow the process in HackerNoon's Privacy Policy or contact us through the HackerNoon Help Center.
9. Changes
We may update this policy. The effective date above shows when it last changed.