Principal Database Developer
for headings. Use - for lists,
for prose. Do not repeat job title as heading. Do not include Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include only sections with real specific content. Avoid filler like "commensurate with experience", etc. Pay section only if posting states salary range; it does: "Our estimated salary range for this position is $130,000 - $170,000". So we include Pay section. Schedule: posting says "Hybrid role, in Ashburn, VA 1-2 days per week". That's schedule info. So include Schedule section. Benefits: posting lists many benefits: generous flexible time-off, flexible work schedules, career development, industry-leading benefits (health plans, dental, vision, FSA, commuter, life insurance, etc.), 401K matching 5%, regular social events, community engagement. So include Benefits section.
We need sections: About the role (maybe "What You'll Be Doing") - that is a description. Could be "What You'll Be Doing". Use
What You'll Be Doing
then ... maybe also include responsibilities? The posting includes "What You'll Be Doing:" then description. Could treat that as Responsibilities? But we have separate Responsibilities heading. The description is about duties. Could map to Responsibilities. However we can also have "About the role" as summary. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have content for: What You'll Be Doing (duties) -> could be Responsibilities. Required Education, Experience, and Skills -> Requirements (maybe also Qualifications). Preferred Education, Experience, and Skills -> Qualifications (or Skills). There's also specific skills list: experience with PostgreSQL, Python, Git, AWS, etc. That could be Skills. We need to avoid duplication. Let's parse:
- Required Education, Experience, and Skills: Bachelor's degree plus 10+ years in database development roles; Experience in data profiling, cleansing, reporting, data staging, ETL jobs; Strong experience creating complex SQL in complex data environments; Strong experience troubleshooting, tuning SQL and writing performance queries; Experience in writing DDL, DML and DCL; Hands-on experience with PostgreSQL database development; Experience writing Python scripts; Experience with Git/version control; AWS experience including data migration, validation, data pipelines, CloudWatch, Kibana and Dynatrace; Ability to learn new tools quickly as needed to provide new ideas for solving problems; Ability and desire to work with other program staff and customers to reach design decisions within given constraints; Excellent diplomacy and communication skills with both clients and technical staff.
- Preferred Education, Experience, and Skills: Experience working with federal government clients; Experience with Oracle/DB2/SQLServer/MySQL/Terradata; Experience with Databricks, PySpark, Liquibase, DMS; Experience in database administration; Experience with Agile methodology and use of Jira for tracking; Must be willing to learn DB2 if not already a skill set.
Thus we can have sections: Requirements (required), Qualifications (preferred), Skills (maybe combine technical skills). But we have many skill items in required and preferred; we could put them under Skills. However instruction: prefer a few substantive sections over many thin ones. Could combine Required and Preferred into Requirements and Qualifications. Skills could be a separate section listing technical skills (PostgreSQL, Python, Git, AWS, etc.) but those are already in required. Might be redundant. Perhaps better: Have sections: About the role (short summary), Responsibilities (the "What You'll Be Doing" paragraph), Requirements (required education/experience/skills), Qualifications (preferred), Benefits, Pay, Schedule.
We must not emit empty sections. Ensure each heading has substantive content.
Now we need to strip boilerplate: lines like "Clearance: Active Public Trust in DHS or a component of DHS Hybrid role, in Ashburn, VA 1-2 days per week" - that's metadata; we can fold into short p maybe under About the role or Schedule. The clearance is a requirement? It's a clearance requirement. Could be part of Requirements. But we can include in Requirements as a bullet: "Active Public Trust clearance in DHS or component". Also location/hybrid schedule goes to Schedule.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep all details from required, preferred, benefits, pay, schedule, etc.
We must not include duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning, application instructions. At end there is "Equal Opportunity Employer / Individuals with Disabilities / Protected Veterans Dev Technology Group operates in the following states: ..." That's EEO boilerplate; remove. Also "To learn more about working at Dev Technology, visit Working At Dev Technology Group" maybe considered boilerplate; remove. Also "Dev Technology is a growing IT company..." that's about the company; could be part of About the role? Might be considered boilerplate but it's substantive about employer; maybe keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who We Are" section is not explicitly prohibited; it's descriptive of the company. Could be considered part of About the role. However we already have a description of what you'll be doing. Could include a short paragraph about the company under About the role. But we must not invent or summarize away detail; we can keep it as is.
Thus About the role could combine the initial sentence: "Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment." plus maybe the "Who We Are" paragraph.
But we must not repeat the job title as heading; we already not using it.
Now produce HTML.
Structure:
What You'll Be Doing
The Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment.
Maybe also include company description? Could add another paragraph: "Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government..." but that may be considered boilerplate? It's not EEO; it's about the company. I'd include it under About the role as additional paragraph.
But we need to avoid duplication: The "Who We Are" paragraph appears later; we can include it here.
Thus:
What You'll Be Doing
The Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment.
Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government. We partner with our federal customers to deliver technology services and solutions, and to drive our client’s missions forward through innovation. We use Agile and DevSecOps principles to provide services including application development, biometrics and identity management, cloud and infrastructure optimization, IT and legacy modernization, and data management. As a Washington Post Top Workplace award winner for the past THIRTEEN years in a row, the Top Workplaces USA for the past five years, and a recipient of the Companies As Responsive Employers (CARE) Award for the past six years, Dev Technology employees enjoy: ...
But that second paragraph includes a list of benefits; we might want to move benefits to separate Benefits section. So we should not include the benefits list in About the role; we should keep only the company description without benefits list. The "Who We Are" paragraph includes benefits list after colon. We could split: keep the description before colon, and move the list to Benefits. So we need to extract the benefits list.
Thus About the role: first paragraph (duties) + second paragraph up to colon: "Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government. We partner with our federal customers to deliver technology services and solutions, and to drive our client’s missions forward through innovation. We use Agile and DevSecOps principles to provide services including application development, biometrics and identity management, cloud and infrastructure optimization, IT and legacy modernization, and data management." Then we stop before colon.
Now Benefits section: list the benefits enumerated after colon: "Generous and flexible time-off policyFlexible work schedules and telework options, including remote work availability for eligible projectsCareer development opportunities including a mentorship program, technical and management training through Dev University, hands-on learning through DevLab, tuition reimbursement, and paid training opportunitiesIndustry-leading benefits including a choice of two health plans that include dental and vision, flexible spending account, commuter benefits, life insurance, and more401K matching with a 5% matching contributionRegular team and company social events including our annual party, happy hours, fitness challenges, and more A focus on community engagement including company wide support activities, employer match for donations, and time off for volunteer efforts"
We need to format as list items. The text currently has no punctuation; we need to split logically. We'll create - for each benefit category.
We can parse:
- Generous and flexible time-off policy
- Flexible work schedules and telework options, including remote work availability for eligible projects
- Career development opportunities including a mentorship program, technical and management training through Dev University, hands-on learning through DevLab, tuition reimbursement, and paid training opportunities
- Industry-leading benefits including a choice of two health plans that include dental and vision, flexible spending account, commuter benefits, life insurance, and more
- 401K matching with a 5% matching contribution
- Regular team and company social events including our annual party, happy hours, fitness challenges, and more
- A focus on community engagement including company wide support activities, employer match for donations, and time off for volunteer efforts
Now Responsibilities: we already have duties in What You'll Be Doing; maybe we can rename that section to Responsibilities. But the instruction gave example headings; we can use Responsibilities heading for duties. Let's use
Responsibilities
and put the duty paragraph there. Then we may not need What You'll Be Doing. However we still need to convey the opportunity to learn new domain etc. That's part of responsibilities. So we can put that in responsibilities.
Thus:
Responsibilities
The Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment.
Now Requirements (required): list items.
We need to include clearance requirement: Active Public Trust in DHS or a component of DHS.
Also location/hybrid schedule goes to Schedule section.
Thus Requirements bullets:
- Bachelor's degree plus 10+ years in database development roles
- Experience in data profiling, cleansing, reporting, data staging, ETL jobs
-
for prose. Do not repeat job title as heading. Do not include Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include only sections with real specific content. Avoid filler like "commensurate with experience", etc. Pay section only if posting states salary range; it does: "Our estimated salary range for this position is $130,000 - $170,000". So we include Pay section. Schedule: posting says "Hybrid role, in Ashburn, VA 1-2 days per week". That's schedule info. So include Schedule section. Benefits: posting lists many benefits: generous flexible time-off, flexible work schedules, career development, industry-leading benefits (health plans, dental, vision, FSA, commuter, life insurance, etc.), 401K matching 5%, regular social events, community engagement. So include Benefits section. We need sections: About the role (maybe "What You'll Be Doing") - that is a description. Could be "What You'll Be Doing". Use
What You'll Be Doing
then... maybe also include responsibilities? The posting includes "What You'll Be Doing:" then description. Could treat that as Responsibilities? But we have separate Responsibilities heading. The description is about duties. Could map to Responsibilities. However we can also have "About the role" as summary. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have content for: What You'll Be Doing (duties) -> could be Responsibilities. Required Education, Experience, and Skills -> Requirements (maybe also Qualifications). Preferred Education, Experience, and Skills -> Qualifications (or Skills). There's also specific skills list: experience with PostgreSQL, Python, Git, AWS, etc. That could be Skills. We need to avoid duplication. Let's parse:
- Required Education, Experience, and Skills: Bachelor's degree plus 10+ years in database development roles; Experience in data profiling, cleansing, reporting, data staging, ETL jobs; Strong experience creating complex SQL in complex data environments; Strong experience troubleshooting, tuning SQL and writing performance queries; Experience in writing DDL, DML and DCL; Hands-on experience with PostgreSQL database development; Experience writing Python scripts; Experience with Git/version control; AWS experience including data migration, validation, data pipelines, CloudWatch, Kibana and Dynatrace; Ability to learn new tools quickly as needed to provide new ideas for solving problems; Ability and desire to work with other program staff and customers to reach design decisions within given constraints; Excellent diplomacy and communication skills with both clients and technical staff.
- Preferred Education, Experience, and Skills: Experience working with federal government clients; Experience with Oracle/DB2/SQLServer/MySQL/Terradata; Experience with Databricks, PySpark, Liquibase, DMS; Experience in database administration; Experience with Agile methodology and use of Jira for tracking; Must be willing to learn DB2 if not already a skill set.
Thus we can have sections: Requirements (required), Qualifications (preferred), Skills (maybe combine technical skills). But we have many skill items in required and preferred; we could put them under Skills. However instruction: prefer a few substantive sections over many thin ones. Could combine Required and Preferred into Requirements and Qualifications. Skills could be a separate section listing technical skills (PostgreSQL, Python, Git, AWS, etc.) but those are already in required. Might be redundant. Perhaps better: Have sections: About the role (short summary), Responsibilities (the "What You'll Be Doing" paragraph), Requirements (required education/experience/skills), Qualifications (preferred), Benefits, Pay, Schedule.
We must not emit empty sections. Ensure each heading has substantive content.
Now we need to strip boilerplate: lines like "Clearance: Active Public Trust in DHS or a component of DHS Hybrid role, in Ashburn, VA 1-2 days per week" - that's metadata; we can fold into short p maybe under About the role or Schedule. The clearance is a requirement? It's a clearance requirement. Could be part of Requirements. But we can include in Requirements as a bullet: "Active Public Trust clearance in DHS or component". Also location/hybrid schedule goes to Schedule.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep all details from required, preferred, benefits, pay, schedule, etc.
We must not include duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning, application instructions. At end there is "Equal Opportunity Employer / Individuals with Disabilities / Protected Veterans Dev Technology Group operates in the following states: ..." That's EEO boilerplate; remove. Also "To learn more about working at Dev Technology, visit Working At Dev Technology Group" maybe considered boilerplate; remove. Also "Dev Technology is a growing IT company..." that's about the company; could be part of About the role? Might be considered boilerplate but it's substantive about employer; maybe keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who We Are" section is not explicitly prohibited; it's descriptive of the company. Could be considered part of About the role. However we already have a description of what you'll be doing. Could include a short paragraph about the company under About the role. But we must not invent or summarize away detail; we can keep it as is.
Thus About the role could combine the initial sentence: "Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment." plus maybe the "Who We Are" paragraph.
But we must not repeat the job title as heading; we already not using it.
Now produce HTML.
Structure:
What You'll Be Doing
The Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment.
Maybe also include company description? Could add another paragraph: "Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government..." but that may be considered boilerplate? It's not EEO; it's about the company. I'd include it under About the role as additional paragraph. But we need to avoid duplication: The "Who We Are" paragraph appears later; we can include it here. Thus:What You'll Be Doing
The Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment.
Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government. We partner with our federal customers to deliver technology services and solutions, and to drive our client’s missions forward through innovation. We use Agile and DevSecOps principles to provide services including application development, biometrics and identity management, cloud and infrastructure optimization, IT and legacy modernization, and data management. As a Washington Post Top Workplace award winner for the past THIRTEEN years in a row, the Top Workplaces USA for the past five years, and a recipient of the Companies As Responsive Employers (CARE) Award for the past six years, Dev Technology employees enjoy: ...
But that second paragraph includes a list of benefits; we might want to move benefits to separate Benefits section. So we should not include the benefits list in About the role; we should keep only the company description without benefits list. The "Who We Are" paragraph includes benefits list after colon. We could split: keep the description before colon, and move the list to Benefits. So we need to extract the benefits list. Thus About the role: first paragraph (duties) + second paragraph up to colon: "Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government. We partner with our federal customers to deliver technology services and solutions, and to drive our client’s missions forward through innovation. We use Agile and DevSecOps principles to provide services including application development, biometrics and identity management, cloud and infrastructure optimization, IT and legacy modernization, and data management." Then we stop before colon. Now Benefits section: list the benefits enumerated after colon: "Generous and flexible time-off policyFlexible work schedules and telework options, including remote work availability for eligible projectsCareer development opportunities including a mentorship program, technical and management training through Dev University, hands-on learning through DevLab, tuition reimbursement, and paid training opportunitiesIndustry-leading benefits including a choice of two health plans that include dental and vision, flexible spending account, commuter benefits, life insurance, and more401K matching with a 5% matching contributionRegular team and company social events including our annual party, happy hours, fitness challenges, and more A focus on community engagement including company wide support activities, employer match for donations, and time off for volunteer efforts" We need to format as list items. The text currently has no punctuation; we need to split logically. We'll create- for each benefit category.
We can parse:
- Generous and flexible time-off policy
- Flexible work schedules and telework options, including remote work availability for eligible projects
- Career development opportunities including a mentorship program, technical and management training through Dev University, hands-on learning through DevLab, tuition reimbursement, and paid training opportunities
- Industry-leading benefits including a choice of two health plans that include dental and vision, flexible spending account, commuter benefits, life insurance, and more
- 401K matching with a 5% matching contribution
- Regular team and company social events including our annual party, happy hours, fitness challenges, and more
- A focus on community engagement including company wide support activities, employer match for donations, and time off for volunteer efforts
Now Responsibilities: we already have duties in What You'll Be Doing; maybe we can rename that section to Responsibilities. But the instruction gave example headings; we can use Responsibilities heading for duties. Let's use
Responsibilities
and put the duty paragraph there. Then we may not need What You'll Be Doing. However we still need to convey the opportunity to learn new domain etc. That's part of responsibilities. So we can put that in responsibilities. Thus:Responsibilities
The Principal Database Developer will work with a team of database developers and database administrators to support an active program of application development - creating new structures, updating existing ones and managing data within large, complex databases. This is a great opportunity to learn a new domain and a new skillsets in a dynamic environment.
Now Requirements (required): list items. We need to include clearance requirement: Active Public Trust in DHS or a component of DHS. Also location/hybrid schedule goes to Schedule section. Thus Requirements bullets: - Bachelor's degree plus 10+ years in database development roles - Experience in data profiling, cleansing, reporting, data staging, ETL jobs -