Technology Risk Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have:
- Position Summary: description of role, responsibilities, etc. Could be "About the role" or "Position Summary". Use heading "About the role". Provide paragraph.
- Key Responsibilities: list of duties. Use - .
- Required Qualifications: list. Use heading "Requirements" or "Qualifications". The instruction includes Requirements, Qualifications, Skills. We have Required Qualifications and Preferred Qualifications. Could combine into "Requirements" (required) and maybe "Preferred Qualifications" as a subsection? But we should avoid thin sections. Could have "Requirements" for required qualifications, and maybe "Preferred Qualifications" as another heading if content is substantive. It is substantive. So we can have two sections: "Requirements" and "Preferred Qualifications". Or we could merge into "Qualifications" with required and preferred sublists? But instruction says use headings from list; we can use "Qualifications" for both required and preferred? Might be better to have "Requirements" for required, and "Preferred Qualifications" for preferred (though not in list but similar). The list includes "Qualifications". Could use "Qualifications" heading and then separate required vs preferred within? Might be okay. But we need to follow instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should pick from those examples. We have Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for Responsibilities, Requirements (required qualifications), Qualifications (maybe preferred?), Skills (maybe we can list technical skills). Benefits: we have statement about competitive benefits and compensation package, flexibility, link. Pay: we have compensation range $52-$78 per hour. Schedule: we have location hybrid, Eastern time zone hours, duration through Q1 2027 etc. That's schedule info.
Thus we can create sections:
- About the role (position summary)
- Responsibilities
- Requirements (required qualifications)
- Qualifications (preferred qualifications) maybe.
- Skills (maybe we can extract skills from required/preferred: SQL, ETL, data modeling, etc.) But we already have those in qualifications; maybe better to put skills separate? Could combine. But we need to avoid thin sections. If we put Skills, we need to list specific skills. Could extract: SQL, ETL/ELT tooling, dimensional/canonical data modeling, slowly changing, point-in-time, snapshot patterns, data quality controls, reconciliation, stakeholder management, Power BI, Azure/Databricks/Synapse/Fabric, etc. That's substantive.
- Benefits: we have paragraph about competitive benefits, flexibility, link.
- Pay: compensation range.
- Schedule: location hybrid, Eastern time zone, duration, onboarding timeline, etc.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, accommodation, etc. Also remove navigation, cookie, legal, EEO, scam-warning, application instructions. Also remove duplicated lines.
We need to preserve all substantive information. So we need to include details from the posting: company description, position summary, responsibilities list, required qualifications list, preferred qualifications list, technology stack maybe part of skills, engagement details (client, program, location, duration, etc.), additional requirements (background screening, third-party risk, prior engagement disclosure, start date flexibility), benefits statement, compensation range.
We must not invent or summarize away detail. So we need to keep specifics like "Build cycle-scoped acquisition and staging routines over client-provided extracts, with no transformation in the landing layer." etc.
We must not include boilerplate like "At RSM, we offer a competitive benefits and compensation package for all our people." That's actually substantive? It's a benefits statement; we can keep it but maybe it's generic. However it's part of benefits section. It's okay.
We must not include EEO statements, accommodation, etc.
We must not include "Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits." That's a link; maybe we can keep as part of benefits.
We must not include "All applicants will receive consideration for employment as RSM does not tolerate discrimination..." that's EEO boilerplate; remove.
We must not include "Accommodation for applicants with disabilities is available upon request..." remove.
We must not include "RSM is committed to providing equal opportunity..." remove.
We must not include "If you require a reasonable accommodation..." remove.
We must not include "RSM does not intend to hire entry level candidates..." remove.
We must not include "If you are a recent U.S. college..." remove.
We must not include "RSM will consider for employment qualified applicants with arrest or conviction records." remove.
We must not include "For those living in California..." remove.
We must not include "At RSM, an employee’s pay at any point..." that's about pay philosophy; maybe we can keep as part of Pay section? It's somewhat generic but still about pay. Could keep.
We must not include "As such, pay for the successful candidate(s) could fall anywhere within the stated range." That's part of pay.
We must not include "Compensation Range: $52 - $78 per hour" keep.
Now craft HTML.
Structure:
About the role
We are the leading provider of professional services to the middle market globally, our purpose is to instill confidence in a world of change, empowering our clients and people to realize their full potential. Our exceptional people are the key to our unrivaled, culture and talent experience and our ability to be compelling to our clients. You’ll find an environment that inspires and empowers you to thrive both personally and professionally. There’s no one like you and that’s why there’s nowhere like RSM. Position Summary RSM is seeking a Temporary Supervisor with 6+ years of experience in analytics and data engineering to support Risk Consulting engagements in the Financial Services and Global Banking sectors. This is a build role. Working under the pod's Senior Analytics Engineer, this individual constructs the foundation layers of a regulatory reporting analytics platform: cycle-scoped data acquisition, an immutable as-filed snapshot vault, the canonical data model, and the exception and data-gap findings store.
But note we should not repeat job title; we didn't.
Now Responsibilities:
Responsibilities
- Build cycle-scoped acquisition and staging routines over client-provided extracts, with no transformation in the landing layer.
- Build the as-filed snapshot vault - immutable and append-only, keyed on reporting cycle and record identifier - so that a prior cycle can be reproduced exactly as filed.
- Build the canonical data model together with its reference and product-to-classification mapping tables.
- Build the exception and data-gap findings store, including disposition state, so that each exception carries its rule version, its run, and the source records behind it.
- Implement the rule-run instrumentation and run logs that make each analytics cycle reproducible.
- Implement data quality controls, validation and reconciliation, including reconciliation of loaded data back to filed regulatory totals.
- Perform data analysis, validation, reconciliation, and issue remediation across complex data environments.
- Document data lineage and control evidence to the standard required for audit and regulatory review.
- Build supporting datasets for the Power BI reporting layer in partnership with the BI Engineer.
- Support risk, compliance, regulatory reporting, and audit-related data initiatives, and participate in SIT, UAT, documentation, implementation and production support activities.
Now Requirements (required qualifications):
Requirements
- 6+ years of hands-on experience in analytics engineering, data engineering, or data warehouse development.
- This role builds and maintains data structures; it is not a governance or business analysis role.
- Strong SQL, including complex transformation logic, performance tuning, and reconciliation queries.
- Experience with ETL/ELT tooling and data integration across multiple source systems.
- Experience with dimensional and canonical data modeling, including slowly changing and point-in-time or snapshot patterns.
- Experience working within Financial Services, Banking, Risk Management, Compliance, or Regulatory Reporting environments.
- Experience implementing data quality controls and reconciliation in a regulated environment.
- Strong communication and stakeholder management skills.
Now Qualifications (preferred):
Qualifications
- Knowledge of BCBS 239, regulatory reporting, risk data aggregation, or enterprise risk programs.
- Experience building immutable or append-only historical stores, and reconstructing prior reporting periods.
- Experience with data lineage and metadata documentation, and with tools such as Collibra.
- Working knowledge of Power BI as the consumption layer over a canonical model.
- Experience with Azure, Databricks, Synapse, Fabric, or other modern cloud analytics platforms.
Now Skills (maybe we can list technical skills from tech stack):
Skills
- SQL (complex transformation logic, performance tuning, reconciliation queries)
- ETL/ELT tooling and data integration across multiple source systems
- Dimensional and canonical data modeling (slowly changing, point-in-time, snapshot patterns)
- Data quality controls, validation, reconciliation
- Data lineage and metadata documentation (e.g., Collibra)
- Power BI (consumption layer over canonical model)
- Cloud analytics platforms: Azure, Databricks, Synapse, Fabric, Snowflake, Informatica, Talend, Alteryx, Teradata
- Stakeholder management and communication
Now Benefits:
Benefits
At RSM, we offer a competitive benefits and compensation package for all our people. We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients. Learn more about our total rewards at rsmus.com/careers/working-at-rsm/benefits.
Now Pay:
Pay
At RSM, an employee’s pay at any point in their career is intended to reflect their experiences, performance, and skills for their current role. The salary range (or starting rate for interns and associates) for this role represents numerous factors considered in the hiring decisions including, but not limited to, education, skills, work experience, certifications, location, etc. As such, pay for the successful candidate(s) could fall anywhere within the stated range. Compensation Range: $52 - $78 per hour.
Now Schedule:
Schedule
Engagement Details: Client: a large US bank. The role is embedded in the client's regulatory compliance function. Program: build-out of a regulatory reporting analytics capability - as-filed snapshot layer, canonical loan model, a rules and analytics engine, an exception store, and Power BI reporting. Location: hybrid, Charlotte NC or Atlanta GA. Onshore US only; Eastern time zone hours. No visa sponsorship and no offshore delivery on this engagement. Duration: through Q1 2027, with extension into Q2 2027 likely. Additional Requirements: Must be able to pass client background screening requirements. Must successfully complete all third-party risk on
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should pick from those examples. We have Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for Responsibilities, Requirements (required qualifications), Qualifications (maybe preferred?), Skills (maybe we can list technical skills). Benefits: we have statement about competitive benefits and compensation package, flexibility, link. Pay: we have compensation range $52-$78 per hour. Schedule: we have location hybrid, Eastern time zone hours, duration through Q1 2027 etc. That's schedule info.
Thus we can create sections:
- About the role (position summary)
- Responsibilities
- Requirements (required qualifications)
- Qualifications (preferred qualifications) maybe.
- Skills (maybe we can extract skills from required/preferred: SQL, ETL, data modeling, etc.) But we already have those in qualifications; maybe better to put skills separate? Could combine. But we need to avoid thin sections. If we put Skills, we need to list specific skills. Could extract: SQL, ETL/ELT tooling, dimensional/canonical data modeling, slowly changing, point-in-time, snapshot patterns, data quality controls, reconciliation, stakeholder management, Power BI, Azure/Databricks/Synapse/Fabric, etc. That's substantive.
- Benefits: we have paragraph about competitive benefits, flexibility, link.
- Pay: compensation range.
- Schedule: location hybrid, Eastern time zone, duration, onboarding timeline, etc.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, accommodation, etc. Also remove navigation, cookie, legal, EEO, scam-warning, application instructions. Also remove duplicated lines.
We need to preserve all substantive information. So we need to include details from the posting: company description, position summary, responsibilities list, required qualifications list, preferred qualifications list, technology stack maybe part of skills, engagement details (client, program, location, duration, etc.), additional requirements (background screening, third-party risk, prior engagement disclosure, start date flexibility), benefits statement, compensation range.
We must not invent or summarize away detail. So we need to keep specifics like "Build cycle-scoped acquisition and staging routines over client-provided extracts, with no transformation in the landing layer." etc.
We must not include boilerplate like "At RSM, we offer a competitive benefits and compensation package for all our people." That's actually substantive? It's a benefits statement; we can keep it but maybe it's generic. However it's part of benefits section. It's okay.
We must not include EEO statements, accommodation, etc.
We must not include "Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits." That's a link; maybe we can keep as part of benefits.
We must not include "All applicants will receive consideration for employment as RSM does not tolerate discrimination..." that's EEO boilerplate; remove.
We must not include "Accommodation for applicants with disabilities is available upon request..." remove.
We must not include "RSM is committed to providing equal opportunity..." remove.
We must not include "If you require a reasonable accommodation..." remove.
We must not include "RSM does not intend to hire entry level candidates..." remove.
We must not include "If you are a recent U.S. college..." remove.
We must not include "RSM will consider for employment qualified applicants with arrest or conviction records." remove.
We must not include "For those living in California..." remove.
We must not include "At RSM, an employee’s pay at any point..." that's about pay philosophy; maybe we can keep as part of Pay section? It's somewhat generic but still about pay. Could keep.
We must not include "As such, pay for the successful candidate(s) could fall anywhere within the stated range." That's part of pay.
We must not include "Compensation Range: $52 - $78 per hour" keep.
Now craft HTML.
Structure:
About the role
We are the leading provider of professional services to the middle market globally, our purpose is to instill confidence in a world of change, empowering our clients and people to realize their full potential. Our exceptional people are the key to our unrivaled, culture and talent experience and our ability to be compelling to our clients. You’ll find an environment that inspires and empowers you to thrive both personally and professionally. There’s no one like you and that’s why there’s nowhere like RSM. Position Summary RSM is seeking a Temporary Supervisor with 6+ years of experience in analytics and data engineering to support Risk Consulting engagements in the Financial Services and Global Banking sectors. This is a build role. Working under the pod's Senior Analytics Engineer, this individual constructs the foundation layers of a regulatory reporting analytics platform: cycle-scoped data acquisition, an immutable as-filed snapshot vault, the canonical data model, and the exception and data-gap findings store.
But note we should not repeat job title; we didn't. Now Responsibilities:Responsibilities
- Build cycle-scoped acquisition and staging routines over client-provided extracts, with no transformation in the landing layer.
- Build the as-filed snapshot vault - immutable and append-only, keyed on reporting cycle and record identifier - so that a prior cycle can be reproduced exactly as filed.
- Build the canonical data model together with its reference and product-to-classification mapping tables.
- Build the exception and data-gap findings store, including disposition state, so that each exception carries its rule version, its run, and the source records behind it.
- Implement the rule-run instrumentation and run logs that make each analytics cycle reproducible.
- Implement data quality controls, validation and reconciliation, including reconciliation of loaded data back to filed regulatory totals.
- Perform data analysis, validation, reconciliation, and issue remediation across complex data environments.
- Document data lineage and control evidence to the standard required for audit and regulatory review.
- Build supporting datasets for the Power BI reporting layer in partnership with the BI Engineer.
- Support risk, compliance, regulatory reporting, and audit-related data initiatives, and participate in SIT, UAT, documentation, implementation and production support activities.
Requirements
- 6+ years of hands-on experience in analytics engineering, data engineering, or data warehouse development.
- This role builds and maintains data structures; it is not a governance or business analysis role.
- Strong SQL, including complex transformation logic, performance tuning, and reconciliation queries.
- Experience with ETL/ELT tooling and data integration across multiple source systems.
- Experience with dimensional and canonical data modeling, including slowly changing and point-in-time or snapshot patterns.
- Experience working within Financial Services, Banking, Risk Management, Compliance, or Regulatory Reporting environments.
- Experience implementing data quality controls and reconciliation in a regulated environment.
- Strong communication and stakeholder management skills.
Qualifications
- Knowledge of BCBS 239, regulatory reporting, risk data aggregation, or enterprise risk programs.
- Experience building immutable or append-only historical stores, and reconstructing prior reporting periods.
- Experience with data lineage and metadata documentation, and with tools such as Collibra.
- Working knowledge of Power BI as the consumption layer over a canonical model.
- Experience with Azure, Databricks, Synapse, Fabric, or other modern cloud analytics platforms.
Skills
- SQL (complex transformation logic, performance tuning, reconciliation queries)
- ETL/ELT tooling and data integration across multiple source systems
- Dimensional and canonical data modeling (slowly changing, point-in-time, snapshot patterns)
- Data quality controls, validation, reconciliation
- Data lineage and metadata documentation (e.g., Collibra)
- Power BI (consumption layer over canonical model)
- Cloud analytics platforms: Azure, Databricks, Synapse, Fabric, Snowflake, Informatica, Talend, Alteryx, Teradata
- Stakeholder management and communication
Benefits
At RSM, we offer a competitive benefits and compensation package for all our people. We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients. Learn more about our total rewards at rsmus.com/careers/working-at-rsm/benefits.
Now Pay:Pay
At RSM, an employee’s pay at any point in their career is intended to reflect their experiences, performance, and skills for their current role. The salary range (or starting rate for interns and associates) for this role represents numerous factors considered in the hiring decisions including, but not limited to, education, skills, work experience, certifications, location, etc. As such, pay for the successful candidate(s) could fall anywhere within the stated range. Compensation Range: $52 - $78 per hour.
Now Schedule:Schedule
Engagement Details: Client: a large US bank. The role is embedded in the client's regulatory compliance function. Program: build-out of a regulatory reporting analytics capability - as-filed snapshot layer, canonical loan model, a rules and analytics engine, an exception store, and Power BI reporting. Location: hybrid, Charlotte NC or Atlanta GA. Onshore US only; Eastern time zone hours. No visa sponsorship and no offshore delivery on this engagement. Duration: through Q1 2027, with extension into Q2 2027 likely. Additional Requirements: Must be able to pass client background screening requirements. Must successfully complete all third-party risk on