Skip to main content
Work experience entries showcase your professional journey and career progression. They’re stored in src/content/experience/ as markdown files with frontmatter defining company metadata.

Experience Collection Schema

The experience collection is defined in src/content.config.ts with the following schema:
string
required
The name of the company or organization (e.g., “Teya”, “Yoyo Group”)
string (URL)
required
The company’s website URL (e.g., “https://www.teya.com”)
string
required
Your job title at the company (e.g., “Senior Software Engineer”)
string
required
The time period you worked there (e.g., “January 2023 - November 2024”)
number
required
Display order for sorting (lower numbers appear first, typically newest jobs have lower numbers)

Adding Work Experience

1

Create an experience file

Navigate to src/content/experience/ and create a new .md file. Use the company name in kebab-case:
2

Add experience frontmatter

Start with YAML frontmatter containing all required fields:
3

List responsibilities and achievements

Below the frontmatter, use a bulleted list to describe your key responsibilities and achievements:
4

Preview your experience section

Run your development server to see the experience entry:
Experience entries typically appear on your about or resume page.

Understanding the Order Field

The order field controls the display sequence of your work experience. Lower numbers appear first:
This allows you to display your work history in reverse chronological order (most recent first), which is the standard format for resumes and portfolios.

Real-World Examples

File Organization

Experience entries are stored in src/content/experience/:
Use the company name (in kebab-case) as the filename for easy identification and organization.

Writing Effective Descriptions

Use Action Verbs

Start each bullet point with strong action verbs:
  • Built, Developed, Implemented - for creating new things
  • Led, Spearheaded, Managed - for leadership roles
  • Improved, Optimized, Enhanced - for improvements
  • Designed, Architected, Planned - for architectural work
  • Collaborated, Partnered, Coordinated - for teamwork

Quantify When Possible

Add numbers to demonstrate impact:

Highlight Technologies

Use bold to emphasize key technologies and tools:

Period Formatting

Be consistent with period formatting. Common formats include:
Choose one format and use it consistently across all experience entries for a professional appearance.

Best Practices

  1. Order chronologically - Use the order field to display most recent jobs first
  2. Be specific - Describe concrete achievements, not just responsibilities
  3. Use metrics - Quantify impact with numbers whenever possible
  4. Highlight technologies - Bold key technologies and tools you used
  5. Focus on impact - Explain what you built and why it mattered
  6. Keep it concise - Aim for 4-6 bullet points per role
  7. Update regularly - Keep your experience current as you take on new responsibilities
  8. Link to companies - Always include accurate company websites

Querying Experience

In your Astro components, query experience entries using the Content Collections API:

Adding Company Logos

While not part of the schema, you can add company logos to your experience section by:
  1. Storing logos in public/companies/:
  2. Referencing them in your Astro component based on company name:

Resume Integration

Experience entries work great for both:
  • Web portfolio - Display on your about/resume page
  • PDF resume - Query and format for downloadable PDF resume
  • LinkedIn sync - Use as source of truth for LinkedIn profile
Keep your experience entries up-to-date, and you’ll always have current resume content ready to use anywhere.