DEV Community

Irfan Tayyab
Irfan Tayyab

Posted on

How do you keep your resume and portfolio in sync?

I've noticed my professional details live in at least three places: my resume, my LinkedIn and my portfolio site. Every time something changes, a new job, a retitled role, a new link, I have to remember to update all of them. I recently retitled one of my roles on LinkedIn and found my resume still said the old title.

Small slips, but a recruiter who sees two versions might wonder which one is true.

How do you handle it?

  • Do you have a single source you copy from?
  • Do you just update everything by hand when something changes?
  • Has anyone automated any of it?
  • Or do you not worry, since nobody compares them closely?

For what it's worth, I automated part of it: my site's facts are generated from my LaTeX resume, and the build fails if the two disagree (wrote it up here). But LinkedIn still has to be updated by hand, since it has no API for that, so I'm curious how others handle it.

Top comments (7)

Collapse
 
alexcodebytes profile image
Oleksandr •

LaTeX is definitely the way to go for the pdf. my portfolio is just a static site generated from the same yaml data. but yeah, linkedin is the eternal pain point. there's no good way to automate it, so i just set a recurring calendar reminder once a month to manually check the dates and titles.

Collapse
 
irfantayyab profile image
Irfan Tayyab •

True.

Ever considered automating updating LinkedIn using some Node.js script that opens the browser and does the work in our stead?

Possibly it might really solve the LinkedIn part too :D

Worth looking into it. I might just do it.

Collapse
 
alexcodebytes profile image
Oleksandr •

honestly man, i'd be careful with that. linkedin's bot detection is absolutely ruthless. they will flag your account and restrict it faster than you can say "puppeteer". it's a fun weekend project, but definitely not worth risking a permanent ban on your main profile lmao.

Thread Thread
 
irfantayyab profile image
Irfan Tayyab •

OMG, I had no idea about LinkedIn being that good in bot detection. Thanks for the heads up though 😂

Thread Thread
 
alexcodebytes profile image
Oleksandr •

haha yeah, they don't mess around. i know a guy who got a 48-hour ban just for using a script to send connection requests. as soon as you start simulating clicks, they catch on scary fast. manual updates are the way to go for now! 😅

Thread Thread
 
irfantayyab profile image
Irfan Tayyab •

Wow, looks like this is the point where my laziness should stop and I should really do it manually :p

Collapse
 
ayushdhanani369 profile image
Ayush Dhanani •

Single source is the part I would keep. I build Aladdin, a job agent, and the same drift shows up there. A resume says one title, a form asks for another, and the agent has to pick.

My rule is to tailor only from the user's own facts, and to ask the user when an answer is unknown instead of guessing. It is slower, but it stops a small retitle from turning into two different versions of the same job.

Your build failing when the site and resume disagree is the right idea. That is the check I would want before anything goes out.