Field Medical Outcomes, Director, MD
Pfizer · Los Angeles, CA · 1 mo ago
Healthcare$231k–$385k/yrFull-time
We need to output HTML fragment with sections: About the role (role summary), Responsibilities, Requirements (Qualifications), Skills maybe, Benefits, Pay, Schedule only if present. The posting includes: Role Summary (we can call About the role). Responsibilities section (Role Responsibilities). Basic Qualifications and Preferred Qualifications (these are qualifications). Also Non-standard Work Schedule, Travel Or Environment Requirements (travel, schedule). Also Other Job Details: Last Date to Apply, Territories covered, Eligible for Reloca (cut off). We need to include only sections with real specific content. We should not include placeholder like "commensurate with experience". There's no explicit Pay or Benefits. So we should not create Pay/Benefits sections. Schedule: there is travel requirements, non-standard work schedule. That could be considered Schedule section? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include Schedule if posting actually states them. It does state travel %, ability to work weekends, fly, overnight travel. So we can include a Schedule section with that content. Benefits: none mentioned. Skills: maybe we could extract skills from qualifications? But better to have Requirements (Qualifications) covering basic and preferred qualifications. Could also have Skills section if we want to separate but not required. We'll include About the role, Responsibilities, Requirements (maybe split into Basic Qualifications and Preferred Qualifications as subheadings? But only
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include Schedule if posting actually states them. It does state travel %, ability to work weekends, fly, overnight travel. So we can include a Schedule section with that content. Benefits: none mentioned. Skills: maybe we could extract skills from qualifications? But better to have Requirements (Qualifications) covering basic and preferred qualifications. Could also have Skills section if we want to separate but not required. We'll include About the role, Responsibilities, Requirements (maybe split into Basic Qualifications and Preferred Qualifications as subheadings? But only allowed for section headings; we could use for Requirements and then inside have
for Requirements and then inside have
or
- . Could also have two subsections but not required. We'll combine.
We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title. Must not include Job ID/requisition numbers. Must remove boilerplate like cookie/navigation/legal/EEO etc. There's none visible.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
- ... each responsibility ...
About the role
... role summary text ...