Sr Data Scientist
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). The text includes some boilerplate like "Note: Exelon-sponsored compensation and benefit programs may vary..." That's part of benefits note; we should keep? It's about benefits variability; it's substantive? Might keep as part of benefits section. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The note about compensation varying is not boilerplate; it's a clarification. Keep.
We need to format sections:
- About the role? Could combine Who We Are and Primary Purpose? But we need headings for sections present: "About the role" maybe not present; we have "Who We Are" (company overview). Could treat as "About the role"? Actually "Who We Are" is company description, not role. Could make a section "About the company" but not in allowed headings list. The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings. Use "About the role" for role description (Primary Purpose). Use "Responsibilities" for Primary Duties. Use "Requirements" maybe for Minimum Qualifications? Or "Qualifications". The list includes both Requirements and Qualifications. We could put Minimum Qualifications under "Qualifications". Preferred Qualifications maybe under "Skills"? Or also under "Qualifications"? But we have both Minimum and Preferred; we could combine into Qualifications section with two subparts? But we must use
- for any list. Could use
for prose. For qualifications we could list items.
Better: Use headings: About the role (Primary Purpose), Responsibilities (Primary Duties), Qualifications (Minimum Qualifications), Skills (Preferred Qualifications maybe), Benefits, Pay, Schedule.
We need to avoid empty sections.
Let's extract content:
Who We Are: company overview. Could be part of About the role? Might be separate but not in allowed headings. Could incorporate into About the role as introductory paragraph.
Primary Purpose: "Apply the scientific method to extract knowledge and insights from data..." etc. That's role purpose.
Primary Duties: list with percentages. We'll turn into
- items.
Job Scope: description about strategic planning, advice, etc. Could be part of Responsibilities? Might be separate but not in allowed headings. Could incorporate into Responsibilities as additional duties.
Minimum Qualifications: education, experience, analytical abilities, technical knowledge, communication skills.
Preferred Qualifications: list items.
Benefits: list of benefits.
Pay: salary range and bonus.
Schedule: extended hours for storms.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Let's craft.
Section About the role:
About the role
then containing who we are + primary purpose? Could split: first paragraph who we are, second paragraph primary purpose.
But we must not repeat job title. No issue.
Responsibilities:
Responsibilities
then - each duty.
We need to include percentages? Keep them inside li.
Job Scope maybe also under Responsibilities as additional li.
Qualifications:
Qualifications
then maybe split into Minimum and Preferred? Could have two subheadings? Not allowed; only h3 for section headings. Could use with headings inside? Might be okay to have Minimum Qualifications inside
. But better to keep as one Qualifications section with two
lists: one for Minimum, one for Preferred, each preceded by a label.
Skills: maybe not needed if we put Preferred under Qualifications. But we have Skills heading allowed; we could put Preferred Qualifications under Skills. Let's do: Qualifications for Minimum, Skills for Preferred.
Thus:
Qualifications
Minimum Qualifications
...
Skills
Preferred Qualifications
...
Benefits: Benefits
...
Pay: Pay
...
Schedule: Schedule
...
Now extract details.
Who We Are paragraph: "We're powering a cleaner, brighter future. Exelon is leading the energy transformation, and we're calling all problem solvers, innovators, community builders and change makers. Work with us to deliver solutions that make our diverse cities and communities stronger, healthier and more resilient. We're powered by purpose-driven people like you who believe in being inclusive and creative, and value safety, innovation, integrity and community service. We are a Fortune 200 company, 20,000 colleagues strong serving more than 10.7 million customers at six energy companies -- Atlantic City Electric (ACE), Baltimore Gas and Electric (BGE), Commonwealth Edison (ComEd), Delmarva Power & Light (DPL), PECO Energy Company (PECO), and Potomac Electric Power Company (Pepco). We're committed to creating an environment where every person can thrive. Our employee experience is grounded in four tenets that guide how we support our people: purposeful careers, growth opportunities, community impact, and support to thrive. In our relentless pursuit of excellence, we elevate diverse voices, fresh perspectives and bold thinking. And since we know transforming the future of energy is hard work, we provide competitive compensation, incentives, excellent benefits and the opportunity to build a rewarding career. Are you in?"
Primary Purpose paragraph: "Apply the scientific method to extract knowledge and insights from data, which may take the form of time-series (smart-meters, smart-grid, and other IoT), structured (relational data stores), and unstructured (text and multi-media) data sets. Closely collaborate with various internal stakeholders, information architects, data engineers, project/program managers, and other teams to turn data into critical information to inform decision making. This requires understanding business needs, providing and receiving regular feedback, and planning the proper transfer of developed solutions. Mine big and small data for insights, using advanced statistic and machine learning methods. Validate findings with the business by sharing analysis outputs in a way that can be understood by business stakeholders. Become a subject matter expert in the areas of artificial intelligence, machine learning, feature engineering, data mining, and data manipulation/storage. Demonstrate commitment to continuous learning and professional development in technical subject matter. Share knowledge with team members, and business stakeholders, and IT partners. Collect, cleanse, standardize and analyze data from a variety of internal and external sources. Produce novel insights to help inform business actions using statistical modeling and machine learning techniques on complex data-sets on the order of several terabytes or petabytes. Position may be required to work extended hours for coverage during storms or other energy delivery emergencies."
Note: The last sentence about extended hours also appears in Primary Purpose; but we also have schedule section. Might duplicate; but we can keep it in purpose and also schedule? Might be duplicate but okay. However we should avoid duplication? Instruction: remove duplicated lines. The sentence appears only once in Primary Purpose; we could keep it there and not repeat in Schedule. But schedule section should have specific content; we could still include the same sentence but that's duplication. Better to move that sentence to Schedule section and remove from Purpose? But the purpose paragraph includes it; we could keep it there and not duplicate in Schedule; schedule section could be omitted if no unique content. However we have schedule info: "Position may be required to work extended hours for coverage during storms or other energy delivery emergencies." That's the only schedule detail. If we keep it in Purpose, we still have schedule info present; we could still create Schedule section with that sentence, but that would duplicate. To avoid duplication, we could keep it only in Schedule and remove from Purpose. But then we lose that detail from Purpose; but purpose paragraph still has many other details; removing one sentence may be okay. Let's do: keep schedule sentence only under Schedule, and remove from Purpose paragraph.
Thus edit Purpose paragraph to exclude that sentence.
Now Primary Duties list: we have bullet points with percentages.
Let's extract each:
- Develop key predictive models that lead to delivering a premier customer experience, operating performance improvement, and increased safety best practices. (25%)
- Develop and recommend data sampling techniques, data collections, and data cleaning specifications and approaches. Apply missing data treatments as needed. (25%)
- Analyze data using advanced analytics techniques in support of process improvement efforts using modern analytics frameworks, including but not limited to Python, R, Scala, or equivalent; Spark, Hadoop file system and others (15%)
- Access and analyze data sourced from various Company systems of record. Support the development of strategic business, marketing, and program implementation plans. (15%)
- Access and enrich data warehouses across multiple Company departments. Build, modify, monitor and maintain high-performance computing systems. (5%)
- Provide expert data and analytics support to multiple business units (20%)
- Works with stakeholders and subject matter experts to understand business needs, goals and objectives. Work closely with business, engineering, and technology teams to develop solution to data-intensive business problems and translates them into data science projects. Collaborate with other analytic teams across Exelon on big data analytics techniques and tools to improve analytical capabilities. (20%)
Note there are 8 items; some percentages sum >100? but okay.
Job Scope: "Support business unit strategic planning while providing a strategic view on machine learning technologies. Advice and counsel key stakeholders on machine learning findings and recommend courses of action that redirect resources to improve operational performance or assist with overall emerging business issues. Provide key stakeholders with machine learning analyses that best positions the company going forward. Educate key stakeholders on the organizations advance analytics capabilities through internal presentations, training workshops, and publications."
We'll add as li under Responsibilities maybe.
Minimum Qualifications:
Education: Bachelor's degree in a Quantitative discipline. Ex: Applied Mathematics, Computer Science, Finance, Operations Research, Physics, Statistics, or related field
4-7 years of relevant experience developing hypotheses, applying machine learning algorithms, validating results to analyze multi-terabyte datasets and extracting actionable insights is required.
Previous research or professional experience applying advanced analytic techniques to large, complex datasets.
Analytical Abilities: Strong knowledge in at least two of the following areas: machine learning, artificial intelligence, statistical modeling, data mining, information retrieval, or data visualization.
Technical Knowledge: Proven experience in developing and deploying predictive analytics projects using one or more leading languages (Python, R, Scala, etc.). Experience working within an open source environment and Unix-based OS.
Communication Skills: Ability to translate data analysis and findings into coherent conclusions and actionable recommendations to business partners, practice leaders, and executives. Strong oral and written communication skills.
Preferred Qualifications list:
- Provide senior oversight for apprentice program
- Education Masters, or PhD in Quantitative discipline. Ex Data Science, Data Analytics, Applied Mathematics, Computer Science, Finance, Ops Research,
for prose. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). The text includes some boilerplate like "Note: Exelon-sponsored compensation and benefit programs may vary..." That's part of benefits note; we should keep? It's about benefits variability; it's substantive? Might keep as part of benefits section. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The note about compensation varying is not boilerplate; it's a clarification. Keep. We need to format sections: - About the role? Could combine Who We Are and Primary Purpose? But we need headings for sections present: "About the role" maybe not present; we have "Who We Are" (company overview). Could treat as "About the role"? Actually "Who We Are" is company description, not role. Could make a section "About the company" but not in allowed headings list. The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings. Use "About the role" for role description (Primary Purpose). Use "Responsibilities" for Primary Duties. Use "Requirements" maybe for Minimum Qualifications? Or "Qualifications". The list includes both Requirements and Qualifications. We could put Minimum Qualifications under "Qualifications". Preferred Qualifications maybe under "Skills"? Or also under "Qualifications"? But we have both Minimum and Preferred; we could combine into Qualifications section with two subparts? But we must use
- for any list. Could use
for prose. For qualifications we could list items. Better: Use headings: About the role (Primary Purpose), Responsibilities (Primary Duties), Qualifications (Minimum Qualifications), Skills (Preferred Qualifications maybe), Benefits, Pay, Schedule. We need to avoid empty sections. Let's extract content: Who We Are: company overview. Could be part of About the role? Might be separate but not in allowed headings. Could incorporate into About the role as introductory paragraph. Primary Purpose: "Apply the scientific method to extract knowledge and insights from data..." etc. That's role purpose. Primary Duties: list with percentages. We'll turn into
- items.
Job Scope: description about strategic planning, advice, etc. Could be part of Responsibilities? Might be separate but not in allowed headings. Could incorporate into Responsibilities as additional duties.
Minimum Qualifications: education, experience, analytical abilities, technical knowledge, communication skills.
Preferred Qualifications: list items.
Benefits: list of benefits.
Pay: salary range and bonus.
Schedule: extended hours for storms.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Let's craft.
Section About the role:
About the role
thencontaining who we are + primary purpose? Could split: first paragraph who we are, second paragraph primary purpose. But we must not repeat job title. No issue. Responsibilities:
Responsibilities
then- each duty.
We need to include percentages? Keep them inside li.
Job Scope maybe also under Responsibilities as additional li.
Qualifications:
Qualifications
then maybe split into Minimum and Preferred? Could have two subheadings? Not allowed; only h3 for section headings. Could usewith headings inside? Might be okay to have Minimum Qualifications inside
. But better to keep as one Qualifications section with two
- lists: one for Minimum, one for Preferred, each preceded by a
label. Skills: maybe not needed if we put Preferred under Qualifications. But we have Skills heading allowed; we could put Preferred Qualifications under Skills. Let's do: Qualifications for Minimum, Skills for Preferred. Thus:
Qualifications
Minimum Qualifications
- ...
Skills
Preferred Qualifications
- ...
Benefits
- ...
Pay:
Pay
...
Schedule:Schedule
...
Now extract details. Who We Are paragraph: "We're powering a cleaner, brighter future. Exelon is leading the energy transformation, and we're calling all problem solvers, innovators, community builders and change makers. Work with us to deliver solutions that make our diverse cities and communities stronger, healthier and more resilient. We're powered by purpose-driven people like you who believe in being inclusive and creative, and value safety, innovation, integrity and community service. We are a Fortune 200 company, 20,000 colleagues strong serving more than 10.7 million customers at six energy companies -- Atlantic City Electric (ACE), Baltimore Gas and Electric (BGE), Commonwealth Edison (ComEd), Delmarva Power & Light (DPL), PECO Energy Company (PECO), and Potomac Electric Power Company (Pepco). We're committed to creating an environment where every person can thrive. Our employee experience is grounded in four tenets that guide how we support our people: purposeful careers, growth opportunities, community impact, and support to thrive. In our relentless pursuit of excellence, we elevate diverse voices, fresh perspectives and bold thinking. And since we know transforming the future of energy is hard work, we provide competitive compensation, incentives, excellent benefits and the opportunity to build a rewarding career. Are you in?" Primary Purpose paragraph: "Apply the scientific method to extract knowledge and insights from data, which may take the form of time-series (smart-meters, smart-grid, and other IoT), structured (relational data stores), and unstructured (text and multi-media) data sets. Closely collaborate with various internal stakeholders, information architects, data engineers, project/program managers, and other teams to turn data into critical information to inform decision making. This requires understanding business needs, providing and receiving regular feedback, and planning the proper transfer of developed solutions. Mine big and small data for insights, using advanced statistic and machine learning methods. Validate findings with the business by sharing analysis outputs in a way that can be understood by business stakeholders. Become a subject matter expert in the areas of artificial intelligence, machine learning, feature engineering, data mining, and data manipulation/storage. Demonstrate commitment to continuous learning and professional development in technical subject matter. Share knowledge with team members, and business stakeholders, and IT partners. Collect, cleanse, standardize and analyze data from a variety of internal and external sources. Produce novel insights to help inform business actions using statistical modeling and machine learning techniques on complex data-sets on the order of several terabytes or petabytes. Position may be required to work extended hours for coverage during storms or other energy delivery emergencies." Note: The last sentence about extended hours also appears in Primary Purpose; but we also have schedule section. Might duplicate; but we can keep it in purpose and also schedule? Might be duplicate but okay. However we should avoid duplication? Instruction: remove duplicated lines. The sentence appears only once in Primary Purpose; we could keep it there and not repeat in Schedule. But schedule section should have specific content; we could still include the same sentence but that's duplication. Better to move that sentence to Schedule section and remove from Purpose? But the purpose paragraph includes it; we could keep it there and not duplicate in Schedule; schedule section could be omitted if no unique content. However we have schedule info: "Position may be required to work extended hours for coverage during storms or other energy delivery emergencies." That's the only schedule detail. If we keep it in Purpose, we still have schedule info present; we could still create Schedule section with that sentence, but that would duplicate. To avoid duplication, we could keep it only in Schedule and remove from Purpose. But then we lose that detail from Purpose; but purpose paragraph still has many other details; removing one sentence may be okay. Let's do: keep schedule sentence only under Schedule, and remove from Purpose paragraph. Thus edit Purpose paragraph to exclude that sentence. Now Primary Duties list: we have bullet points with percentages. Let's extract each: - Develop key predictive models that lead to delivering a premier customer experience, operating performance improvement, and increased safety best practices. (25%) - Develop and recommend data sampling techniques, data collections, and data cleaning specifications and approaches. Apply missing data treatments as needed. (25%) - Analyze data using advanced analytics techniques in support of process improvement efforts using modern analytics frameworks, including but not limited to Python, R, Scala, or equivalent; Spark, Hadoop file system and others (15%) - Access and analyze data sourced from various Company systems of record. Support the development of strategic business, marketing, and program implementation plans. (15%) - Access and enrich data warehouses across multiple Company departments. Build, modify, monitor and maintain high-performance computing systems. (5%) - Provide expert data and analytics support to multiple business units (20%) - Works with stakeholders and subject matter experts to understand business needs, goals and objectives. Work closely with business, engineering, and technology teams to develop solution to data-intensive business problems and translates them into data science projects. Collaborate with other analytic teams across Exelon on big data analytics techniques and tools to improve analytical capabilities. (20%) Note there are 8 items; some percentages sum >100? but okay. Job Scope: "Support business unit strategic planning while providing a strategic view on machine learning technologies. Advice and counsel key stakeholders on machine learning findings and recommend courses of action that redirect resources to improve operational performance or assist with overall emerging business issues. Provide key stakeholders with machine learning analyses that best positions the company going forward. Educate key stakeholders on the organizations advance analytics capabilities through internal presentations, training workshops, and publications." We'll add as li under Responsibilities maybe. Minimum Qualifications: Education: Bachelor's degree in a Quantitative discipline. Ex: Applied Mathematics, Computer Science, Finance, Operations Research, Physics, Statistics, or related field 4-7 years of relevant experience developing hypotheses, applying machine learning algorithms, validating results to analyze multi-terabyte datasets and extracting actionable insights is required. Previous research or professional experience applying advanced analytic techniques to large, complex datasets. Analytical Abilities: Strong knowledge in at least two of the following areas: machine learning, artificial intelligence, statistical modeling, data mining, information retrieval, or data visualization. Technical Knowledge: Proven experience in developing and deploying predictive analytics projects using one or more leading languages (Python, R, Scala, etc.). Experience working within an open source environment and Unix-based OS. Communication Skills: Ability to translate data analysis and findings into coherent conclusions and actionable recommendations to business partners, practice leaders, and executives. Strong oral and written communication skills. Preferred Qualifications list: - Provide senior oversight for apprentice program - Education Masters, or PhD in Quantitative discipline. Ex Data Science, Data Analytics, Applied Mathematics, Computer Science, Finance, Ops Research,
- each duty.
We need to include percentages? Keep them inside li.
Job Scope maybe also under Responsibilities as additional li.
Qualifications:
- items.
Job Scope: description about strategic planning, advice, etc. Could be part of Responsibilities? Might be separate but not in allowed headings. Could incorporate into Responsibilities as additional duties.
Minimum Qualifications: education, experience, analytical abilities, technical knowledge, communication skills.
Preferred Qualifications: list items.
Benefits: list of benefits.
Pay: salary range and bonus.
Schedule: extended hours for storms.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Let's craft.
Section About the role: