Database Architect
GLOTECH, Inc. · Orlando, FL · 4 wk ago
Information TechnologyFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Preserve all substantive info.
We need to parse the posting.
First part: GLOTECH description: company info, benefits, etc. That could be "About the role"? Actually "About the role" maybe about the position. But we have company description and benefits. Could treat as "About the role" or maybe "Benefits". The posting includes benefits description: medical dental vision, disability, life, FSA, EAP, annual leave, sick leave, holiday pay, educational assistance, certification/training reimbursement, 401(k) with employer match. That's benefits.
Also there is "Pay" not mentioned. No salary. So we should not include Pay section.
Schedule: mentions onsite one day per week, on-call one week each month, 24/7 support for high-priority outages. That's schedule info. So we can include Schedule section.
Responsibilities: there is a big block after "Responsibilities GLOTECH, Inc. is seeking a Database Architect..." plus later "RESPONSIBILITIES:" list. We need to combine responsibilities content. Should not duplicate. We'll extract substantive responsibilities.
Qualifications: list after "Qualifications". Also there is "NICE TO HAVE" list which could be Skills? Actually "NICE TO HAVE" could be Skills section. We have Skills section maybe for nice-to-have tools. We'll treat "Skills" for nice-to-have.
Requirements: maybe the qualifications are requirements. We'll put qualifications under "Requirements" or "Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications? Might be overlapping. We could put core qualifications under Requirements, and nice-to-have under Skills. Or we could put qualifications under Qualifications and skills under Skills. Let's decide: Use Requirements for mandatory qualifications (7+ years MS SQL Server Admin, performance tuning, etc). Use Qualifications maybe for education? Not present. Could combine. But we need to follow instruction: include a section only when posting has real specific content for it. So we need to decide which headings have content.
We have:
- About the role: could include company description and maybe role summary. The posting starts with company overview. That could be "About the role". We'll include that.
- Responsibilities: definitely.
- Requirements: mandatory qualifications list.
- Qualifications: maybe we could treat as same as Requirements? But we need distinct. Could put "Qualifications" for the nice-to-have? Actually nice-to-have is more like skills. So we could put "Skills" for nice-to-have tools. Then "Qualifications" could be empty; we should not include empty section. So we omit Qualifications.
- Skills: nice-to-have list.
- Benefits: benefits description.
- Pay: none -> omit.
- Schedule: schedule info.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now we need to format.
About the role: include company overview: GLOTECH, Inc., founded 1995, privately and minority-owned, serving military, federal, commercial clients. Successful IT firm with large staff providing superior IT and advanced engineering services worldwide. Success built on attracting/retaining quality staff via competitive benefits, focus on continuing career development and corporate financial support. Collegial working environment, opportunities to improve/enhance skills. Committed to comprehensive employee benefits program that helps employees stay healthy, feel secure, maintain work/life balance. Provide medical dental vision care, disability insurance (short/long term), Life & AD&D Insurance, Flexible Spending Accounts (Healthcare, Dependent Care and Commuter Transportation and Parking Reimbursement), Employee Assistance Programs. Additionally, Annual Leave, Sick Leave, Holiday Pay, Educational Assistance, Certification/Training Reimbursement, and a 401(k)-retirement savings contribution plan (with employer match). Wait that's benefits; but we already have Benefits section. So maybe About the role should be just company overview without benefits. But we can include company overview and maybe mention benefits briefly? However benefits will be separate. To avoid duplication, we should not repeat benefits in About the role. So About the role: company overview only (founding, ownership, clients, IT firm, success factors, collegial environment, opportunities). We'll keep that.
Responsibilities: combine the responsibilities paragraphs. Need to preserve all substantive info. Let's extract.
From after "Responsibilities GLOTECH, Inc. is seeking a Database Architect to support the corporate office of SeaWorld Parks & Entertainment, located in Orlando, Florida. Prefer local candidates to the Orlando, FL or surrounding area as this role will be required to be onsite one day per week. Remote candidates will only be considered from SeaWorld approved states (OR NJ CT WA NC VA CA FL PA TX). This position requires “on call” responsibilities for one week each month and also requires being on support 24/7 for high-priority system outages. This candidate will join a database team size of five people including the director and four other senior DBA's. The ideal candidate will be in a technical lead architect role as the Director’s “right hand”. Their responsibilities include architect work 25% of the time, technical lead work 25% of the time and senior DBA work 50% of the time. Architect breakdown (25%): The architect work entails having experience thinking of applications that could help streamline or create efficiency for a specific business problem. This person must have brought an application from conception through development AKA finding a business problem, creating a solution, designing that solution and then building it out. They will be responsible for architecting some work internal to the database team from concept to design to execution. An example of this work is building customized applications into the environment to monitor systems. Specifically, the person in this role before built a tool that could access the data in an effort to deploy it across fleets to see what users were accessing what systems. This tool could technically serve as an audit tool, but it was moreso used to determine what systems were not being used like hosts, databases, systems, etc. so that they could then be decommissioned. Technical lead breakdown (25%): The technical lead work entails having experience working with cross department teams and working with them in order to ensure their application plans will be feasible with the database. This person must have the business acumen to work with other stakeholders and developers from other teams to guide, aid and solution how their specific application can or cannot integrate with the database (and if there’s an issue where it can’t interact, how can we get it there). This means they will be working with other application teams to design, implementation and make decisions on their applications so that it can integrate with all of the systems at SeaWorld. Basically, full SDLC knowledge and being able to document a written design plan, as well as why or why not a particular application would work. They will be working hand in hand on this type of work with the Director. Senior DBA breakdown (50%): This person must be proficient in all versions of MS SQL server, SSIS and have a decent amount of experience/knowledge working with Azure cloud. This DBA will be responsible for the implementation, configuration, maintenance, and performance of critical SQL Server systems, to ensure the availability and consistent performance of our corporate applications. This is a hands-on position requiring solid technical skills as well as excellent interpersonal and communication skills. They will be responsible for the development and sustainment of SQL Server environments (DEV, QA, UAT and PROD), ensuring its operational readiness (security, health, and performance), performance tuning and data modeling in support of multiple development teams and 3rd party vendor products. The environments support an enterprise application suite of OLTP and OLAP solutions. The individual must be capable of working independently and collaboratively with the ability to quickly understand complex data solutions and schema. There are gaps right now as it pertains to the DBA team with the cloud and support will be needed with replication work - on a day to day, this person will be responsible for replicating, checking if backups have failed, re running tests, checking services (for example, sometimes they have alerts of discontention so they need to check the IO to see if there's a bottleneck that needs tuning), checking the health of the databases overall, performing tests on various settings within the databases and adjusting accordingly, etc. Additionally, this person will be writing queries in SQL sometimes but mostly setting up and configuring within MS SQL. They will be responsible for collecting metrics on servers that report back to the repository but need to migrate this to SSIS so it works well with the BI team.
Then later "RESPONSIBILITIES:" list:
- Manage SQL Server databases through multiple product lifecycle environments, from development to mission-critical production systems.
- Configure and maintain database servers and processes, including monitoring of system health and performance, to ensure high levels of performance, availability, and security.
- Apply data modeling techniques to ensure development and implementation support efforts meet integration and performance expectations.
- Assist with design and implementation of a data loading tool to move sanitized data from production to a non-production environment.
- Independently analyze, solve, and correct issues in real time, providing problem resolution end-to-end.
- Refine and automate regular processes, track issues, and document changes.
- Assist developers with complex query tuning and schema refinement.
- Participate in an on-call rotation to provide 24x7 support for critical production systems.
- Perform scheduled maintenance and support release deployment activities after hours.
- Share domain and technical expertise, providing technical mentorship and cross-training to other peers and team members.
- Monitor and apply SQL Server Service Packs and Cumulative Updates.
We need to combine without duplication. The earlier paragraphs already cover many of these points. We'll produce a cohesive responsibilities section that includes all points, but avoid repeating same sentences. We'll just combine them into a bullet list (
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Preserve all substantive info.
We need to parse the posting.
First part: GLOTECH description: company info, benefits, etc. That could be "About the role"? Actually "About the role" maybe about the position. But we have company description and benefits. Could treat as "About the role" or maybe "Benefits". The posting includes benefits description: medical dental vision, disability, life, FSA, EAP, annual leave, sick leave, holiday pay, educational assistance, certification/training reimbursement, 401(k) with employer match. That's benefits.
Also there is "Pay" not mentioned. No salary. So we should not include Pay section.
Schedule: mentions onsite one day per week, on-call one week each month, 24/7 support for high-priority outages. That's schedule info. So we can include Schedule section.
Responsibilities: there is a big block after "Responsibilities GLOTECH, Inc. is seeking a Database Architect..." plus later "RESPONSIBILITIES:" list. We need to combine responsibilities content. Should not duplicate. We'll extract substantive responsibilities.
Qualifications: list after "Qualifications". Also there is "NICE TO HAVE" list which could be Skills? Actually "NICE TO HAVE" could be Skills section. We have Skills section maybe for nice-to-have tools. We'll treat "Skills" for nice-to-have.
Requirements: maybe the qualifications are requirements. We'll put qualifications under "Requirements" or "Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications? Might be overlapping. We could put core qualifications under Requirements, and nice-to-have under Skills. Or we could put qualifications under Qualifications and skills under Skills. Let's decide: Use Requirements for mandatory qualifications (7+ years MS SQL Server Admin, performance tuning, etc). Use Qualifications maybe for education? Not present. Could combine. But we need to follow instruction: include a section only when posting has real specific content for it. So we need to decide which headings have content.
We have:
- About the role: could include company description and maybe role summary. The posting starts with company overview. That could be "About the role". We'll include that.
- Responsibilities: definitely.
- Requirements: mandatory qualifications list.
- Qualifications: maybe we could treat as same as Requirements? But we need distinct. Could put "Qualifications" for the nice-to-have? Actually nice-to-have is more like skills. So we could put "Skills" for nice-to-have tools. Then "Qualifications" could be empty; we should not include empty section. So we omit Qualifications.
- Skills: nice-to-have list.
- Benefits: benefits description.
- Pay: none -> omit.
- Schedule: schedule info.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now we need to format.
About the role: include company overview: GLOTECH, Inc., founded 1995, privately and minority-owned, serving military, federal, commercial clients. Successful IT firm with large staff providing superior IT and advanced engineering services worldwide. Success built on attracting/retaining quality staff via competitive benefits, focus on continuing career development and corporate financial support. Collegial working environment, opportunities to improve/enhance skills. Committed to comprehensive employee benefits program that helps employees stay healthy, feel secure, maintain work/life balance. Provide medical dental vision care, disability insurance (short/long term), Life & AD&D Insurance, Flexible Spending Accounts (Healthcare, Dependent Care and Commuter Transportation and Parking Reimbursement), Employee Assistance Programs. Additionally, Annual Leave, Sick Leave, Holiday Pay, Educational Assistance, Certification/Training Reimbursement, and a 401(k)-retirement savings contribution plan (with employer match). Wait that's benefits; but we already have Benefits section. So maybe About the role should be just company overview without benefits. But we can include company overview and maybe mention benefits briefly? However benefits will be separate. To avoid duplication, we should not repeat benefits in About the role. So About the role: company overview only (founding, ownership, clients, IT firm, success factors, collegial environment, opportunities). We'll keep that.
Responsibilities: combine the responsibilities paragraphs. Need to preserve all substantive info. Let's extract.
From after "Responsibilities GLOTECH, Inc. is seeking a Database Architect to support the corporate office of SeaWorld Parks & Entertainment, located in Orlando, Florida. Prefer local candidates to the Orlando, FL or surrounding area as this role will be required to be onsite one day per week. Remote candidates will only be considered from SeaWorld approved states (OR NJ CT WA NC VA CA FL PA TX). This position requires “on call” responsibilities for one week each month and also requires being on support 24/7 for high-priority system outages. This candidate will join a database team size of five people including the director and four other senior DBA's. The ideal candidate will be in a technical lead architect role as the Director’s “right hand”. Their responsibilities include architect work 25% of the time, technical lead work 25% of the time and senior DBA work 50% of the time. Architect breakdown (25%): The architect work entails having experience thinking of applications that could help streamline or create efficiency for a specific business problem. This person must have brought an application from conception through development AKA finding a business problem, creating a solution, designing that solution and then building it out. They will be responsible for architecting some work internal to the database team from concept to design to execution. An example of this work is building customized applications into the environment to monitor systems. Specifically, the person in this role before built a tool that could access the data in an effort to deploy it across fleets to see what users were accessing what systems. This tool could technically serve as an audit tool, but it was moreso used to determine what systems were not being used like hosts, databases, systems, etc. so that they could then be decommissioned. Technical lead breakdown (25%): The technical lead work entails having experience working with cross department teams and working with them in order to ensure their application plans will be feasible with the database. This person must have the business acumen to work with other stakeholders and developers from other teams to guide, aid and solution how their specific application can or cannot integrate with the database (and if there’s an issue where it can’t interact, how can we get it there). This means they will be working with other application teams to design, implementation and make decisions on their applications so that it can integrate with all of the systems at SeaWorld. Basically, full SDLC knowledge and being able to document a written design plan, as well as why or why not a particular application would work. They will be working hand in hand on this type of work with the Director. Senior DBA breakdown (50%): This person must be proficient in all versions of MS SQL server, SSIS and have a decent amount of experience/knowledge working with Azure cloud. This DBA will be responsible for the implementation, configuration, maintenance, and performance of critical SQL Server systems, to ensure the availability and consistent performance of our corporate applications. This is a hands-on position requiring solid technical skills as well as excellent interpersonal and communication skills. They will be responsible for the development and sustainment of SQL Server environments (DEV, QA, UAT and PROD), ensuring its operational readiness (security, health, and performance), performance tuning and data modeling in support of multiple development teams and 3rd party vendor products. The environments support an enterprise application suite of OLTP and OLAP solutions. The individual must be capable of working independently and collaboratively with the ability to quickly understand complex data solutions and schema. There are gaps right now as it pertains to the DBA team with the cloud and support will be needed with replication work - on a day to day, this person will be responsible for replicating, checking if backups have failed, re running tests, checking services (for example, sometimes they have alerts of discontention so they need to check the IO to see if there's a bottleneck that needs tuning), checking the health of the databases overall, performing tests on various settings within the databases and adjusting accordingly, etc. Additionally, this person will be writing queries in SQL sometimes but mostly setting up and configuring within MS SQL. They will be responsible for collecting metrics on servers that report back to the repository but need to migrate this to SSIS so it works well with the BI team.
Then later "RESPONSIBILITIES:" list:
- Manage SQL Server databases through multiple product lifecycle environments, from development to mission-critical production systems.
- Configure and maintain database servers and processes, including monitoring of system health and performance, to ensure high levels of performance, availability, and security.
- Apply data modeling techniques to ensure development and implementation support efforts meet integration and performance expectations.
- Assist with design and implementation of a data loading tool to move sanitized data from production to a non-production environment.
- Independently analyze, solve, and correct issues in real time, providing problem resolution end-to-end.
- Refine and automate regular processes, track issues, and document changes.
- Assist developers with complex query tuning and schema refinement.
- Participate in an on-call rotation to provide 24x7 support for critical production systems.
- Perform scheduled maintenance and support release deployment activities after hours.
- Share domain and technical expertise, providing technical mentorship and cross-training to other peers and team members.
- Monitor and apply SQL Server Service Packs and Cumulative Updates.
We need to combine without duplication. The earlier paragraphs already cover many of these points. We'll produce a cohesive responsibilities section that includes all points, but avoid repeating same sentences. We'll just combine them into a bullet list (- ) as per rule: Use
- for any list of duties/requirements/benefits. So responsibilities should be a list.
Thus we will create
Responsibilities
then - items.
We need to include all substantive responsibilities from both sections.
Let's compile list:
- Support the corporate office of SeaWorld Parks & Entertainment in Orlando, Florida (onsite one day per week; remote candidates limited to approved states).
- Participate in on-call rotation (one week each month) and provide 24/7 support for high-priority system outages.
- Function as technical lead architect (Director’s right hand) splitting time: 25% architect work, 25% technical lead work, 50% senior DBA work.
- Architect work: conceive, design, build applications to streamline business problems; develop customized monitoring tools; identify underused systems for decommissioning.
- Technical lead work: collaborate with cross-department teams to ensure application feasibility with database; guide integration; apply full SDLC knowledge; document design plans; work with Director.
- Senior DBA work: proficient in MS SQL Server (all versions), SSIS, Azure cloud; implement, configure, maintain, performance-tune critical SQL Server systems; ensure availability and consistent performance of corporate applications.
- Develop and sustain SQL Server environments (DEV, QA, UAT, PROD); ensure operational readiness (security, health, performance); performance tuning; data modeling for multiple dev teams and third-party products supporting OLTP/OLAP suite.
- Work independently and collaboratively to understand complex data solutions and schema.
- Handle cloud-related gaps: replication work, verify backups, rerun tests, check services, monitor I/O for bottlenecks, assess database health, adjust settings.
- Write SQL queries occasionally; primarily configure MS SQL.
- Collect server metrics and migrate to SSIS for BI team.
- Manage SQL Server databases across lifecycle environments (dev to mission-critical production).
- Configure and maintain database servers and processes, monitor system health/performance for
- for any list of duties/requirements/benefits. So responsibilities should be a list.
Thus we will create
Responsibilities
then- items. We need to include all substantive responsibilities from both sections. Let's compile list: - Support the corporate office of SeaWorld Parks & Entertainment in Orlando, Florida (onsite one day per week; remote candidates limited to approved states). - Participate in on-call rotation (one week each month) and provide 24/7 support for high-priority system outages. - Function as technical lead architect (Director’s right hand) splitting time: 25% architect work, 25% technical lead work, 50% senior DBA work. - Architect work: conceive, design, build applications to streamline business problems; develop customized monitoring tools; identify underused systems for decommissioning. - Technical lead work: collaborate with cross-department teams to ensure application feasibility with database; guide integration; apply full SDLC knowledge; document design plans; work with Director. - Senior DBA work: proficient in MS SQL Server (all versions), SSIS, Azure cloud; implement, configure, maintain, performance-tune critical SQL Server systems; ensure availability and consistent performance of corporate applications. - Develop and sustain SQL Server environments (DEV, QA, UAT, PROD); ensure operational readiness (security, health, performance); performance tuning; data modeling for multiple dev teams and third-party products supporting OLTP/OLAP suite. - Work independently and collaboratively to understand complex data solutions and schema. - Handle cloud-related gaps: replication work, verify backups, rerun tests, check services, monitor I/O for bottlenecks, assess database health, adjust settings. - Write SQL queries occasionally; primarily configure MS SQL. - Collect server metrics and migrate to SSIS for BI team. - Manage SQL Server databases across lifecycle environments (dev to mission-critical production). - Configure and maintain database servers and processes, monitor system health/performance for