JSON Resume with Social Profiles
How to add GitHub, LinkedIn, Twitter, and other social profiles to the basics.profiles array in your JSON Resume for professional online presence.
Section-Specific
Detailed Explanation
Adding Social Profiles to Your JSON Resume
The basics.profiles array lets you link your professional online presence. This is especially important for developers, where GitHub activity and technical blog posts serve as proof of expertise.
Profiles Structure
"basics": {
"name": "Jordan Lee",
"profiles": [
{
"network": "GitHub",
"username": "jordanlee",
"url": "https://github.com/jordanlee"
},
{
"network": "LinkedIn",
"username": "jordanlee",
"url": "https://linkedin.com/in/jordanlee"
},
{
"network": "Twitter",
"username": "jordanlee_dev",
"url": "https://twitter.com/jordanlee_dev"
},
{
"network": "Stack Overflow",
"username": "jordanlee",
"url": "https://stackoverflow.com/users/123456/jordanlee"
},
{
"network": "Personal Blog",
"url": "https://jordanlee.dev/blog"
}
]
}
Common Networks
| Network | When to include |
|---|---|
| GitHub | Almost always — shows your code and contributions |
| Standard for professional networking | |
| Twitter/X | If you share technical content |
| Stack Overflow | If you have a high reputation |
| Dev.to / Hashnode | If you write technical articles |
| Dribbble / Behance | For frontend/design roles |
| Personal Blog | If you maintain a technical blog |
Tips
- Only include profiles that are active and professional. An empty GitHub profile is worse than no link.
- The
usernamefield is optional but helpful for renderers that display it alongside the icon. - Keep the
urlfield as the canonical profile URL — most renderers use this for the link. - Order profiles by relevance to the role you're applying for (GitHub first for engineering roles, LinkedIn first for management roles).
Use Case
You want to link your professional online profiles (GitHub, LinkedIn, blog) in your JSON Resume to give recruiters a complete picture of your developer identity.