What to put on a developer’s digital card
- Role and primary stack A line like “Android developer, Kotlin and Jetpack Compose” tells the person exactly which conversation to have with you later.
- Code repository link Engineers trust code they can read; one tap to your repositories answers “can they actually build?” faster than any title.
- Personal website Leads to your project write-ups and CV, so the card stays short while the detail is one click away.
- LinkedIn profile Recruiters in India move conversations to LinkedIn quickly, and it shows mutual connections that build trust with strangers.
- Open-to status A short note such as “open to backend roles, Pune or remote” saves both sides a round of questions.
- Email address A professional email, not a college or current-employer address, keeps offers and follow-ups reachable after you move on.
- Time zone and working hours If you work with distributed teams or overseas clients, “IST, overlaps with UK mornings” answers the first scheduling question before it is asked.
- One featured project A single linked project with a one-line outcome, such as an open-source library or a shipped app, gives the person something concrete to remember you by.
When to share it
- After a meetup or tech talk, when someone asks for your details and you want them to see your projects before they forget your name.
- Printed as a small QR on your hackathon badge or team slide, so judges and sponsors can reach you after results.
- In your email signature and conference-call background when you are job hunting or taking freelance contracts.
- At campus drives or alumni sessions where you speak, so students and recruiters can connect without collecting paper.
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 Ankit, good to meet you at the Go meetup today. Here is my card with my code and the billing API project I mentioned. If your team needs backend help, I am free for a call any evening this week.
Where to put the QR code
- The closing slide of a meetup talk or demo-day pitch, left on screen during questions.
- A sticker on the back of your laptop lid, where people at hackathons and co-working spaces already look.
- The README of your most-starred repository, so visitors can save your details along with the code.
Mistakes to avoid
- Linking a code profile full of forks If the first screen someone sees is ten forked tutorials, the card works against you. Pin original work, archive the rest and make sure the top repository has a clear README.
- Using a joke handle as your name A gamer tag or inside-joke username is fine on forums but confusing on a contact card. Keep your real name as the title and put the handle only in the link.
- Pointing to a portfolio built for an old stack If you have moved from PHP to Go but your website still leads with PHP projects, recruiters will file you under the wrong role. Update the featured project when your focus changes.
Tips for a card that gets saved
- Keep the stack line to three or four items. A card that lists every framework looks unfocused, while a sharp line invites the right technical conversation.
- Use a personal email and phone number, not company ones. Many developers change employers every few years, and a card tied to an old job silently stops working.
- Test the QR code on several phone cameras, Android and iOS, in low light, before an event. Keep screen brightness high when someone scans it from your phone.