Quantitative Researcher/Senior Researcher – State and Local Government Services

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Mathematica" then "Primary Duties And Responsibilities", "Responsibilities And Expectations", "Required Qualifications", salary info, etc. We must use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not repeat job title. We need to include sections only when posting has real specific content. We have content for About Mathematica (company description) maybe map to "About the role"? Actually "About Mathematica" is about company, not role. Could map to "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections we have content for. We have: - About Mathematica (company overview) -> could be "About the role"? Might be better as "About the role" describing role? But we have "Primary Duties And Responsibilities" and "Responsibilities And Expectations". Those are responsibilities. - Required Qualifications includes qualifications. - Skills: we have many skill items (quantitative analytical skills, training in causal inference, etc.) Could be Skills. - Benefits: mention competitive salaries, comprehensive benefits package, ESOP, etc. Also link to benefits page. So we have benefits content. - Pay: salary ranges given for Researcher and Senior Researcher. Also mention discretionary bonus. So we have pay. - Schedule: not mentioned. So we should not include Schedule. We must not include placeholder text. So we need to extract substantive info. We need to avoid boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions (like "To apply, please submit...") should be removed. Also remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities, qualifications, skills, benefits, pay, etc. But we must remove application instructions (like "To apply, please submit a resume...") and background check info? The background check info is substantive? It's about employment contingency; maybe it's considered boilerplate? It's not EEO but it's about hiring process. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Background check info might be considered legal? It's about contingency. Might be considered legal boilerplate. Safer to remove it. Also remove "Currently, Mathematica’s largest client is CMS..." that's substantive? It's about client; maybe keep? It's not a standard heading but could be part of About Mathematica? Might be considered substantive. However it's not under any heading; we could include it in About the role? Might be okay. We need to preserve ALL substantive information; but we must remove application instructions. So we need to keep everything else except those removed. Let's parse the posting and extract sections. Original text: About Mathematica Mathematica applies expertise at the intersection of data, methods, policy, and practice to improve well-being around the world. We collaborate closely with public- and private-sector partners to translate big questions into deep insights that improve programs, refine strategies, and enhance understanding using data science and analytics. Our work yields actionable information to guide decisions in wide-ranging policy areas, from health, education, early childhood, and family support to nutrition, employment, disability, and international development. Mathematica offers our employees competitive salaries, and a comprehensive benefits package, as well as the advantages of being 100 percent employee owned. As an employee stock owner, you will experience financial benefits of ESOP holdings that have increased in tandem with the company’s growth and financial strength. You will also be part of an independent, employee-owned firm that is able to define and further our mission, enhance our quality and accountability, and steadily grow our financial strength. Read more about our benefits here: https://www.mathematica.org/career-opportunities/benefits-at-a-glance. Primary Duties And Responsibilities Mathematica is hiring researchers with expertise in quantitative research and causal inference methods and health policy research, who will conduct studies and support program evaluation in the areas of public health, rural health, and healthcare. The researchers will support project teams in the planning and execution of rigorous, data-driven research projects for state and local clients and may also contribute to evaluations for federal, leading health foundations, and commercial clients. Responsibilities And Expectations Collaborate with senior staff in a multidisciplinary environment to apply rigorous quantitative research methods, including study design, causal inference, data management, and statistical and econometric analysis for describing or evaluating programs and policiesDraft materials (reports, presentations, memos, policy briefs, dashboards) to present findings to policy, community, and professional audiencesHelp develop proposals for new research projectsContribute to the growth, expertise, and institutional knowledge of other research staff Required Qualifications All candidates should have a Ph.D. or equivalent in economics, public health, epidemiology, biostatistics, data science/data analytics, health services research, or other relevant discipline. In lieu of a Ph.D., a Masters’ degree with coursework in causal inference and demonstrated experience applying it to research will be considered equivalent.A Senior Researcher candidate should also bring at least five (5) years of relevant, full-time professional experience to the role, with experience providing leadership to teams or project groups. Strong quantitative analytical skills. Training in causal inference methodologies is strongly preferred.Broad understanding of state health policy and programsExperience working at a state or local agency or consulting with states/localities strongly preferred.Experience using healthcare and public health data sources (e.g., healthcare claims, cost data, electronic health records, national surveys) is strongly preferred.Experience working with programming languages, such as R, Python, or STATA, and with AI platforms, such as ChatGPT or Microsoft CopilotExcellent written and oral communication skills, including an ability to translate complex research methods and findings for various audiences including policymakers, providers, and community members.Comfort in client facing roles.Ability to work well in teams.Strong organizational skills and high level of attention to detail; flexibility to lead and manage multiple priorities, sometimes simultaneously, under deadlines. The Researcher role offers an anticipated annual base salary of $100,000 - $140,000 annually. The Senior Researcher role offers an anticipated annual base salary of $145,000 - $160,000 annually. Both roles are eligible for an annual discretionary bonus opportunity based on individual and company performance. To apply, please submit a resume, cover letter, and work sample or writing sample that demonstrates your independent work or work in which you played a significant role (a publication, manuscript, job market paper, dissertation chapter, etc.). Currently, Mathematica’s largest client is Centers for Medicare & Medicaid Services (CMS). Most staff working on CMS contracts will be required to complete a successful background investigation including the Questionnaire for Public Trust Position SF-85. Staff that are unable to successfully undergo the background investigation will need to be able to obtain work outside CMS. Staff will work with their supervisor to get re-staffed, however if they are unable to do so it may result in employment termination due to lack of work. We are an Equal Opportunity Employer and do not discriminate against any employee or applicant for employment because of race, color, sex, age, national origin, religion, sexual orientation, gender identity, status as a veteran, and basis of disability or any other federal, state or local protected class. At Mathematica, we understand the importance of building relationships with colleagues. If you’re not located near one of our offices but would like opportunities to meet up with co-workers, we offer coworking spaces where available. Ask your Talent Acquisition partner for more information about this opportunity and whether it’s an option in your area. Any offer of employment will be contingent upon passing a background check. Various federal agencies with whom we contract require that staff successfully undergo security clearance as a condition of working on the project. If you are assigned to such a project, you will be required to obtain the requisite security clearance. Additionally, if you participate in/complete the application process and are denied, Mathematica may choose to terminate your employment. We take pride in our employees and in their commitment to excellence. We encourage staff to collaborate in developing creative solutions to difficult problems and to share the responsibility and enjoyment of carrying out complex projects. This collegial spirit has helped us earn our reputation for innovative and high quality work. We need to remove: - Application instructions: "To apply, please submit a resume, cover letter, and work sample or writing sample that demonstrates your independent work or work in which you played a significant role (a publication, manuscript, job market paper, dissertation chapter, etc.)." - EEO statement: "We are an Equal Opportunity Employer..." remove. - Coworking spaces info? Might be considered substantive? It's about benefits? Could be considered part of benefits? It's about coworking spaces where available. Might be considered a benefit. But it's after EEO. Might keep as part of benefits? However it's not a standard benefit like health insurance. Could be considered a perk. Might keep. - Background check statements: "Any offer of employment will be contingent upon passing a background check." etc. Might be considered legal boilerplate; remove. - Security clearance statements: remove. - The sentence about Mathematica’s largest client is CMS: that's substantive? It's about client; maybe keep as part of About Mathematica? Could be included. - The sentence about staff working on CMS contracts background investigation: that's about requirement for certain roles; could be considered substantive? Might be considered a condition of employment; maybe keep? But it's somewhat specific to CMS contracts. Might be considered a requirement. However it's also about background investigation; could be considered legal. Might remove to be safe. - The sentence about staff unable to undergo background investigation need to obtain work outside CMS etc. Might be considered legal; remove. - The sentence about "We take pride in our employees..." is fluff; maybe keep? It's not boilerplate but could be considered generic. Might keep as part of About Mathematica? It's about culture. Could keep. We need to preserve ALL substantive information; but we must remove boilerplate. The line about "We take pride in our employees..." is not boilerplate but is generic fluff; still substantive? It's not specific detail. Might be considered filler. Safer to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep details that are specific. Generic fluff might be considered not substantive? It's not specific detail. Might be considered filler. I'd lean to remove generic fluff like "We take pride in our employees..." and "We encourage staff to collaborate..." as they are not specific details. However they are about culture; could be considered substantive? Hard. Given the instruction to prefer a few substantive sections over many thin ones, we can combine. Let's decide sections: - About the role: Could include description of Mathematica (company) and maybe the role context? But we have separate responsibilities and qualifications. Better to follow typical job posting structure: About the role (overview), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. We have: About the role: Could combine "About Mathematica" plus maybe the client info? But "About the role" should describe the role, not company. However we don't have a separate role overview besides duties. Could use "About the role" to summarize the role: Mathematica is hiring researchers with expertise in quantitative research and causal inference methods and health policy research, who will conduct studies and support program evaluation in the areas of public health, rural health, and healthcare. The researchers will support project teams in the planning and execution of rigorous, data-driven research projects for state and local clients and may also contribute to evaluations for federal, leading health foundations, and commercial clients. That's from Primary Duties And Responsibilities. So we can put that as About the role. Responsibilities: Use the Responsibilities And Expectations bullet list (though it's not bullet but sentences). We can convert to

• items. Requirements/Qualifications: Use Required Qualifications section. Skills: Could extract skill items from