Senior Scientist (Regulatory)

Exponent · Bowie, MD · 3 wk ago

On-siteAnalyst$113k/yrFull-time

We need to output HTML fragment with sections: About the role? The posting includes "Our Opportunity" describing role. Also "You Will Have The Following Skills And Qualifications". Also "Compensation" with salary range. Also "Benefits You Will Enjoy". Also "Work Environment". Also "Life @ Exponent". Also "Key statistics". Also "About Exponent". But we must only include sections when posting has real specific content. We need to decide which sections to include: About the role (maybe "Our Opportunity" is role description). Responsibilities? Not explicit list but there are bullet-like sentences: Managing and tracking client projects, etc. Could treat as list under Responsibilities. Requirements/Qualifications: list of qualifications. Skills: maybe separate? The posting lumps skills and qualifications together. Benefits: they mention benefits info link but not specific benefits; they say "Access benefits information on our Life@Exponent page". No specific benefits listed, so we should NOT create Benefits section because no specific content. Pay: they have salary range, so include Pay section. Schedule: not mentioned, so omit. Also "Work Environment" could be a section maybe "Work Environment". "Life @ Exponent" maybe "About the company" but we already have About Exponent. Could include "Company Overview". But rule: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should stick to those headings only. So we need to map content to those headings. - About the role: we can use "Our Opportunity" description: role description paragraph. - Responsibilities: list of duties: Managing and tracking client projects, project deliverables and budgets; Collaborating with internal project teams to discuss client projects, tasks, deliverables, and budgets; Interacting with clients as well as EPA and State regulators; Build upon your understanding of chemical regulatory policies, including TSCA, and apply regulatory insights to complex client challenges; Demonstrated experience supporting product stewardship initiatives and applying product stewardship concepts to real-world industry challenges; Preparing and submitting regulatory approval documents; Providing regulatory and technical review and quality control support for TSCA and product stewardship projects. - Requirements / Qualifications: Could combine? The posting has "You Will Have The Following Skills And Qualifications". We could split into Requirements (education, experience) and Qualifications (skills). But we can just put under Requirements (or Qualifications). Since we have both headings allowed, we can split: Requirements: B.S. degree required; M.S. or Ph.D. preferred; Experience with TSCA and other environmental regulations; Three (3) years of consulting or government regulatory experience. Qualifications: Detail oriented, able to work independently, manage time effectively; Excellent communication, writing, editing and proofreading skills; Excellent interpersonal skills and ability to work in a collaborative environment; Strong ability to organize and prioritize multiple projects with competing deadlines; Experience using AI tools such as Microsoft Copilot, with an understanding of their capabilities, limitations, and appropriate applications; Strong working knowledge of Excel, Word, PowerPoint, Outlook, Adobe Acrobat required; Exposure to sensitive information will necessitate considerable use of tact, diplomacy, discretion, and judgment; Experience with project management, budget tracking, and invoicing a plus; Strong commitment to professional development; Entrepreneurial spirit is a plus. - Skills: maybe we could separate but we already used Qualifications for skills. Could also put Skills heading for technical skills: Experience using AI tools, strong working knowledge of Office suite, etc. But to avoid duplication, we can keep Qualifications for skills and maybe not use Skills heading. However we need to include a section only when posting has real specific content. We have content for Skills (AI tools, Office suite). So we could create Skills section for those. Then Qualifications for education/experience. Let's decide: Requirements: education and years experience. Qualifications: maybe not needed if we split. But we have both headings allowed; we can use both. Better: Requirements: B.S. degree required; M.S. or Ph.D. preferred; Experience with TSCA and other environmental regulations; Three (3) years of consulting or government regulatory experience. Qualifications: Detail oriented, able to work independently, manage time effectively; Excellent communication, writing, editing and proofreading skills; Excellent interpersonal skills and ability to work in a collaborative environment; Strong ability to organize and prioritize multiple projects with competing deadlines; Experience using AI tools such as Microsoft Copilot, with an understanding of their capabilities, limitations, and appropriate applications; Strong working knowledge of Excel, Word, PowerPoint, Outlook, Adobe Acrobat required; Exposure to sensitive information will necessitate considerable use of tact, diplomacy, discretion, and judgment; Experience with project management, budget tracking, and invoicing a plus; Strong commitment to professional development; Entrepreneurial spirit is a plus. Skills: maybe we could omit because overlapped. But we already put AI tools and Office under Qualifications. Could still have Skills heading for those technical skills. But to avoid duplication, maybe we keep Qualifications as above and not use Skills. However the instruction says we can use those headings; we don't have to use all. So we can omit Skills if we feel content already covered. Pay: Salary Range USD $113,000.00 - USD $138,000.00 /Yr. Schedule: not present, omit. Benefits: not specific, omit. We also need to include a short paragraph for metadata like Job ID etc? Not needed. We need to preserve all substantive information; we must not drop any details. Ensure we include all bullet points from responsibilities and qualifications. Also include the "Key statistics" maybe not needed as it's about company; could be part of About Exponent but we already have About the role. Could we add a section "About Exponent"? Not in allowed headings. So we should not add extra headings beyond those listed. So we must fit company info maybe under About the role? But About the role is for role description. However we could include a brief paragraph about Exponent under About the role? Might be okay but risk of misalignment. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It says "include a section ONLY when the posting has real, specific content for it". So we can use those headings; we shouldn't invent other headings like "About Exponent". So we need to incorporate Exponent description somewhere, maybe under About the role as part of role description? But About the role should be about the role, not company. However we could treat "About the role" as including both role and company overview? Might be acceptable. But we could also put company info under a paragraph without heading? The instruction says output ONLY the HTML fragment; we can include
tags without heading. So we can have a
with Exponent overview before the headings. That's allowed. The heading sections are optional; we can have free
content. Thus structure:
About Exponent ... (the paragraph about Exponent).
Then

About the role

with paragraph from "Our Opportunity". Then

Responsibilities

with

... each duty. Then
Requirements
with
- ... education/experience. Then
  Qualifications
  with
  - ... skills/attributes. Then
    Pay
    with
    salary range. We should not include Benefits, Schedule. Check we didn't miss any substantive info: The "Life @ Exponent" paragraph about work environment, flexible hours, etc. That's substantive. Should we include it? Could be under a heading like "Work Environment" but not allowed. Could we put it under a
    without heading? Yes we can include a
    about work environment/life. Also the "Key statistics" could be a
    . Also the "Life @ Exponent" links maybe we can include as
    with links? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Life @ Exponent section includes links to learn more about life at Exponent and impact; that's not boilerplate, it's substantive. We should keep it. Also the "Work Environment" paragraph about in-person interactions, flexible schedule, etc. Keep. Also the "Compensation" section we already used for Pay. Also the "Benefits You Will Enjoy" we omitted because no specific benefits listed; but we could include a
    that says "Access benefits information on our Life@Exponent page: https://..." but that's basically a link; it's not specific benefits. The instruction says never create Benefits section unless posting actually states them. It does state "Access benefits information on our Life@Exponent page". That's not a benefit description; it's a referral. So we should not create Benefits section. But we could include that sentence as a
    somewhere? It's not boilerplate; it's a reference. Could be included under a
    without heading. However it's somewhat like a navigation link; but it's not navigation. I'd include it as a
    maybe under a generic section? But we have no heading for it. We could just include it as a
    after Pay. Also the "Job Locations" list: we should keep that as substantive info. Not a heading; we can include as
    or

Senior Scientist (Regulatory)

About the role

Responsibilities

Requirements

Qualifications

Pay

About the role

Responsibilities

Requirements

Qualifications

Similar jobs