Enterprise Data & BI Architect II
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to extract content:
- About the role: The first paragraph(s) describing the division and opportunity. "Analytics & Integrated Planning The Analytics and Integrated Planning (AIP) division brings expertise... The Opportunity UCF’s Analytics & Integrated Planning (AIP) team is hiring an Enterprise Data & BI Architect II to design the data and analytics in support of the Office of Research Vienna Project. This position is responsible for designing, developing, and supporting enterprise analytics and data engineering solutions that enable institutional and departmental reporting, analysis, and decision‑making across the university. This is a visiting and renewable position. Visiting positions are based on circumstances, such as funding sources, which control the length of time for which the position is available. Visiting positions are renewable for up to four years. This project is estimated to last two years."
That's about the role. We'll put under
About the role
with paragraphs.
- Responsibilities: list of bullet points under headings: Data Engineering and Analytics Development, Platform Support And Standards Adherence, Performance Optimization And Troubleshooting, Data Quality And Compliance, Business Collaboration And Solution Delivery, Documentation And Project Support. Each has sub-bullets. We'll create a
- for each main responsibility, maybe with nested
for subpoints. But spec says use - for any list of duties/requirements/benefits. Could nest but still okay. We'll produce top-level
with each responsibility as - containing the description and possibly nested
.
- Minimum Qualifications: "Bachelor's or Master's degree and 2+ years of relevant experience; or an equivalent combination of education and experience pursuant to Fla. Stat. 112.219(6)." That's a qualification. We'll put under Minimum Qualifications
with .
- Preferred Qualifications: list of items: "2+ years of experience as a data architect or data engineer, preferably within enterprise cloud environments. Experience with modern cloud data platforms, especially Microsoft Azure, AWS, or other enterprise cloud environments. Hands‑on experience with Microsoft Fabric and/or Power BI in an enterprise analytics environment; Fabric experience is strongly preferred. Strong command of SQL, Python/PySpark, and DAX for querying, modeling, and validating complex datasets. Demonstrated experience designing and delivering data analytics or BI solutions, including data pipelines, semantic models, and dimensional data structures. Experience working in higher education is highly desirable. Certifications: Microsoft Certified: Fabric Analytics Engineer Associate (DP-700)." We'll put under
Preferred Qualifications
with - .
- The Most Successful Candidates May Possess The Following Qualities: list of qualities: "Excellent communicator with the ability to collaborate effectively with technical and non‑technical stakeholders, including consultants and internal partners. Proactive, self‑directed contributor who can take initiative in a fast‑moving project environment. Strong attention to detail and accuracy, with the ability to validate complex datasets and ensure high‑quality, consistent outputs across analytics and documentation." Could be under
Skills
or maybe "Qualities". The spec says we can use Skills section. We'll put under Skills
with - .
- Additional Application Materials Required: "In addition to your applications, please provide your most up-to-date resume." That's application instruction; we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we drop that.
- Special Instructions To The Applicants: includes visa sponsorship not available, salary range, etc. Salary range is substantive: "The anticipated salary range for this position is $87,500-$95,000. The final salary will be determined based on the candidate's qualifications, experience, and internal equity considerations." Also repeated visiting position info (duplicate). We'll keep salary info under Pay section. Also we have "Expected Salary $75,809.00 to Negotiable" earlier but that seems contradictory; but we should preserve all substantive info. There's also "Expected Salary $75,809.00 to Negotiable". That's also salary info. We need to include both? The rule: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include both salary mentions. However we should avoid duplication? The duplicated lines rule says remove duplicated lines. The salary lines are not exactly duplicate; one is anticipated salary range $87,500-$95,000, another is Expected Salary $75,809.00 to Negotiable. Both are substantive. We'll include both maybe in Pay section.
- Work Schedule: "Department Analytics & Integrated Planning Work Schedule Monday - Friday 8:00AM - 5:00PM". That's schedule. So we create Schedule section.
- Benefits: "UCF offers: Benefit packages, including Medical, Dental, Vision, Life Insurance, Flexible Spending, and Employee Assistance Program Paid time off, including annual and sick time off and paid holidays Retirement savings options Employee discounts, including tickets to many Orlando attractions Education assistance And more…". That's benefits. We'll create Benefits section with
- list.
- Also there is line: "Unless explicitly stated on the job posting, it is UCF’s expectation that an employee of UCF will reside in Florida as of the date the employment begins." That's maybe not a section; could be included in About the role or maybe as a note. It's substantive. We'll include in About the role paragraph.
- Also there is "Type of Appointment Fixed Term (Fixed Term)" maybe not needed.
- "Job Posting End Date 09-28-2026-12-00-AM" maybe not needed; it's metadata; we can drop as minor metadata.
- Also "The University of Central Florida is an equal opportunity employer..." that's EEO boilerplate; remove.
- Also "UCF is proud to be a smoke-free campus and an E-Verify employer." remove.
- Also contact emails: remove as application instructions.
Now construct HTML.
We'll have sections: About the role, Responsibilities, Minimum Qualifications, Preferred Qualifications, Skills, Benefits, Pay, Schedule.
Check each for real content.
About the role: we have paragraphs.
Responsibilities: we have bullet points.
Minimum Qualifications: we have.
Preferred Qualifications: we have.
Skills: we have qualities.
Benefits: we have.
Pay: we have salary range and expected salary.
Schedule: we have work schedule.
We should not include sections that are empty or filler.
Now produce HTML.
We need to use
for section headings. Use - for lists. Use
for prose.
We'll need to ensure we don't include any markdown fences.
Let's craft.
About the role: maybe two paragraphs: first describing division and opportunity, second about visiting position and project length and Florida residence expectation.
We'll combine.
Responsibilities: We'll create a
with each main responsibility as - . Inside each
- we can have a heading? Not required but we can keep plain text. We'll include subpoints as nested
.
Let's list responsibilities:
1. Data Engineering and Analytics Development:
- Designs, develops, and implements scalable data pipelines and analytics solutions using Microsoft Azure and Microsoft Fabric platforms.
- Builds, optimizes, and maintains data models utilizing relational, dimensional, and star schemas to support reporting, analytics, and semantic layers.
- Develops and optimizes SQL queries and transformation logic to support ETL and ELT processes across multiple data sources.
2. Platform Support And Standards Adherence:
- Supports and maintains Microsoft Fabric environments, including workspace organization, access configurations, and deployment practices across development, test, and production environments.
- Implements and follows established analytics standards, development best practices, and architectural guidelines to ensure consistency and maintainability.
- Works closely with architects and other engineers to align solutions with institutional platform standards.
3. Performance Optimization And Troubleshooting:
- Monitors and tunes performance of data pipelines, models, and analytics workloads to ensure reliability and efficiency.
- Troubleshoots and resolves data pipeline failures, data model issues, and integration problems to maintain platform stability and data reliability.
- Provides data‑related technical support and troubleshooting for user‑reported issues.
4. Data Quality And Compliance:
- Performs data profiling, validation, and data quality assessments to ensure accuracy, consistency, and adherence to business rules and compliance with UCF data policies.
- Supports performance tuning, metadata management, data lineage, data security, and governance controls across analytics platforms.
- Contributes to metadata documentation, data lineage artifacts, and governance.
5. Business Collaboration And Solution Delivery:
- Collaborates with business stakeholders to gather, define, document, and refine requirements for analytics and business intelligence solutions.
- Translates business requirements into technical data solutions, including semantic models and reporting datasets.
- Develops and executes testing strategies and validation criteria to ensure data accuracy and functional correctness of deliverables.
6. Documentation And Project Support:
- Supports analytics projects through task estimation, development activities, and milestone tracking.
- Creates and maintains technical documentation, including data flow diagrams, transformation logic, and operational runbooks.
Now Minimum Qualifications: "Bachelor's or Master's degree and 2+ years of relevant experience; or an equivalent combination of education and experience pursuant to Fla. Stat. 112.219(6)."
Preferred Qualifications list:
- 2+ years of experience as a data architect or data engineer, preferably within enterprise cloud environments.
- Experience with modern cloud data platforms, especially Microsoft Azure, AWS, or other enterprise cloud environments.
- Hands‑on experience with Microsoft Fabric and/or Power BI in an enterprise analytics environment; Fabric experience is strongly preferred.
- Strong command of SQL, Python/PySpark, and DAX for querying, modeling, and validating complex datasets.
- Demonstrated experience designing and delivering data analytics or BI solutions, including data pipelines, semantic models, and dimensional data structures.
- Experience working in higher education is highly desirable.
- Certifications: Microsoft Certified: Fabric Analytics Engineer Associate (DP-700).
Skills (qualities):
- Excellent communicator with the ability to collaborate effectively with technical and non‑technical stakeholders, including consultants and internal partners.
- Proactive, self‑directed contributor who can take initiative in a fast‑moving project environment.
- Strong attention to detail and accuracy, with the ability to validate complex datasets and ensure high‑quality, consistent outputs across analytics and documentation.
Benefits list:
- Benefit packages, including Medical, Dental, Vision, Life Insurance, Flexible Spending, and Employee Assistance Program
- Paid time off, including annual and sick time off and paid holidays
- Retirement savings options
- Employee discounts, including tickets to many Orlando attractions
- Education assistance
We could also include "And more…" but that's vague; maybe omit as filler.
Pay: include both salary statements:
- The anticipated salary range for this position is $87,500-$95,000. The final salary will be determined based on
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Never create Pay/Schedule/Benefits sections unless posting actually states them. We need to extract content: - About the role: The first paragraph(s) describing the division and opportunity. "Analytics & Integrated Planning The Analytics and Integrated Planning (AIP) division brings expertise... The Opportunity UCF’s Analytics & Integrated Planning (AIP) team is hiring an Enterprise Data & BI Architect II to design the data and analytics in support of the Office of Research Vienna Project. This position is responsible for designing, developing, and supporting enterprise analytics and data engineering solutions that enable institutional and departmental reporting, analysis, and decision‑making across the university. This is a visiting and renewable position. Visiting positions are based on circumstances, such as funding sources, which control the length of time for which the position is available. Visiting positions are renewable for up to four years. This project is estimated to last two years." That's about the role. We'll put under
About the role
withparagraphs. - Responsibilities: list of bullet points under headings: Data Engineering and Analytics Development, Platform Support And Standards Adherence, Performance Optimization And Troubleshooting, Data Quality And Compliance, Business Collaboration And Solution Delivery, Documentation And Project Support. Each has sub-bullets. We'll create a
- for each main responsibility, maybe with nested
- for subpoints. But spec says use
- for any list of duties/requirements/benefits. Could nest but still okay. We'll produce top-level
- with each responsibility as
- containing the description and possibly nested
- .
- Minimum Qualifications: "Bachelor's or Master's degree and 2+ years of relevant experience; or an equivalent combination of education and experience pursuant to Fla. Stat. 112.219(6)." That's a qualification. We'll put under
- .
- The Most Successful Candidates May Possess The Following Qualities: list of qualities: "Excellent communicator with the ability to collaborate effectively with technical and non‑technical stakeholders, including consultants and internal partners. Proactive, self‑directed contributor who can take initiative in a fast‑moving project environment. Strong attention to detail and accuracy, with the ability to validate complex datasets and ensure high‑quality, consistent outputs across analytics and documentation." Could be under
Skills
or maybe "Qualities". The spec says we can use Skills section. We'll put underSkills
with- .
- Additional Application Materials Required: "In addition to your applications, please provide your most up-to-date resume." That's application instruction; we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we drop that.
- Special Instructions To The Applicants: includes visa sponsorship not available, salary range, etc. Salary range is substantive: "The anticipated salary range for this position is $87,500-$95,000. The final salary will be determined based on the candidate's qualifications, experience, and internal equity considerations." Also repeated visiting position info (duplicate). We'll keep salary info under Pay section. Also we have "Expected Salary $75,809.00 to Negotiable" earlier but that seems contradictory; but we should preserve all substantive info. There's also "Expected Salary $75,809.00 to Negotiable". That's also salary info. We need to include both? The rule: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include both salary mentions. However we should avoid duplication? The duplicated lines rule says remove duplicated lines. The salary lines are not exactly duplicate; one is anticipated salary range $87,500-$95,000, another is Expected Salary $75,809.00 to Negotiable. Both are substantive. We'll include both maybe in Pay section.
- Work Schedule: "Department Analytics & Integrated Planning Work Schedule Monday - Friday 8:00AM - 5:00PM". That's schedule. So we create Schedule section.
- Benefits: "UCF offers: Benefit packages, including Medical, Dental, Vision, Life Insurance, Flexible Spending, and Employee Assistance Program Paid time off, including annual and sick time off and paid holidays Retirement savings options Employee discounts, including tickets to many Orlando attractions Education assistance And more…". That's benefits. We'll create Benefits section with
- list.
- Also there is line: "Unless explicitly stated on the job posting, it is UCF’s expectation that an employee of UCF will reside in Florida as of the date the employment begins." That's maybe not a section; could be included in About the role or maybe as a note. It's substantive. We'll include in About the role paragraph.
- Also there is "Type of Appointment Fixed Term (Fixed Term)" maybe not needed.
- "Job Posting End Date 09-28-2026-12-00-AM" maybe not needed; it's metadata; we can drop as minor metadata.
- Also "The University of Central Florida is an equal opportunity employer..." that's EEO boilerplate; remove.
- Also "UCF is proud to be a smoke-free campus and an E-Verify employer." remove.
- Also contact emails: remove as application instructions.
Now construct HTML.
We'll have sections: About the role, Responsibilities, Minimum Qualifications, Preferred Qualifications, Skills, Benefits, Pay, Schedule.
Check each for real content.
About the role: we have paragraphs.
Responsibilities: we have bullet points.
Minimum Qualifications: we have.
Preferred Qualifications: we have.
Skills: we have qualities.
Benefits: we have.
Pay: we have salary range and expected salary.
Schedule: we have work schedule.
We should not include sections that are empty or filler.
Now produce HTML.
We need to use
for section headings. Use
- for lists. Use
for prose. We'll need to ensure we don't include any markdown fences. Let's craft. About the role: maybe two paragraphs: first describing division and opportunity, second about visiting position and project length and Florida residence expectation. We'll combine. Responsibilities: We'll create a
- with each main responsibility as
- . Inside each
- we can have a heading? Not required but we can keep plain text. We'll include subpoints as nested
- .
Let's list responsibilities:
1. Data Engineering and Analytics Development:
- Designs, develops, and implements scalable data pipelines and analytics solutions using Microsoft Azure and Microsoft Fabric platforms.
- Builds, optimizes, and maintains data models utilizing relational, dimensional, and star schemas to support reporting, analytics, and semantic layers.
- Develops and optimizes SQL queries and transformation logic to support ETL and ELT processes across multiple data sources.
2. Platform Support And Standards Adherence:
- Supports and maintains Microsoft Fabric environments, including workspace organization, access configurations, and deployment practices across development, test, and production environments.
- Implements and follows established analytics standards, development best practices, and architectural guidelines to ensure consistency and maintainability.
- Works closely with architects and other engineers to align solutions with institutional platform standards.
3. Performance Optimization And Troubleshooting:
- Monitors and tunes performance of data pipelines, models, and analytics workloads to ensure reliability and efficiency.
- Troubleshoots and resolves data pipeline failures, data model issues, and integration problems to maintain platform stability and data reliability.
- Provides data‑related technical support and troubleshooting for user‑reported issues.
4. Data Quality And Compliance:
- Performs data profiling, validation, and data quality assessments to ensure accuracy, consistency, and adherence to business rules and compliance with UCF data policies.
- Supports performance tuning, metadata management, data lineage, data security, and governance controls across analytics platforms.
- Contributes to metadata documentation, data lineage artifacts, and governance.
5. Business Collaboration And Solution Delivery:
- Collaborates with business stakeholders to gather, define, document, and refine requirements for analytics and business intelligence solutions.
- Translates business requirements into technical data solutions, including semantic models and reporting datasets.
- Develops and executes testing strategies and validation criteria to ensure data accuracy and functional correctness of deliverables.
6. Documentation And Project Support:
- Supports analytics projects through task estimation, development activities, and milestone tracking.
- Creates and maintains technical documentation, including data flow diagrams, transformation logic, and operational runbooks.
Now Minimum Qualifications: "Bachelor's or Master's degree and 2+ years of relevant experience; or an equivalent combination of education and experience pursuant to Fla. Stat. 112.219(6)."
Preferred Qualifications list:
- 2+ years of experience as a data architect or data engineer, preferably within enterprise cloud environments.
- Experience with modern cloud data platforms, especially Microsoft Azure, AWS, or other enterprise cloud environments.
- Hands‑on experience with Microsoft Fabric and/or Power BI in an enterprise analytics environment; Fabric experience is strongly preferred.
- Strong command of SQL, Python/PySpark, and DAX for querying, modeling, and validating complex datasets.
- Demonstrated experience designing and delivering data analytics or BI solutions, including data pipelines, semantic models, and dimensional data structures.
- Experience working in higher education is highly desirable.
- Certifications: Microsoft Certified: Fabric Analytics Engineer Associate (DP-700).
Skills (qualities):
- Excellent communicator with the ability to collaborate effectively with technical and non‑technical stakeholders, including consultants and internal partners.
- Proactive, self‑directed contributor who can take initiative in a fast‑moving project environment.
- Strong attention to detail and accuracy, with the ability to validate complex datasets and ensure high‑quality, consistent outputs across analytics and documentation.
Benefits list:
- Benefit packages, including Medical, Dental, Vision, Life Insurance, Flexible Spending, and Employee Assistance Program
- Paid time off, including annual and sick time off and paid holidays
- Retirement savings options
- Employee discounts, including tickets to many Orlando attractions
- Education assistance
We could also include "And more…" but that's vague; maybe omit as filler.
Pay: include both salary statements:
- The anticipated salary range for this position is $87,500-$95,000. The final salary will be determined based on
- for lists. Use
- list.
- Also there is line: "Unless explicitly stated on the job posting, it is UCF’s expectation that an employee of UCF will reside in Florida as of the date the employment begins." That's maybe not a section; could be included in About the role or maybe as a note. It's substantive. We'll include in About the role paragraph.
- Also there is "Type of Appointment Fixed Term (Fixed Term)" maybe not needed.
- "Job Posting End Date 09-28-2026-12-00-AM" maybe not needed; it's metadata; we can drop as minor metadata.
- Also "The University of Central Florida is an equal opportunity employer..." that's EEO boilerplate; remove.
- Also "UCF is proud to be a smoke-free campus and an E-Verify employer." remove.
- Also contact emails: remove as application instructions.
Now construct HTML.
We'll have sections: About the role, Responsibilities, Minimum Qualifications, Preferred Qualifications, Skills, Benefits, Pay, Schedule.
Check each for real content.
About the role: we have paragraphs.
Responsibilities: we have bullet points.
Minimum Qualifications: we have.
Preferred Qualifications: we have.
Skills: we have qualities.
Benefits: we have.
Pay: we have salary range and expected salary.
Schedule: we have work schedule.
We should not include sections that are empty or filler.
Now produce HTML.
We need to use
- .
- Additional Application Materials Required: "In addition to your applications, please provide your most up-to-date resume." That's application instruction; we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we drop that.
- Special Instructions To The Applicants: includes visa sponsorship not available, salary range, etc. Salary range is substantive: "The anticipated salary range for this position is $87,500-$95,000. The final salary will be determined based on the candidate's qualifications, experience, and internal equity considerations." Also repeated visiting position info (duplicate). We'll keep salary info under Pay section. Also we have "Expected Salary $75,809.00 to Negotiable" earlier but that seems contradictory; but we should preserve all substantive info. There's also "Expected Salary $75,809.00 to Negotiable". That's also salary info. We need to include both? The rule: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include both salary mentions. However we should avoid duplication? The duplicated lines rule says remove duplicated lines. The salary lines are not exactly duplicate; one is anticipated salary range $87,500-$95,000, another is Expected Salary $75,809.00 to Negotiable. Both are substantive. We'll include both maybe in Pay section.
- Work Schedule: "Department Analytics & Integrated Planning Work Schedule Monday - Friday 8:00AM - 5:00PM". That's schedule. So we create Schedule section.
- Benefits: "UCF offers: Benefit packages, including Medical, Dental, Vision, Life Insurance, Flexible Spending, and Employee Assistance Program Paid time off, including annual and sick time off and paid holidays Retirement savings options Employee discounts, including tickets to many Orlando attractions Education assistance And more…". That's benefits. We'll create Benefits section with
Minimum Qualifications
with. - Preferred Qualifications: list of items: "2+ years of experience as a data architect or data engineer, preferably within enterprise cloud environments. Experience with modern cloud data platforms, especially Microsoft Azure, AWS, or other enterprise cloud environments. Hands‑on experience with Microsoft Fabric and/or Power BI in an enterprise analytics environment; Fabric experience is strongly preferred. Strong command of SQL, Python/PySpark, and DAX for querying, modeling, and validating complex datasets. Demonstrated experience designing and delivering data analytics or BI solutions, including data pipelines, semantic models, and dimensional data structures. Experience working in higher education is highly desirable. Certifications: Microsoft Certified: Fabric Analytics Engineer Associate (DP-700)." We'll put under
Preferred Qualifications
with - .
- The Most Successful Candidates May Possess The Following Qualities: list of qualities: "Excellent communicator with the ability to collaborate effectively with technical and non‑technical stakeholders, including consultants and internal partners. Proactive, self‑directed contributor who can take initiative in a fast‑moving project environment. Strong attention to detail and accuracy, with the ability to validate complex datasets and ensure high‑quality, consistent outputs across analytics and documentation." Could be under
- containing the description and possibly nested
- for any list of duties/requirements/benefits. Could nest but still okay. We'll produce top-level