Sponsored by
THE CODE
Inside the Reviewer's Inbox: How to Beat the Slush Pile
Here's a secret the conference circuit doesn't advertise: most talks aren't rejected because the speaker wasn't good enough. They're rejected because the pitch gave a tired reviewer an easy reason to move on.
Picture the scene. It's 11pm. A volunteer reviewer — probably with a day job, definitely with cold coffee — is on submission number 312 of 600. They are not savoring your prose. They are speed-scanning for clarity and skimming for "do I believe this person can deliver?" Your job is not to impress them with how much you know. Your job is to make their decision easy. Let's do that.
Pick an angle, not a topic.
"Kubernetes." "Burnout." "Accessibility." Those are topics, and topics are where talks go to blend in. An angle is a topic with a point of view and a scar. "The three Kubernetes mistakes that paged me at 3am (so they never page you)." "How we cut onboarding from six weeks to six days." See the difference? One is a Wikipedia page. The other is a story only you can tell. Reviewers reject the generic because they've seen it eleven times this round. Specificity is how you stop being submission number 312 and start being the one about the 3am pages.
The title is 80% of the job.
Most people write the title last, in a rush, and it shows. Flip it. Your title is the headline that gets your abstract read at all. Aim for specific + a hint of payoff + a flicker of intrigue. "Improving Database Performance" → snooze. "We Made Our Database 10x Faster By Deleting Code" → now I'm leaning in. Avoid cleverness that hides the subject (the pun that needs a footnote), and avoid the kitchen-sink title that promises everything and therefore nothing.
The abstract: four moves, three short paragraphs.
Reviewers want to see a shape, not a wall of text. Use this skeleton:
The hook + the problem. Open with the tension. "Every team says they want fewer meetings. Then they schedule a meeting about it." Land the ache your talk relieves.
What they'll actually learn. Be concrete. Not "attendees will gain insights into productivity" (insights — the word that means nothing) but "you'll leave with a 3-step framework for killing recurring meetings without killing your reputation."
Who it's for. "Ideal for ICs and team leads who've ever side-eyed a calendar invite." This tells the reviewer it fits an audience, and it tells that audience to show up.
Keep it tight. If the conference gives a word limit, treat it like a budget, not a target.
Takeaways: make a promise you can keep.
Lots of CFPs ask for "key takeaways" or "learning objectives." This is where vague pitches die. List two or three things an attendee can do on Monday morning. "Understand the importance of testing" is not a takeaway; it's a fortune cookie. "Write your first contract test in under ten lines" — that's a takeaway. Concrete promises signal that you've actually thought through the talk, which is the single biggest thing reviewers are sniffing for.
The bio: relevance beats résumé.
Your bio is not your LinkedIn dumped into a box. The reviewer is asking one quiet question: can this person credibly deliver this specific talk? So lead with the part of your story that earns the stage. Giving a talk on scaling? "I kept a payments system alive through three Black Fridays" does more work than your job title and your two unrelated certifications. One sharp sentence of relevance, one of personality, done.
The mistakes that get an instant no.
Too broad. "The Future of AI" is not a talk, it's a magazine cover.
Secretly a sales pitch. Reviewers can smell a product demo wearing a talk costume from across the room.
No clear takeaway. If they can't tell what the audience leaves with, they leave it out.
Ignoring the conference. Read the theme, skim last year's accepted talks, match the tracks. A pitch that clearly gets the event beats a stronger pitch that clearly didn't read the brief.
Here's the reframe to carry into the inbox: you're not begging for a slot. You're handing a stressed-out reviewer a gift — a clear, specific, deliverable talk that makes their lineup better and their job easier. Write it like that, and you stop fighting the slush pile. You float above it.
THE RUN
🎬 Your Week: From "Someday" to "Submitted"
Gif by nickelodeon on Giphy
This is the week the talk leaves your head and enters an inbox. Five moves, one per day-ish. No perfectionism allowed.
1. Find two open CFPs (15 minutes). Search "[your topic] conference call for proposals 2026" or browse a CFP aggregator. Pick two that are open and that you'd actually want to attend. Bookmark the deadlines. Future-you will thank present-you.
2. Mine your own scars for the angle (20 minutes). Open a blank note and finish this sentence three times: "The thing I learned the hard way about ___ was ___." One of those is your talk. The hard-won lesson is always more interesting than the polished overview.
3. Draft a title and abstract (30 minutes). Use the four-move skeleton from The Code: hook + problem, what they'll learn, who it's for. Write it badly first. Bad drafts are editable; blank pages are not.
4. Get one set of eyes on it (10 minutes to send). Send your draft to one peer or mentor with a specific ask: "Does the title make you want to read on, and is the takeaway clear?" Specific questions get useful answers.
5. Hit submit before Friday's over. This is the whole point. Not "polish for two more weeks." Submit. Then — and this matters — message one other woman in your network and send her the CFP link too. The lineup changes faster when we bring each other along.
Bonus credit: reply to this email and tell me what you submitted. I want to cheer.
You don't need permission to take the mic. You need a deadline and a send button. You've got both now. 🎤
THE WRAP
✋Before you go:
🌞 Keep Shining,
Barkha
What’s next is almost here.
On July 16th at 1PM EST, beehiiv is going live with a look at the future of publishing, audience growth, and digital business.
What started as a newsletter platform has evolved into something much bigger: a place where creators and brands can grow, monetize, and own their audiences without stitching together half the internet to make it work.
The next chapter starts live at the Summer Release Event.
Join us to see what’s coming next.
