SQL DBA II
Versant Media · Orlando, FL · 3 wk ago
RemoteRemoteEngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually job description includes "Company Description", "Job Description", "Why This Role Matters", "Qualifications", "What You’ll Do", "What You Bring", "How We Do It", "Bonus Points", "Why You’ll Love It Here", "Additional Information". We must use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should only include sections when posting has real specific content. We need to map content to these headings.
We have:
- Company Description: could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Job Description" which includes responsibilities. Could map to "Responsibilities". Also "Qualifications" heading matches.
- "What You’ll Do" is responsibilities.
- "What You Bring" is qualifications/requirements.
- "How We Do It" maybe "Skills"? Actually it's values/trust etc. Could be omitted if not specific? It's more about culture; maybe we can include as "Skills"? But it's not skill list; it's values. Might be considered boilerplate? It's not required but could be included as "Skills"? However instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "How We Do It" section lists Trust, Teamwork, Transparency, Agility, Entrepreneurial Spirit. That's specific content (values). Could be considered "Skills"? But maybe better to treat as "Skills" heading? However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: maybe company description + why role matters? Could combine.
- Responsibilities: "What You’ll Do" list.
- Requirements: "What You Bring" list (experience, education).
- Qualifications: maybe same as Requirements? But we shouldn't duplicate. Could treat "Qualifications" as the list of qualifications (education, experience). But we already have Requirements. Might combine.
Better: Use sections: About the role (company description + why role matters), Responsibilities (What You’ll Do), Requirements (What You Bring), Skills (maybe technical skills list from qualifications?), Benefits (maybe not present), Pay (not present), Schedule (remote Florida-based, 10% in-person). Actually schedule info is present: remote role based in Florida, primarily remote, expect in-person collaboration approx 10% of time. That's schedule info. So we can include Schedule section.
Benefits: Not explicitly listed; there is mention of compensation and benefits in Additional Information: "Actual compensation will be based on factors... and may include additional forms of compensation and benefits such as health insurance, retirement plans, paid time off, etc." That's vague but mentions benefits. However it's not specific; it's generic. Might be considered filler? It says "may include additional forms of compensation and benefits such as health insurance, retirement plans, paid time off, etc." That's somewhat specific but still generic. Could we include Benefits section with that? It's not a list of specific benefits; it's a statement. Might be considered filler? The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is not exactly those, but it's vague. Might be okay to include? Safer to omit Benefits if not concrete.
Pay: There's mention of "good faith pay range for each position" but not actual numbers. So no specific pay. So omit Pay.
Thus sections: About the role, Responsibilities, Requirements, Skills (maybe technical skills), Schedule.
But we need to avoid duplication. Let's extract content.
Company Description: "VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business and home to trusted brands that shape culture, inform audiences, and build lasting connections. It operates across four core markets: political news and opinion, business news and personal finance, golf, and sports and genre entertainment. These markets are served through a powerful portfolio of iconic and innovative brands, including CNBC, MS NOW, USA Network, Golf Channel, Oxygen, E!, SYFY, and Versant's sports division USA Sports, along with complementary digital assets including Fandango, Rotten Tomatoes, GolfNow and GolfPass."
Why This Role Matters: "Our database platforms support critical applications and workflows across Versant. Your work will directly contribute to the stability, scalability, security, and recoverability of the systems our teams rely on to operate effectively."
Combine these into About the role.
Responsibilities: "What You’ll Do" bullet list (actually sentences). Let's extract each sentence as list item.
- Own the health and reliability of SQL Server environments across Production, Staging, and Development, including SQL Server hosted on AWS RDS, maintaining availability in accordance with established SLAs, SLOs, RTOs, and RPOs.
- Support and administer additional relational database platforms, including MySQL and PostgreSQL, as needed across cloud and on-premises environments, applying consistent standards for reliability, security, performance, backup, and recovery.
- Monitor and optimize database performance and capacity using execution plans, Query Store, wait statistics, Extended Events, indexing analysis, observability platforms, and other diagnostic tools to proactively identify and resolve issues.
- Strengthen database security and resilience by administering access and permissions using least-privilege practices and designing, implementing, testing, and validating backup, restore, high-availability, and disaster-recovery strategies.
- Partner with engineering teams throughout the development lifecycle to improve T-SQL, query and schema design, indexing, CI/CD workflows, automated deployments, data migrations, integrations, and post-deployment validation.
- Automate repeatable database operations and improve production support using infrastructure-as-code, PowerShell, and other scripting technologies while enhancing monitoring, alerting, dashboards, incident response, root-cause analysis, and technical documentation.
Requirements: "What You Bring" list.
- 5+ years of hands-on SQL Server transactional database administration experience, including production database environments.
- Strong SQL Server administration expertise across configuration, security, permissions, maintenance, backups, restores, troubleshooting, and operational support.
- Strong experience with AWS database and infrastructure services, particularly RDS, Secrets Manager, S3, CloudWatch, and related technologies.
- Advanced SQL Server performance analysis and optimization capabilities, including execution plans, Query Store, index design, wait statistics, blocking analysis, query tuning, Extended Events, and related diagnostic technologies.
- Strong knowledge of SQL Server concurrency and transaction behavior, including isolation levels, locking, blocking, and deadlocks.
- Experience designing and supporting high-availability and disaster-recovery solutions, including Always On Availability Groups, backup and restore strategies, and RTO/RPO planning.
- Strong proficiency in T-SQL and PowerShell, with experience using automation to improve database administration and operational workflows.
- Working knowledge of MySQL and PostgreSQL administration, including configuration, monitoring, security, backup and restore, and troubleshooting in production environments.
- Experience with source control and database CI/CD practices using Git, GitHub, GitHub Actions, or equivalent technologies.
- Experience with monitoring and observability platforms such as Datadog, Prometheus, CloudWatch, or equivalent.
- Demonstrated ability to independently troubleshoot complex production database issues, perform root-cause analysis, manage assigned work, communicate risks and blockers, and escalate appropriately.
- An associate’s degree in Computer Science, Information Technology, a related field, or equivalent professional experience.
Skills: Could be derived from "How We Do It" (Trust, Teamwork, Transparency, Agility, Entrepreneurial Spirit) but those are values not skills. Maybe we can treat "Bonus Points" as skills? Bonus Points list:
- Experience with Python or Bash.
- Experience with MySQL or PostgreSQL in AWS-managed services such as Amazon RDS or Aurora.
- Experience operating and optimizing heterogeneous database environments that include SQL Server, MySQL, and PostgreSQL.
- Experience building infrastructure-as-code or other repeatable database provisioning and configuration workflows.
- Experience supporting data integration, migration, or replication across systems and environments.
These are additional skills/experience. Could be placed under Skills.
Also "Why You’ll Love It Here" includes some description but not specific skills.
Thus Skills section could combine Bonus Points and maybe How We Do It? But How We Do It is more about values; maybe we can omit.
Schedule: remote role based in Florida, primarily remote, employees should expect opportunities for in-person collaboration, team meetings, or company events approximately 10% of the time.
Also Additional Information includes interview details etc but we should remove boilerplate like EEO, legal, accommodation, pay transparency, search firm policy. Those are boilerplate to remove.
Thus final HTML:
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should only include sections when posting has real specific content. We need to map content to these headings.
We have:
- Company Description: could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Job Description" which includes responsibilities. Could map to "Responsibilities". Also "Qualifications" heading matches.
- "What You’ll Do" is responsibilities.
- "What You Bring" is qualifications/requirements.
- "How We Do It" maybe "Skills"? Actually it's values/trust etc. Could be omitted if not specific? It's more about culture; maybe we can include as "Skills"? But it's not skill list; it's values. Might be considered boilerplate? It's not required but could be included as "Skills"? However instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "How We Do It" section lists Trust, Teamwork, Transparency, Agility, Entrepreneurial Spirit. That's specific content (values). Could be considered "Skills"? But maybe better to treat as "Skills" heading? However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: maybe company description + why role matters? Could combine.
- Responsibilities: "What You’ll Do" list.
- Requirements: "What You Bring" list (experience, education).
- Qualifications: maybe same as Requirements? But we shouldn't duplicate. Could treat "Qualifications" as the list of qualifications (education, experience). But we already have Requirements. Might combine.
Better: Use sections: About the role (company description + why role matters), Responsibilities (What You’ll Do), Requirements (What You Bring), Skills (maybe technical skills list from qualifications?), Benefits (maybe not present), Pay (not present), Schedule (remote Florida-based, 10% in-person). Actually schedule info is present: remote role based in Florida, primarily remote, expect in-person collaboration approx 10% of time. That's schedule info. So we can include Schedule section.
Benefits: Not explicitly listed; there is mention of compensation and benefits in Additional Information: "Actual compensation will be based on factors... and may include additional forms of compensation and benefits such as health insurance, retirement plans, paid time off, etc." That's vague but mentions benefits. However it's not specific; it's generic. Might be considered filler? It says "may include additional forms of compensation and benefits such as health insurance, retirement plans, paid time off, etc." That's somewhat specific but still generic. Could we include Benefits section with that? It's not a list of specific benefits; it's a statement. Might be considered filler? The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is not exactly those, but it's vague. Might be okay to include? Safer to omit Benefits if not concrete.
Pay: There's mention of "good faith pay range for each position" but not actual numbers. So no specific pay. So omit Pay.
Thus sections: About the role, Responsibilities, Requirements, Skills (maybe technical skills), Schedule.
But we need to avoid duplication. Let's extract content.
Company Description: "VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business and home to trusted brands that shape culture, inform audiences, and build lasting connections. It operates across four core markets: political news and opinion, business news and personal finance, golf, and sports and genre entertainment. These markets are served through a powerful portfolio of iconic and innovative brands, including CNBC, MS NOW, USA Network, Golf Channel, Oxygen, E!, SYFY, and Versant's sports division USA Sports, along with complementary digital assets including Fandango, Rotten Tomatoes, GolfNow and GolfPass."
Why This Role Matters: "Our database platforms support critical applications and workflows across Versant. Your work will directly contribute to the stability, scalability, security, and recoverability of the systems our teams rely on to operate effectively."
Combine these into About the role.
Responsibilities: "What You’ll Do" bullet list (actually sentences). Let's extract each sentence as list item.
- Own the health and reliability of SQL Server environments across Production, Staging, and Development, including SQL Server hosted on AWS RDS, maintaining availability in accordance with established SLAs, SLOs, RTOs, and RPOs.
- Support and administer additional relational database platforms, including MySQL and PostgreSQL, as needed across cloud and on-premises environments, applying consistent standards for reliability, security, performance, backup, and recovery.
- Monitor and optimize database performance and capacity using execution plans, Query Store, wait statistics, Extended Events, indexing analysis, observability platforms, and other diagnostic tools to proactively identify and resolve issues.
- Strengthen database security and resilience by administering access and permissions using least-privilege practices and designing, implementing, testing, and validating backup, restore, high-availability, and disaster-recovery strategies.
- Partner with engineering teams throughout the development lifecycle to improve T-SQL, query and schema design, indexing, CI/CD workflows, automated deployments, data migrations, integrations, and post-deployment validation.
- Automate repeatable database operations and improve production support using infrastructure-as-code, PowerShell, and other scripting technologies while enhancing monitoring, alerting, dashboards, incident response, root-cause analysis, and technical documentation.
Requirements: "What You Bring" list.
- 5+ years of hands-on SQL Server transactional database administration experience, including production database environments.
- Strong SQL Server administration expertise across configuration, security, permissions, maintenance, backups, restores, troubleshooting, and operational support.
- Strong experience with AWS database and infrastructure services, particularly RDS, Secrets Manager, S3, CloudWatch, and related technologies.
- Advanced SQL Server performance analysis and optimization capabilities, including execution plans, Query Store, index design, wait statistics, blocking analysis, query tuning, Extended Events, and related diagnostic technologies.
- Strong knowledge of SQL Server concurrency and transaction behavior, including isolation levels, locking, blocking, and deadlocks.
- Experience designing and supporting high-availability and disaster-recovery solutions, including Always On Availability Groups, backup and restore strategies, and RTO/RPO planning.
- Strong proficiency in T-SQL and PowerShell, with experience using automation to improve database administration and operational workflows.
- Working knowledge of MySQL and PostgreSQL administration, including configuration, monitoring, security, backup and restore, and troubleshooting in production environments.
- Experience with source control and database CI/CD practices using Git, GitHub, GitHub Actions, or equivalent technologies.
- Experience with monitoring and observability platforms such as Datadog, Prometheus, CloudWatch, or equivalent.
- Demonstrated ability to independently troubleshoot complex production database issues, perform root-cause analysis, manage assigned work, communicate risks and blockers, and escalate appropriately.
- An associate’s degree in Computer Science, Information Technology, a related field, or equivalent professional experience.
Skills: Could be derived from "How We Do It" (Trust, Teamwork, Transparency, Agility, Entrepreneurial Spirit) but those are values not skills. Maybe we can treat "Bonus Points" as skills? Bonus Points list:
- Experience with Python or Bash.
- Experience with MySQL or PostgreSQL in AWS-managed services such as Amazon RDS or Aurora.
- Experience operating and optimizing heterogeneous database environments that include SQL Server, MySQL, and PostgreSQL.
- Experience building infrastructure-as-code or other repeatable database provisioning and configuration workflows.
- Experience supporting data integration, migration, or replication across systems and environments.
These are additional skills/experience. Could be placed under Skills.
Also "Why You’ll Love It Here" includes some description but not specific skills.
Thus Skills section could combine Bonus Points and maybe How We Do It? But How We Do It is more about values; maybe we can omit.
Schedule: remote role based in Florida, primarily remote, employees should expect opportunities for in-person collaboration, team meetings, or company events approximately 10% of the time.
Also Additional Information includes interview details etc but we should remove boilerplate like EEO, legal, accommodation, pay transparency, search firm policy. Those are boilerplate to remove.
Thus final HTML:
About the role
VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business and home to trusted brands that shape culture, inform audiences, and build lasting connections. It operates across four core markets: political news and opinion, business news and personal finance, golf, and sports and genre entertainment. These markets are served through a powerful portfolio of iconic and innovative brands, including CNBC, MS NOW, USA Network, Golf Channel, Oxygen, E!, SYFY, and Versant's sports division USA Sports, along with complementary digital assets including Fandango, Rotten Tomatoes, GolfNow and GolfPass. Our database platforms support critical applications and workflows across Versant. Your work will directly contribute to the stability, scalability, security, and recoverability of the systems our teams rely on to operate effectively.
Responsibilities
- Own the health and reliability of SQL Server environments across Production, Staging, and Development, including SQL Server hosted on AWS RDS, maintaining availability in accordance with established SLAs, SLOs, RTOs, and RPOs.
- Support and administer additional relational database platforms, including MySQL and PostgreSQL, as needed across cloud and on-premises environments, applying consistent standards for reliability, security, performance, backup, and recovery.
- Monitor and optimize database performance and capacity using execution plans, Query Store, wait statistics, Extended Events, indexing analysis, observability platforms, and other diagnostic tools to proactively identify and resolve issues.
- Strengthen database security and resilience by administering access and permissions using least-privilege practices and designing, implementing, testing, and validating backup, restore, high-availability, and disaster-recovery strategies.
- Partner with engineering teams throughout the development lifecycle to improve T-SQL, query and schema design, indexing, CI/CD workflows, automated deployments, data migrations, integrations, and post-deployment validation.
- Automate repeatable database operations and improve production support using infrastructure-as-code, PowerShell, and other scripting technologies while enhancing monitoring, alerting, dashboards, incident response, root-cause analysis, and technical documentation.
Requirements
- 5+ years of hands-on SQL Server transactional database administration experience, including production database environments.
- Strong SQL Server administration expertise across configuration, security, permissions, maintenance, backups, restores, troubleshooting, and operational support.
- Strong experience with AWS database and infrastructure services, particularly RDS, Secrets Manager, S3, CloudWatch, and related technologies.
- Advanced SQL Server performance analysis and optimization capabilities, including execution plans, Query Store, index design, wait statistics, blocking analysis, query tuning, Extended Events, and related diagnostic technologies.
- Strong knowledge of SQL Server concurrency and transaction behavior, including isolation levels, locking, blocking, and deadlocks.
- Experience designing and supporting high-availability and disaster-recovery solutions, including Always On Availability Groups, backup and restore strategies, and RTO/RPO planning.
- Strong proficiency in T-SQL and PowerShell, with experience using automation to improve database administration and operational workflows.