Skip to main content

Overview

The PersonalInfo interface defines the structure for personal information and contact details that appear at the top of a resume.

Type definition

export interface PersonalInfo {
  name: string;
  title: string;
  location: string;
  phone: string;
  email: string;
  website: string;
  linkedin: string;
  github: string;
  twitter: string;
  imageUrl: string;
}

Properties

name
string
required
Full name of the person. Typically displayed prominently at the top of the resume.
title
string
required
Professional title or role (e.g., “Senior Software Engineer”, “Product Designer”). Appears below the name.
location
string
required
Current location or preferred work location (e.g., “New York, NY”, “Remote”).
phone
string
required
Contact phone number. Can include country code and formatting (e.g., “+1 (555) 123-4567”).
email
string
required
Email address for professional contact.
website
string
required
Personal website or portfolio URL. Can be an empty string if not applicable.
linkedin
string
required
LinkedIn profile URL. Can be an empty string if not applicable.
github
string
required
GitHub profile URL. Particularly relevant for technical roles. Can be an empty string if not applicable.
twitter
string
required
Twitter/X profile URL. Can be an empty string if not applicable.
imageUrl
string
required
URL to profile photo or headshot. Can be an empty string if no image is provided.

Example

{
  "name": "Alex Johnson",
  "title": "DevOps Engineer",
  "location": "Austin, TX",
  "phone": "+1 (512) 555-0123",
  "email": "[email protected]",
  "website": "https://alexjohnson.io",
  "linkedin": "https://linkedin.com/in/alexjohnson",
  "github": "https://github.com/alexj",
  "twitter": "https://twitter.com/alexjohnson",
  "imageUrl": "https://example.com/photos/alex.jpg"
}

Usage notes

  • All fields are required in the type definition, but can be empty strings for optional social links
  • The imageUrl field is used to display a profile photo in resume templates that support images
  • Social links (LinkedIn, GitHub, Twitter) are typically rendered as clickable icons or links
  • Phone and email are primary contact methods and should always be valid

Build docs developers (and LLMs) love