What to put on a software engineer’s digital card
- Role and primary stack Backend Go engineer or Android developer tells people immediately whether your skills match their team.
- Code profile link Engineers and hiring managers look at real code and commit history before recommending someone.
- Portfolio or write-ups link Takes people to project explanations and engineering posts that show how you think.
- LinkedIn profile Recruiters use it for your full work history and to send connection requests after events.
- Professional email Preferred by most recruiters for outreach, interview scheduling and offer discussions with engineers.
- Open to A short line such as “open to backend roles, Bengaluru or remote” sets expectations for recruiters.
- Systems you have worked on A line such as “payments, search and messaging at scale” tells an engineering manager more about your experience than a list of languages.
- Preferred work setup Remote, hybrid or office, and the city you are in, are the first filters many recruiters apply, so stating them saves both sides time.
When to share it
- Shared by QR code with other engineers at a tech meetup or conference after a hallway conversation about a shared problem.
- Shown on the last slide of a talk you give at a meetup, so attendees can find your code and write-ups.
- Sent to a former colleague who offered to refer you, so they can forward complete details to their hiring manager.
- Exchanged with teammates at a hackathon so you can collaborate on the project after the event ends.
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 Varun, it was great to discuss queue design after your talk. My card links to my write-up on the message-retry system I mentioned. If your infrastructure team is hiring later this year, I would like to stay in touch.
Where to put the QR code
- The closing slide of a conference talk or internal tech talk.
- Your name badge at an engineering conference or hiring event.
- The top of your engineering blog posts, so readers can save your contact.
Mistakes to avoid
- Mentioning your employer’s internal systems by name Codenames and internal details may be confidential, and naming them can breach your employment terms. Describe the kind of system and the problem it solved in general terms instead.
- Linking a résumé PDF that is years old A stale CV link undercuts a polished card. Point to a page you update, or replace the PDF each time you change roles.
- Listing seniority without evidence A “staff engineer” title with no write-up or project link gives people nothing to judge. Link one design write-up that shows your level.
Tips for a card that gets saved
- If you are not actively job hunting, leave out the “open to” line and phone number. Your card can simply be a professional contact point until you are ready.
- Pin your best two repositories on your code profile, since that is where people land from your card and they may not scroll further.
- Use a personal email rather than your employer’s address, so the card keeps working after you change jobs and recruiters can still reach you.