Careers / Jobs Stack
Job detail pages with employer identity, optional salary estimates, FAQs, and breadcrumb context.
When to use this stack
- Job detail pages on company career sites
- Roles that need org identity, salary clarity, and navigation
- Pages where FAQs cover location, process, and compensation
What is included
Primary job entity with title, description, dates, employer, and location.
Employer identity for trust and eligibility.
Optional salary estimates to align with job surfaces.
Answer application process, location, and compensation questions.
Navigation context within careers.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- datePosted
- description
- employmentType
- estimatedSalary.currency
- estimatedSalary.percentile50.value
- hiringOrganization.name
- itemListElement[].name
- jobLocation.address.addressCountry
- jobLocation.address.addressLocality
- jobLocation.address.addressRegion
- logo
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- title
- url
- validThrough
Recommended properties
- applicantLocationRequirements.name
- baseSalary.currency
- baseSalary.value.unitText
- baseSalary.value.value
- contactPoint.contactType
- contactPoint.telephone
- directApply
- estimatedSalary.percentile10.value
- estimatedSalary.percentile90.value
- estimatedSalary.unitText
- hiringOrganization.url
- industry
- itemListElement[].item
- jobLocation.address.postalCode
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- sameAs[]
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "JobPosting",
"@id": "https://www.example.com/careers/senior-fe#job",
"title": "Senior Frontend Engineer",
"description": "Build and optimize our web app experience. Collaborate with design and product to ship performant UI.",
"datePosted": "2026-02-18",
"validThrough": "2026-03-20",
"employmentType": "FULL_TIME",
"hiringOrganization": {
"@type": "Organization",
"name": "Example Software",
"url": "https://www.example.com",
"logo": "https://www.example.com/images/logo-120x60.png"
},
"jobLocation": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Austin",
"addressRegion": "TX",
"addressCountry": "US"
}
},
"applicantLocationRequirements": {
"@type": "Country",
"name": "US"
},
"directApply": true,
"baseSalary": {
"@type": "MonetaryAmount",
"currency": "USD",
"value": {
"@type": "QuantitativeValue",
"value": 165000,
"unitText": "YEAR"
}
},
"estimatedSalary": {
"@type": "MonetaryAmountDistribution",
"currency": "USD",
"unitText": "YEAR",
"percentile10": {
"@type": "MonetaryAmount",
"value": 145000,
"currency": "USD"
},
"percentile50": {
"@type": "MonetaryAmount",
"value": 165000,
"currency": "USD"
},
"percentile90": {
"@type": "MonetaryAmount",
"value": 185000,
"currency": "USD"
}
},
"industry": "Software",
"identifier": {
"@type": "PropertyValue",
"name": "Req ID",
"value": "FE-2026-01"
}
},
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#org",
"name": "Example Software",
"url": "https://www.example.com",
"logo": "https://www.example.com/images/logo-120x60.png",
"sameAs": [
"https://www.linkedin.com/company/example",
"https://twitter.com/example"
]
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Is this role remote?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We are remote-first in the US with optional coworking stipends."
}
},
{
"@type": "Question",
"name": "What is the interview process?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Intro call, portfolio review, a live pairing session, and final panel. No take-home test."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Careers", "item": "https://www.example.com/careers" },
{ "@type": "ListItem", "position": 3, "name": "Senior Frontend Engineer", "item": "https://www.example.com/careers/senior-fe" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Do I have to include estimatedSalary?
No. It’s optional. If you include it, keep currency and unitText aligned; otherwise omit that section.
What if the role is remote anywhere?
Set applicantLocationRequirements to a broader region or omit it; keep jobLocation consistent with how you list the role on the page.