What to put on a data scientist’s digital card
- Modelling focus A line such as “demand forecasting and pricing experiments” tells people which problems to bring to you.
- Domain Lending, retail, health or ad tech; domain knowledge often decides a shortlist as much as technique.
- Project write-ups link Leads to end-to-end case studies so the reader sees your reasoning, not just the result.
- Code repositories Clean, runnable notebooks and pipelines show practical skill to engineering-minded reviewers.
- LinkedIn Recruiters and hiring managers often continue the conversation there.
- Email address A personal address keeps collaboration and job conversations reachable over time.
- Deployment experience A line such as “models served through batch pipelines and REST APIs” tells a team whether you stop at notebooks or can work with engineers to put models into production.
- Talks or papers Links to a conference talk, blog post or paper show you can explain complex methods to others, which hiring managers value for senior roles and cross-team work.
When to share it
- After presenting at an ML or analytics meetup, so attendees can find your slides and code.
- At hackathons and data challenges where judges, mentors and sponsors scout for talent and remember strong team presentations.
- In campus placement talks or alumni sessions where students and recruiters want to follow your work.
- Shared after a take-home assignment review, so the panel can see related projects in your portfolio and the way you document experiments.
What to say when you send it
A card link on its own is easy to ignore. Add a line that reminds the person where you met and what to do next — for example:
Hi Anita, thanks for the questions on my forecasting talk today. My card links to the slides and a notebook with the synthetic dataset. If your team is exploring stock planning models, I am happy to talk next week.
Where to put the QR code
- The last slide of a meetup or conference talk, next to the slides and code links.
- The README of your most-used open-source notebook or library.
- A printed poster at a research or student showcase event.
Mistakes to avoid
- Linking only certificates A card that leads to a list of online course certificates tells reviewers little. Link to a project write-up with real reasoning and evaluation instead.
- Using a vague title like “AI enthusiast” Hiring managers search for plain titles. Use “Data Scientist” with your focus area, so you appear in searches and readers know what to expect.
- Linking repositories with stale results If your notebook shows results from an old run that no longer match the code, careful reviewers will notice. Rerun and update before sharing the card at an event.
Tips for a card that gets saved
- Feature one project that matches the audience; a fintech meetup will respond better to a credit-risk write-up than to an image classifier.
- Keep repositories linked from the card tidy, with clear READMEs and a results summary at the top, since many reviewers will open only the first one.
- Avoid listing every library you have touched; a short, honest stack line invites deeper technical conversation and keeps interviewers focused on the tools you know well.