Senior Software Engineer, Frontend, Design Systems
for section headings. We need to include sections only when posting has real content. We have content for About the team (first paragraph). Then "What You Will Do" is responsibilities. Then "Your profile" includes sub-sections: Languages & Frameworks, AI & Automation, Quality, Communication & Collaboration, Education and Experience, Bonus if you have... Might be considered as Requirements/Qualifications/Skills. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings where appropriate. We need to decide which sections to include.
We have:
- About The Team: could map to "About the role". Provide description of team and role.
- What You Will Do: Responsibilities.
- Your profile: includes Languages & Frameworks, AI & Automation, Quality, Communication & Collaboration, Education and Experience, Bonus if you have... These could be Requirements/Qualifications/Skills. We need to decide which headings to use. Probably combine into Requirements (or Qualifications) and Skills. The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Qualifications not needed if we put everything in Requirements. But we need to include Benefits, Pay, Schedule only if posting actually states them. The posting includes: "For this role, the target base salary range in San Francisco is $156,000-$195,000 annually. This role is also eligible for equity and benefits." Also later: "Benefits Competitive salary, equity, benefits, and perks for all full-time employees..." So we have Benefits and Pay details. Also schedule: "This role will be in-office on a hybrid schedule — Turists will be expected to work in the office 3 days per week on Mondays, Wednesdays, and Thursday." So we have Schedule.
Thus we include sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the scam alert, AI policy, EEO statements, etc. Also remove "About Turo" etc. Keep substantive info.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the sections we keep, but we can omit boilerplate.
Let's extract content:
About The Team paragraph:
"We’re looking for a Senior Front-End Software Engineer to join Turo’s Design Systems team. You’ll help us architect, build, document, and maintain Pedal, our cross-platform system for iOS, Android, and Web. This role combines engineering and enablement. You’ll build foundations and components for Web, develop automation for scale, and help lead our team’s efforts to roll out AI-assisted workflows across Product, Design, and Engineering. You’ll also build relationships, process, tooling, and documentation to support an effective and well managed contribution model."
That's the about the role.
What You Will Do (Responsibilities) list:
- Architect, build, document, and maintain design system foundations and components for Web, with an eye toward cross-platform consistency.
- Develop and maintain automations for release workflows, token pipelines, asset updates, documentation, testing, and adoption measurement.
- Own the Pedal web repo: publish packages, merge dependency updates, maintain CI pipelines, GitHub Actions, and release processes.
- Lead development of AI-assisted systems and workflows that support product development. Collaborate on both technical implementation and organizational decision-making to help the team align on tools, techniques, and governance.
- Build relationships with product teams that support and encourage system contribution. Evangelize, coach, and educate contributing designers and engineers. Provide customer support and education for system users.
- Advise, coach, and mentor other engineers.
- Participate in the hiring process.
- Other duties as assigned.
We need to put these in - .
Your profile sections:
Languages & Frameworks: "Fluent in HTML, CSS, CSS-in-JS, TypeScript, React, Git, GitHub. Proficient with Storybook and Chromatic. Familiar with Figma, SwiftUI, Jetpack Compose."
AI & Automation: "1+ years of regular use of LLMs and related tools in your engineering workflow. Experience contributing to AI infrastructure for your organization. You’ve helped teams select tooling and develop governance for shared context."
Quality: "Skilled at developing and maintaining automated test coverage that provides high confidence with minimal friction. Accessibility is a first-order concern in your work, not an afterthought. Expertise developing responsive, flexible components that support internationalization, user preference, and the unexpected. Deep understanding of composition in declarative component frameworks."
Communication & Collaboration: "Excellent verbal and written communication skills, especially when explaining complex technical concepts to non-technical audiences. Experience developing projects start-to-finish in close, genuine collaboration with designers and engineers across multiple platforms. Not parallel work, integrated work. Strong organizational skills, and an established practice to manage focus and maintain attention to detail, especially through long, complex projects with shifting requirements. Track record of delivering projects on time."
Education and Experience: "Bachelor’s degree in Computer Science or equivalent. 4+ years of professional experience as a front-end software engineer, ideally with experience on cross-functional product teams. 2+ of those years focused on Design Systems work within a dedicated Design Systems team. Experience collaborating with designers, DS engineers, and system users during development of accessible, composable components with interfaces aligned across design and other supported platforms. Experience guiding DS designers by providing engineering platform requirements, accessibility requirements, implementation examples from other systems, and exploratory code prototyping. Hands-on experience migrating new components or breaking changes into a consuming application."
Bonus if you have: "Experience with contribution models. You’ve worked at a company where product teams actively contribute to a shared design system, and you’ve helped make that work well. Experience with LLM context engineering. Previous experience in service industries, agencies, or other customer-focused environments."
We also have a paragraph about values: "We value invention, pragmatism, hustle, and empathy. We exist to make our product development teams more effective." Could be part of About the role or maybe not needed. It's substantive but not under a specific heading. Could be included in About the role paragraph.
We also have Pay: "For this role, the target base salary range in San Francisco is $156,000-$195,000 annually. This role is also eligible for equity and benefits. In general, our ranges reflect the market-based target for new hire salaries based on the level and location of the role. Within the range, individual pay is determined by objective factors assessed during the application and interview process, such as job-related skills, experience, and relevant education or training. We encourage you to talk with your recruiter to learn more about the total compensation and benefits available for this role."
We have Benefits: "Competitive salary, equity, benefits, and perks for all full-time employees Employer-paid medical, dental, and vision insurance (Country specific) Retirement employer match Learning & Development stipend to invest in your professional development Turo host matching program Turo travel credit Cell phone and internet stipend Paid time off to relax and recharge Paid holidays, volunteer time off, and parental leave For those who are in the office full-time or hybrid we have in-office lunch, office snacks, and fun activities"
Schedule: "Turo highly values having employees working in-office to foster a collaborative work environment and company culture. This role will be in-office on a hybrid schedule — Turists will be expected to work in the office 3 days per week on Mondays, Wednesdays, and Thursday. Turo considers working in the office at least 3 days per week to be an essential function of this hybrid role. Your recruiter can share more information about the various in-office perks Turo offers."
We need to output only HTML fragment, no markdown fences.
We must not include boilerplate like scam alert, AI policy, EEO, etc. Also remove duplicated lines.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
We'll produce:
About the role
... (the about team paragraph plus maybe the values sentence)
Responsibilities
- ... each responsibility
Requirements
We could combine Languages & Frameworks, AI & Automation, Quality, Communication & Collaboration, Education and Experience, Bonus if you have into a single Requirements section with subheadings? But we cannot use headings other than for section headings; we could still use ? Not allowed? The instruction only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use
for each subsection inside Requirements. Or we could split into Requirements and Skills. But we prefer few sections. Let's make one Requirements section containing all the profile details as paragraphs.
We need to preserve all substantive info; we can break into paragraphs for readability.
Thus:
Requirements
Languages & Frameworks: Fluent in HTML, CSS, CSS-in-JS, TypeScript, React, Git, GitHub. Proficient with Storybook and Chromatic. Familiar with Figma, SwiftUI, Jetpack Compose.
AI & Automation: 1+ years of regular use of LLMs and related tools in your engineering workflow. Experience contributing to AI infrastructure for your organization. You’ve helped teams select tooling and develop governance for shared context.
Quality: Skilled at developing and maintaining automated test coverage that provides high confidence with minimal friction. Accessibility is a first-order concern in your work, not an afterthought. Expertise developing responsive, flexible components that support internationalization, user preference, and the unexpected. Deep understanding of composition in declarative component frameworks.
Communication & Collaboration: Excellent verbal and written communication skills, especially when explaining complex technical concepts to non-technical audiences. Experience developing projects start-to-finish in close, genuine collaboration with designers and engineers across multiple platforms. Not parallel work, integrated work. Strong organizational skills, and an established practice to manage focus and maintain attention to detail, especially through long, complex projects with shifting requirements. Track record of delivering projects on time.
Education and Experience: Bachelor’s degree in Computer Science or equivalent. 4+ years of professional experience as a front-end software engineer, ideally with experience on cross-functional product teams. 2+ of those years focused on Design Systems work within a dedicated Design Systems team. Experience collaborating with designers, DS engineers, and system users during development of accessible, composable components with interfaces aligned across design and other supported platforms. Experience guiding DS designers by providing engineering platform requirements, accessibility requirements, implementation examples from other systems, and exploratory code prototyping. Hands-on experience migrating new components or breaking changes into a consuming application.
Bonus: Experience with contribution models. You’ve worked at a company where product teams actively contribute to a shared design system, and you’ve helped make that work well. Experience with LLM context engineering. Previous experience in service industries, agencies, or other customer-focused environments.
Then Benefits:
Benefits
Competitive salary, equity, benefits, and perks for all full-time employees. Employer-paid medical, dental,
- .
Your profile sections:
Languages & Frameworks: "Fluent in HTML, CSS, CSS-in-JS, TypeScript, React, Git, GitHub. Proficient with Storybook and Chromatic. Familiar with Figma, SwiftUI, Jetpack Compose."
AI & Automation: "1+ years of regular use of LLMs and related tools in your engineering workflow. Experience contributing to AI infrastructure for your organization. You’ve helped teams select tooling and develop governance for shared context."
Quality: "Skilled at developing and maintaining automated test coverage that provides high confidence with minimal friction. Accessibility is a first-order concern in your work, not an afterthought. Expertise developing responsive, flexible components that support internationalization, user preference, and the unexpected. Deep understanding of composition in declarative component frameworks."
Communication & Collaboration: "Excellent verbal and written communication skills, especially when explaining complex technical concepts to non-technical audiences. Experience developing projects start-to-finish in close, genuine collaboration with designers and engineers across multiple platforms. Not parallel work, integrated work. Strong organizational skills, and an established practice to manage focus and maintain attention to detail, especially through long, complex projects with shifting requirements. Track record of delivering projects on time."
Education and Experience: "Bachelor’s degree in Computer Science or equivalent. 4+ years of professional experience as a front-end software engineer, ideally with experience on cross-functional product teams. 2+ of those years focused on Design Systems work within a dedicated Design Systems team. Experience collaborating with designers, DS engineers, and system users during development of accessible, composable components with interfaces aligned across design and other supported platforms. Experience guiding DS designers by providing engineering platform requirements, accessibility requirements, implementation examples from other systems, and exploratory code prototyping. Hands-on experience migrating new components or breaking changes into a consuming application."
Bonus if you have: "Experience with contribution models. You’ve worked at a company where product teams actively contribute to a shared design system, and you’ve helped make that work well. Experience with LLM context engineering. Previous experience in service industries, agencies, or other customer-focused environments."
We also have a paragraph about values: "We value invention, pragmatism, hustle, and empathy. We exist to make our product development teams more effective." Could be part of About the role or maybe not needed. It's substantive but not under a specific heading. Could be included in About the role paragraph.
We also have Pay: "For this role, the target base salary range in San Francisco is $156,000-$195,000 annually. This role is also eligible for equity and benefits. In general, our ranges reflect the market-based target for new hire salaries based on the level and location of the role. Within the range, individual pay is determined by objective factors assessed during the application and interview process, such as job-related skills, experience, and relevant education or training. We encourage you to talk with your recruiter to learn more about the total compensation and benefits available for this role."
We have Benefits: "Competitive salary, equity, benefits, and perks for all full-time employees Employer-paid medical, dental, and vision insurance (Country specific) Retirement employer match Learning & Development stipend to invest in your professional development Turo host matching program Turo travel credit Cell phone and internet stipend Paid time off to relax and recharge Paid holidays, volunteer time off, and parental leave For those who are in the office full-time or hybrid we have in-office lunch, office snacks, and fun activities"
Schedule: "Turo highly values having employees working in-office to foster a collaborative work environment and company culture. This role will be in-office on a hybrid schedule — Turists will be expected to work in the office 3 days per week on Mondays, Wednesdays, and Thursday. Turo considers working in the office at least 3 days per week to be an essential function of this hybrid role. Your recruiter can share more information about the various in-office perks Turo offers."
We need to output only HTML fragment, no markdown fences.
We must not include boilerplate like scam alert, AI policy, EEO, etc. Also remove duplicated lines.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
We'll produce:
About the role
... (the about team paragraph plus maybe the values sentence)
Responsibilities
- ... each responsibility
Requirements
We could combine Languages & Frameworks, AI & Automation, Quality, Communication & Collaboration, Education and Experience, Bonus if you have into a single Requirements section with subheadings? But we cannot use headings other thanfor section headings; we could still use
? Not allowed? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use
for each subsection inside Requirements. Or we could split into Requirements and Skills. But we prefer few sections. Let's make one Requirements section containing all the profile details as paragraphs. We need to preserve all substantive info; we can break into paragraphs for readability. Thus:
Requirements
Languages & Frameworks: Fluent in HTML, CSS, CSS-in-JS, TypeScript, React, Git, GitHub. Proficient with Storybook and Chromatic. Familiar with Figma, SwiftUI, Jetpack Compose.
AI & Automation: 1+ years of regular use of LLMs and related tools in your engineering workflow. Experience contributing to AI infrastructure for your organization. You’ve helped teams select tooling and develop governance for shared context.
Quality: Skilled at developing and maintaining automated test coverage that provides high confidence with minimal friction. Accessibility is a first-order concern in your work, not an afterthought. Expertise developing responsive, flexible components that support internationalization, user preference, and the unexpected. Deep understanding of composition in declarative component frameworks.
Communication & Collaboration: Excellent verbal and written communication skills, especially when explaining complex technical concepts to non-technical audiences. Experience developing projects start-to-finish in close, genuine collaboration with designers and engineers across multiple platforms. Not parallel work, integrated work. Strong organizational skills, and an established practice to manage focus and maintain attention to detail, especially through long, complex projects with shifting requirements. Track record of delivering projects on time.
Education and Experience: Bachelor’s degree in Computer Science or equivalent. 4+ years of professional experience as a front-end software engineer, ideally with experience on cross-functional product teams. 2+ of those years focused on Design Systems work within a dedicated Design Systems team. Experience collaborating with designers, DS engineers, and system users during development of accessible, composable components with interfaces aligned across design and other supported platforms. Experience guiding DS designers by providing engineering platform requirements, accessibility requirements, implementation examples from other systems, and exploratory code prototyping. Hands-on experience migrating new components or breaking changes into a consuming application.
Bonus: Experience with contribution models. You’ve worked at a company where product teams actively contribute to a shared design system, and you’ve helped make that work well. Experience with LLM context engineering. Previous experience in service industries, agencies, or other customer-focused environments.
Then Benefits:Benefits
Competitive salary, equity, benefits, and perks for all full-time employees. Employer-paid medical, dental,