src/content/experiences/ with frontmatter that conforms to the experience schema.
Schema Definition
The experience schema is defined insrc/content/config.ts using Zod validation.
Fields
Your job title or position name.Example:
"Software Development Engineer 2"The name of the company or organization where you worked.Example:
"SaaS Labs"The date you started this position in
YYYY-MM-DD format.Example: 2025-04-01Optional end date of the position in
YYYY-MM-DD format. Omit this field if you are currently in this role.Example: 2026-03-31Optional array of technologies, skills, or tools used in this role. Useful for showcasing your technical expertise.Example:
["Remix", "Typescript", "Tailwind CSS", "ChatGPT Apps SDK", "MCP"]Example Experience File
Here’s a complete example of an experience MDX file:src/content/experiences/sde2.mdx
Field Requirements
| Field | Type | Required | Default |
|---|---|---|---|
title | string | Yes | - |
company | string | Yes | - |
startDate | date | Yes | - |
endDate | date | No | undefined |
tags | string[] | No | undefined |
Current vs Past Positions
To indicate a current position (ongoing role):- Omit the
endDatefield entirely - The absence of
endDatesignals that this is your current role
endDate:
Usage Notes
- The
slugfield in frontmatter is used for routing but is not part of the schema validation - Both
startDateandendDatemust be in ISO format (YYYY-MM-DD) - If
endDateis omitted, the role is considered current/ongoing - Tags are case-sensitive and will be displayed exactly as entered
- The MDX body content can include detailed descriptions of your responsibilities, achievements, and projects
- Use HTML elements (like
<ul>,<li>,<a>) for rich formatting when needed