Data Platform Administrator
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Job Summary (maybe About the role). Responsibilities (Job Responsibilities). Requirements / Qualifications (combined). There's also a list of specific technical skills etc. Could treat as Skills? But we can include Requirements/Qualifications as one section. Pay: they gave compensation range $80,930 – $101,162. So we can include Pay section. Schedule: they gave Work Schedule: Day, Full-Time. So we can include Schedule. Benefits: not mentioned. So skip Benefits. Skills: maybe we can include a Skills section summarizing technical skills? But we already have Requirements/Qualifications covering many specifics. The instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section. Could also have Skills separate if there is distinct list. However the posting includes many bullet-like responsibilities and requirements. We could have sections: About the role (Job Summary), Responsibilities, Requirements/Qualifications, Pay, Schedule. That seems sufficient. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like sponsorship note? The sponsorship note is "Please note Stater Bros. Markets is not able to consider candidates who will require visa sponsorship at the time of application or in the future." That's a minor metadata; we can fold into a short p or drop. Probably drop as it's not substantive? It's a condition but maybe we can include in a short p under About the role? The instruction: fold minor metadata into a short
or drop it. So we could include a short p about sponsorship. But we can also drop. Safer to include a short p. Also include location info? Address: 301 S Tippecanoe Avenue Location: San Bernardino, CA, US, 92408 Store Number: MAINOFFICE. That's minor metadata; could be a short p. Work Environment: 100% On-Site. Could be part of schedule or about role. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the responsibilities list exactly as given, but we can format as
- . Must not lose any bullet. The responsibilities list is long sentences separated by line breaks; we need to convert each line into a list item. Ensure we keep all content.
Similarly requirements/qualifications: we need to keep all bullet points.
We must not include application instructions, EEO, etc. The posting includes "Additional Information Applications will be received until a sufficient number of applications are received..." That's application instructions/boilerplate; we should drop.
Also "Join our team and make a difference..." that's boilerplate; drop.
Also "Learn More Nearest Major Market: San Bernardino Nearest Secondary Market: Los Angeles" drop.
We need to output only HTML fragment.
Let's craft:
About the role
Location: 301 S Tippecanoe Avenue, San Bernardino, CA 92408. Work Environment: 100% On‑Site. Work Schedule: Day, Full‑Time. Pay Type: Salaried. Union Position: Non‑Union. Department: Information Technology. Note: Stater Bros. Markets is not able to consider candidates who will require visa sponsorship at the time of application or in the future.
But we already have Pay and Schedule sections; maybe we should not duplicate. The instruction: include a section ONLY when posting has real specific content. Pay and Schedule we will have separate sections. So we can keep location and work environment in About the role. Thus About the role: include Job Summary paragraph. Job Summary: The Data Platform [Azure & SQL] Administrator has hands-on experience supporting and administering SQL Server, Microsoft Azure data services, Microsoft Fabric, Azure Synapse Analytics, Azure SQL Database, Azure Storage, data pipelines, and Power BI environments. The ideal candidate will have an understanding of Azure data-platform architecture and MS SQL database administration and will be responsible for platform support, monitoring, troubleshooting, deployments, access management, and day-to-day operational activities across development, QA, and production environments. Responsibilities include monitoring and managing Azure cost and consumption, including budgets, alerts, tagging, rightsizing, and support for chargeback/showback reporting. This is primarily a platform administration, database administration, and technical support role (not a software development position). The candidate should have an admin mindset and be comfortable working with development, infrastructure, security, and business teams. We'll put that in. Then Responsibilities:
Responsibilities
- ... each line. We need to split each responsibility line. Let's extract lines from the responsibilities block: "Administer and support on-premises MS SQL Database, Azure data-platform resources across development, QA, and production environments" "Administer and support on-premises SQL databases, including database configuration, installation, upgrade, migration, security, performance, availability, and troubleshooting" "Provide support for Microsoft Fabric, Azure Synapse Analytics, Azure SQL Database, Azure Storage, and related services" "Monitor database health, performance, storage utilization, connectivity, and availability" "Troubleshoot SQL database issues including blocking, deadlocks, failed jobs, connectivity issues, permissions, and performance degradation" "Support database backup, restore, recovery, and disaster-recovery processes" "Assist with database upgrades, migrations, patching, and environment refreshes" "Manage database users, logins, roles, permissions, and access using appropriate security practices" "Support data pipeline deployments and troubleshoot failed pipeline executions" "Deploy and manage data pipelines and related resources across environments using established deployment processes" "Support Microsoft Fabric workspaces, pipelines, lakehouses, and related data-platform components" "Support Azure Synapse Analytics environments and troubleshoot common connectivity, pipeline, and resource issues" "Manage and troubleshoot Azure Storage and Blob Storage resources" "Work with Parquet files and understand common data-lake storage concepts" "Manage Azure Resource Groups, subscriptions, resources, and environment configurations" "Support Azure RBAC and AD roles and permissions / Microsoft Entra ID" "Support Power BI workspaces, datasets/semantic models, refreshes, gateways, permissions, and connectivity" "Monitor Azure resources and investigate alerts and operational issues" "Work with development teams to support application and database deployments without being responsible for application development" "Participate in production incident resolution and root-cause analysis" "Follow established change-management, security, release, and production-support processes" "Maintain technical documentation, operational procedures, and troubleshooting guides" "Serve as a technical point of contact for Azure data-platform and database-related issues" "Any other duties assigned by leadership" We'll put each as
- .
Then Requirements/Qualifications: combine.
We need to extract requirements list:
"High school diploma or GED required."
"Associate’s or Bachelor’s degree in Computer Science, Information Technology, or a related field preferred (equivalent combination of education and hands-on experience will be considered in lieu of a formal degree)"
"Minimum of 2 years of hands-on experience in database administration, database development, or a related technical support role"
"Microsoft Certified: Azure Administrator Associate (or equivalent cloud platform certification) is a plus"
Then sub-sections: SQL Database Administration (list), Azure & Microsoft Fabric Technologies, Azure Storage & Data Concepts, Power BI, Security & Azure Governance, Required Soft Skills & Operational Mindset.
We need to keep all bullet points under each subheading as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should flatten all requirements into a list? Or we could keep subheadings as
? But we only allowed headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We cannot add extra headings like "SQL Database Administration". So we need to incorporate those details into the Requirements/Qualifications section as list items, preserving the detail. We can keep the subheadings as plain text inside
- maybe? But that would lose structure. Better to keep them as part of the list items, maybe using
- SQL Database Administration: ... . That preserves detail. Thus we will create a
- . We'll need to break down each bullet. Let's list all requirement statements: - High school diploma or GED required. - Associate’s or Bachelor’s degree in Computer Science, Information Technology, or a related field preferred (equivalent combination of education and hands-on experience will be considered in lieu of a formal degree) - Minimum of 2 years of hands-on experience in database administration, database development, or a related technical support role - Microsoft Certified: Azure Administrator Associate (or equivalent cloud platform certification) is a plus Then under SQL Database Administration: - Strong knowledge of Microsoft SQL Server and Azure SQL Database administration, operational support, architecture, configuration, and maintenance - Hands-on experience with database installation, upgrades, migrations between environments, and environment refreshes - Experience managing databases, schemas, tables, indexes, database objects, logins, users, roles, and permissions using proper SQL Server authentication and Azure SQL authentication/authorization - Demonstrated ability to monitor database performance, troubleshoot connectivity issues, and manage execution plans, indexing, statistics, blocking, and deadlocks - Knowledge of SQL Server Agent jobs, scheduled database processes, backup/restore procedures, recovery models, point-in-time recovery, and high availability/disaster recovery (HA/DR) concepts - Working knowledge of T-SQL and ability to assist development teams with deployment, release activities, and basic query performance reviews (Note: Not a SQL developer role) Azure & Microsoft Fabric Technologies: - Strong working knowledge of Microsoft Azure and modern cloud data-platform technologies across Dev, QA, and Production environments - Hands-on experience supporting Microsoft Fabric (workspaces, capacities, lakehouses, pipelines, data resources) - Practical experience supporting Azure Synapse Analytics (workspaces, SQL pools, pipelines) - Experience deploying, monitoring, and troubleshooting data pipelines using Azure Data Factory (ADF) or similar tools (triggers, parameters, linked services, datasets) Azure Storage & Data Concepts: - Experience managing Azure Storage Accounts, Blob Storage, containers, access controls, and storage permissions - Familiarity with data-lake concepts, Parquet files, and common data formats - Ability to troubleshoot storage connectivity and access issues across integrated services (Synapse, Fabric, Power BI, data pipelines) - Experience with Azure resource monitoring, alerting, and incident management Power BI, Security & Azure Governance: - Working knowledge of Power BI administration and support, including workspaces, permissions, datasets/semantic models, refreshes, gateways, and connectivity troubleshooting (Note: Report development is not a primary duty) - Experience managing Azure subscriptions, Resource Groups, Azure RBAC roles (Reader, Contributor, Owner), managed identities, and service principals Required Soft Skills & Operational Mindset: - Strong troubleshooting, problem-solving, and diagnostic skills in production-support environments - Ability to collaborate effectively in an IT team environment (Development, Infrastructure, DBAs, Data team) - Strong communication, collaboration, and technical documentation skills - Ability to evaluate the entire Azure data environment and understand how components interoperate, focusing on administering, monitoring, and troubleshooting rather than building solutions from scratch We'll include all as
- .
Pay section:
Pay
$80,930.00 – $101,162.00 (this represents the expected pay range for this job requisition. Ultimately, in determining your pay, we'll consider your experience and other job-related factors)
Schedule section:Schedule
Work Schedule: Day. Job Type: Full-Time. Work Environment: 100% On‑Site.
We might also include note about sponsorship in About the role or as a short p. We'll add a short p after About the role maybe. But we already have About the role
- with each requirement as
- for any list of duties/requirements/benefits. So we should flatten all requirements into a list? Or we could keep subheadings as