Presenting at a Conference for the First Time — A Chemistry Postgraduate's Guide
Your first conference is the first time your chemistry leaves your notebook and meets people who did not supervise it. That is uncomfortable, and it is also the point. A poster or a short talk is how a postgraduate becomes visible to the small number of people working on the same problem — which is how collaborations, PhD offers and later job interviews actually begin.
This guide covers what to submit, how to build a poster and a short talk, how to answer questions without panicking, and the specific mistakes first-timers make. It quotes no registration fees, no travel-grant amounts and no deadlines, because every conference states its own — read the announcement of the specific conference you are applying to.
What a presentation actually has to do
First-timers almost always try to present everything they have done since joining the lab. That is the single biggest cause of a confusing poster. A visitor gives you two to five minutes; a session chair gives you a fixed number of minutes and then stops you. Pick one question, show the evidence for it, and let the rest of your work live in the conversation afterwards.
The formats, and which one to choose
| Format | Typical shape | Best for | Main risk |
|---|---|---|---|
| Poster | You stand beside a printed board during a session and talk to people one at a time | A first presentation; work still in progress | Too much text, so nobody stops |
| Short oral / contributed talk | A fixed slot, often around ten to fifteen minutes including questions | A result complete enough to defend | Overrunning, so the chair cuts your conclusion |
| Flash or lightning talk | Very few minutes, sometimes one or two slides, often advertising a poster | Pulling an audience to your poster | Trying to fit a full talk into it |
| Invited talk | Longer slot, by invitation | Not a first-timer format | — |
If you have a choice, take the poster for your first conference. Standing beside your own work and explaining it fifteen times in an afternoon teaches you more about how to describe your project than any amount of rehearsing a talk alone in a room.
The abstract — where most rejections happen
The abstract is usually the only thing the committee sees. Chemistry abstracts are normally short, often carry a strict character or word limit, and are read quickly by someone who is not in your sub-field.
A structure that reliably works, in four or five sentences:
- Context — one sentence on the problem, in language a general chemist understands.
- The gap — one sentence on what is not yet settled or not yet possible.
- What you did — the system studied and the method used, concretely.
- What you found — an actual result, not a promise. "Results will be discussed" is the phrase most likely to get an abstract downgraded or rejected.
- Why it matters — one sentence, without overclaiming.
Check the submission page for the things that get abstracts returned unread: the required file format, whether structures or schemes are permitted at all, the character limit, and whether the presenting author must be registered before submitting.
Building a poster that people stop at
A poster is read from about a metre away, by someone walking past who decides in two seconds whether to stop. Design for that reader.
A layout that works — three columns, read top-left to bottom-right.
Title band: the title as a short statement of the finding, not a vague topic. "Ligand X accelerates the coupling at room temperature" stops more people than "Studies on ligand systems". Authors and affiliation underneath, in smaller type.
Column 1: a two-to-three sentence introduction, then your question or aim in one line, boxed. Nothing else.
Column 2: the method as a scheme or a short flow of steps, then your main data — the one plot, spectrum or table that carries the result, made large.
Column 3: a supporting result, then conclusions as three bullet points, then a short "next steps" line, acknowledgements and your contact.
Rules of thumb: keep body text large enough to read standing back; aim for well under a thousand words on the whole board; use white space deliberately; keep to two or three colours; and make sure every axis has a label and a unit. An unlabelled axis is the fastest way to lose a specialist's confidence.
Prepare three versions of your explanation before the session: a thirty-second version for someone from a different field, a two-minute version for a chemist who is interested, and a five-minute version with mechanism and controls for a specialist. Ask each visitor what they work on first, then pick the version. This one habit separates confident presenters from nervous ones.
Building a short talk
A working plan for a twelve-minute slot with three minutes of questions.
Minute 1 — the problem. One slide. Why anyone should care, in ordinary language.
Minute 2 — the specific question. One slide, stated as a sentence. Everything after this exists to answer it.
Minutes 3–4 — the approach. One or two slides. What you made or measured, and how, at the level of detail a chemist outside your group needs.
Minutes 5–9 — the results. Three or four slides, one message per slide. Say the message out loud before you explain the data: "the reaction is first order in catalyst — here is the plot that shows it".
Minute 10 — limitations. One slide, and do not skip it. Naming what your data cannot yet decide makes the rest of your claims more credible, not less.
Minutes 11–12 — conclusions and acknowledgements. Three bullets a listener could repeat to a colleague afterwards.
Then rehearse it aloud, standing, with a timer, at least four times — twice alone and twice in front of your group. Rehearsing silently in your head always runs faster than reality, which is why first-timers overrun.
Handling questions
Questions are the part everyone dreads and the part that is most predictable. Almost all questions at a chemistry session fall into five types: a request to repeat something that was unclear, a question about a control you did or did not run, a question about mechanism or interpretation, a suggestion of another technique, and a question about scope — will it work for my system?
Four habits that work in all five cases. Listen to the end of the question instead of starting your answer halfway through. Repeat it back in one line, which buys thinking time and helps the room hear it. Answer the question that was asked, briefly. And when you do not know, say so plainly and then say what you would do to find out — "we haven't tested that yet; the control I would run is…". A calm "I don't know" is respected. A confident wrong answer is remembered.
Before, during and after — a checklist
| When | Do this |
|---|---|
| Before submitting | Read the conference's own instructions for authors; confirm eligibility, whether a supervisor's approval is needed, and any institutional permission for showing unpublished data |
| Abstract stage | Draft it, let your supervisor cut it, submit well before the last day — portals slow down at deadlines |
| Two weeks before | Poster or slides finished and reviewed by someone outside your project |
| One week before | Print the poster early; carry a digital copy and, if you can, a smaller backup print. Rehearse the talk to time |
| On the day | Arrive at your board or the session room early; test the file on the room's own computer if it is a talk |
| During the session | Stand beside your poster the whole time, not behind it. Carry a notebook for questions you cannot answer |
| After | Write up every question you were asked within a day; email the people you promised something to within a week |
Mistakes first-timers make
- Presenting everything. One question, one story. The rest is conversation material.
- A poster that is a paper. Dense paragraphs at small size are simply not read at a poster session.
- Unlabelled axes and missing units. The quickest way to lose a specialist's trust.
- Reading slides aloud. The audience reads faster than you speak. Say the message; let the slide carry the evidence.
- No error bars, no controls, no honest limitation slide. Experienced chemists ask about exactly these three, every time.
- Standing behind the poster looking at a phone. People will not interrupt you. Face outward and make eye contact.
- Showing data you do not have permission to show. Check with your supervisor about unpublished or industry-linked results before you submit, not after.
- Skipping the rest of the conference. The sessions you attend and the people you talk to over tea are worth more than your own twelve minutes.
- Not collecting contacts. Note who visited and what they suggested; one of them may be your future supervisor or examiner.
The honest value of a first conference
Very little happens because of a single poster. What happens is cumulative: you learn to describe your work in a sentence, you find out which parts of it strangers find interesting, you discover the two other groups working on your problem, and you stop being frightened of a room. Those four things change how the rest of a research degree feels — and every one of them requires you to actually stand there and present, badly if necessary, the first time.
Check the numbers before they go on the board. Rate constants, equilibrium values, Gibbs energies and concentrations printed on a poster are read closely by specialists, and an arithmetic slip is noticed immediately. The ABC Chemistry Calculator Suite lets you re-verify every value in your figures and tables before you print.
Open the ABC Chemistry Calculator Suite →Still working towards the postgraduate seat that gets you into a research group? ABC Chemistry runs IIT-JAM, GATE, CSIR-NET and CUET-PG batches at the coaching centre and online for students anywhere in India — abcchemistry.in.