Database Technical Expert (Remote)
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 — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the job description.
Key info:
- Title: Database Technical Expert (Remote) ID:EISD-032 Location: Kansas City Program: ERS Wage/Hr: $52.00 Hours/Week: 40 Minimum Age: 55
- Description: For over 25 years, NEW Solutions... connecting experienced workers (ages 55+) with full-time and part-time job opportunities that support the critical missions of Federal Agencies across the United States. NEW Solutions connects experienced workers (ages 55+) with the USDA Economic Research Service (ERS). These experienced professionals provide administrative, scientific, and technical support to the Economic Research Service through the Experienced Worker Program (EWP). Positions listed here do not guarantee employment for any definite period. Enrollment in the Experienced Worker Programs administered by NEW Solutions is temporary. The enrollment relationship between NEW Solutions and the Enrollee is an "at-will" relationship. This means that an Enrollee is free to terminate enrollment at any time during the enrollment period, and NEW Solutions and the Agency have the right to terminate the relationship with the Enrollee. PLEASE NOTE: An "Enrollee" is not a federal employee, nor an employee of NEW Solutions. An "Enrollee" is a participant in a grant program established through a Cooperative Agreement funded by the agency and administered by NEW Solutions. This opportunity applies to applicants legally eligible to work in the United States. This position will be open until filled. NOTE: This position has the option to work remotely.
- Qualifications: Minimum of 5 year(s) of experience in Database Management field. OR BA/BS Degree Experience required with Windows, MS Word, MS Excel
- Duties: The Database Technical Expert position within the Economic Research Service will provide specialized technical leadership in the design, security, optimization, modernization, and availability of ERS enterprise database environments that support the agency?s mission of economic and social science research. The enrollee will ensure mission-critical systems, data dissemination processes, and data platforms remain aligned with USDA and federal standards. The functions of this role will include analyzing and enhancing complex data environments, developing operational standards and procedures, coordinating across multiple technologies for high-impact projects, conducting advanced troubleshooting, implementing automation, supporting cloud integration, and improving database management practices to strengthen the production and delivery of ERS data products. The enrollee shall not sign federal documents, authorize the use of federal funds, nor initiate or conduct federally funded research projects. The enrollee shall not author articles for publication as a federal employee, nor coordinate scientific research between the Government and private industry. The enrollee shall not present themselves as a Government employee or Government representative at meetings both foreign and domestic or when coordinating federal agencies? areas of research. The enrollee shall not make decisions on federally based research on behalf of Government policy makers, and the enrollee shall not supervise any Government employees. Lead the architecture, design, and enhancement of ERS enterprise database environments to ensure optimal performance, reliability, and support for mission-critical research and data dissemination. 35%Create, maintain, and ensure recovery of physical databases, including server software installation, database object creation, security implementation, data loading, and execution of backup and recovery activities. 35%Develop database application solutions that support ERS research and publishing needs, including designing data structures, interrelationships, storage requirements, and data processing code. 15%Provide systems analysis to improve database performance and efficacy, monitoring usage, evaluating procedural activities, identifying weaknesses, and recommending enhancements to data structures, security, and access methods. 15%
- Other Physical requirements: Office job Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions of this position. NEW Solutions is committed to promoting equal opportunity and to an environment free from discrimination and harassment in any form administering Experienced Worker Programs under cooperative agreements with federal agencies. It is NEW Solutions' policy to comply with all applicable laws that provide equal opportunity and to prohibit unlawful discrimination in enrolling participants in the federal programs.
We need to remove boilerplate: equal opportunity statements, etc. The "Other Physical requirements" includes office job and reasonable accommodations. Also the equal opportunity statement is boilerplate; we should remove it. Also the "PLEASE NOTE" about enrollee not being federal employee is substantive? It's about the nature of the position; maybe keep as part of description. The "Positions listed here do not guarantee employment for any definite period." etc. Might be considered boilerplate but it's specific to the program; we can keep as part of description.
We need to decide sections: Likely we will have sections: About the role (maybe a summary), Responsibilities (duties), Requirements/Qualifications (qualifications), Skills (maybe list Windows, MS Word, MS Excel), Benefits? Not given. Pay? Wage/Hr: $52.00 given. Schedule? Hours/Week: 40 given. So we have Pay and Schedule specifics. According to rules: include Pay and Schedule sections only if posting actually states them. Yes, we have wage/hours. So we should include Pay and Schedule sections.
Benefits: not stated, so omit.
We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive info: include location, program, wage, hours, minimum age, remote option, description of NEW Solutions, enrollee nature, qualifications, duties with percentages, physical requirements (office job, reasonable accommodations). Also maybe include that position open until filled.
We need to format using
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide what constitutes a list. Duties have percentages and bullet-like statements; we can make a
with each duty as - . Requirements: maybe list qualifications: Minimum 5 years experience OR BA/BS, Experience with Windows, MS Word, MS Excel. Could be a list.
Skills: maybe list Windows, MS Word, MS Excel as skills.
But we need to avoid duplication: qualifications and skills may overlap. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section "Requirements". Or have separate sections if distinct. Let's think: Qualifications: experience/degree. Skills: specific software. Could be separate but might be thin. Better to combine into "Requirements" section covering both experience/degree and technical skills.
We need to include About the role: maybe a summary paragraph describing the role, mission, remote option, etc.
Responsibilities: duties with percentages.
Requirements: qualifications + skills.
Pay: wage/hour.
Schedule: hours/week.
Also maybe include Location, Program, Minimum Age, Remote option as part of About the role or a separate section like "Details". But we have no heading for Details; we could embed in About the role paragraph.
We must not repeat job title as heading. So no
Database Technical Expert
. Good.
We must not put Job ID/requisition numbers as headings; we can fold minor metadata into a short or drop it. So we can include ID, Location, Program, Minimum Age, Remote option in a paragraph under About the role or a separate "Details" section but we need a heading; maybe "Details" is okay as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists examples but not exhaustive; we could use other headings if needed but better to stick to those. So we could put location, program, etc inside About the role paragraph.
Thus structure:
About the role
... includes location, program, wage? Actually wage goes to Pay section. So About the role: description of NEW Solutions, remote option, enrollee nature, mission, etc.
Responsibilities
- Lead the architecture, design, and enhancement of ERS enterprise database environments to ensure optimal performance, reliability, and support for mission-critical research and data dissemination.
- Create, maintain, and ensure recovery of physical databases, including server software installation, database object creation, security implementation, data loading, and execution of backup and recovery activities. (35%)
- Develop database application solutions that support ERS research and publishing needs, including designing data structures, interrelationships, storage requirements, and data processing code. (35%)
- Provide systems analysis to improve database performance and efficacy, monitoring usage, evaluating procedural activities, identifying weaknesses, and recommending enhancements to data structures, security, and access methods. (15%)
- Analyzing and enhancing complex data environments, developing operational standards and procedures, coordinating across multiple technologies for high-impact projects, conducting advanced troubleshooting, implementing automation, supporting cloud integration, and improving database management practices to strengthen the production and delivery of ERS data products.
- The enrollee shall not sign federal documents, authorize the use of federal funds, nor initiate or conduct federally funded research projects.
- The enrollee shall not author articles for publication as a federal employee, nor coordinate scientific research between the Government and private industry.
- The enrollee shall not present themselves as a Government employee or Government representative at meetings both foreign and domestic or when coordinating federal agencies? areas of research.
- The enrollee shall not make decisions on federally based research on behalf of Government policy makers, and the enrollee shall not supervise any Government employees.
But we have some duplication: the first bullet (Lead architecture...) is similar to later bullet list. Might combine. However we need to preserve all substantive info; we can keep both but maybe combine to avoid redundancy. The original text: "Lead the architecture, design, and enhancement of ERS enterprise database environments to ensure optimal performance, reliability, and support for mission-critical research and data dissemination." Then percentages: 35% Create..., 35% Develop..., 15% Provide..., then earlier paragraph: "The functions of this role will include analyzing and enhancing complex data environments, developing operational standards and procedures, coordinating across multiple technologies for high-impact projects, conducting advanced troubleshooting, implementing automation, supporting cloud integration, and improving database management practices to strengthen the production and delivery of ERS data products." That seems like a summary of duties. We could keep that as a separate bullet.
We need to avoid too many thin sections; but responsibilities can be a list.
Now Requirements:
Requirements
- Minimum of 5 years of experience in Database Management field OR a BA/BS degree.
- Experience with Windows, MS Word, and MS Excel.
We could also include Minimum Age 55 as a requirement? It's a condition of the program; maybe include in About the role or Requirements. Since it's a eligibility criterion, we could add to Requirements: "Applicants must be age 55 or older." But the instruction says preserve all substantive info; we should include
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the job description. Key info: - Title: Database Technical Expert (Remote) ID:EISD-032 Location: Kansas City Program: ERS Wage/Hr: $52.00 Hours/Week: 40 Minimum Age: 55 - Description: For over 25 years, NEW Solutions... connecting experienced workers (ages 55+) with full-time and part-time job opportunities that support the critical missions of Federal Agencies across the United States. NEW Solutions connects experienced workers (ages 55+) with the USDA Economic Research Service (ERS). These experienced professionals provide administrative, scientific, and technical support to the Economic Research Service through the Experienced Worker Program (EWP). Positions listed here do not guarantee employment for any definite period. Enrollment in the Experienced Worker Programs administered by NEW Solutions is temporary. The enrollment relationship between NEW Solutions and the Enrollee is an "at-will" relationship. This means that an Enrollee is free to terminate enrollment at any time during the enrollment period, and NEW Solutions and the Agency have the right to terminate the relationship with the Enrollee. PLEASE NOTE: An "Enrollee" is not a federal employee, nor an employee of NEW Solutions. An "Enrollee" is a participant in a grant program established through a Cooperative Agreement funded by the agency and administered by NEW Solutions. This opportunity applies to applicants legally eligible to work in the United States. This position will be open until filled. NOTE: This position has the option to work remotely. - Qualifications: Minimum of 5 year(s) of experience in Database Management field. OR BA/BS Degree Experience required with Windows, MS Word, MS Excel - Duties: The Database Technical Expert position within the Economic Research Service will provide specialized technical leadership in the design, security, optimization, modernization, and availability of ERS enterprise database environments that support the agency?s mission of economic and social science research. The enrollee will ensure mission-critical systems, data dissemination processes, and data platforms remain aligned with USDA and federal standards. The functions of this role will include analyzing and enhancing complex data environments, developing operational standards and procedures, coordinating across multiple technologies for high-impact projects, conducting advanced troubleshooting, implementing automation, supporting cloud integration, and improving database management practices to strengthen the production and delivery of ERS data products. The enrollee shall not sign federal documents, authorize the use of federal funds, nor initiate or conduct federally funded research projects. The enrollee shall not author articles for publication as a federal employee, nor coordinate scientific research between the Government and private industry. The enrollee shall not present themselves as a Government employee or Government representative at meetings both foreign and domestic or when coordinating federal agencies? areas of research. The enrollee shall not make decisions on federally based research on behalf of Government policy makers, and the enrollee shall not supervise any Government employees. Lead the architecture, design, and enhancement of ERS enterprise database environments to ensure optimal performance, reliability, and support for mission-critical research and data dissemination. 35%Create, maintain, and ensure recovery of physical databases, including server software installation, database object creation, security implementation, data loading, and execution of backup and recovery activities. 35%Develop database application solutions that support ERS research and publishing needs, including designing data structures, interrelationships, storage requirements, and data processing code. 15%Provide systems analysis to improve database performance and efficacy, monitoring usage, evaluating procedural activities, identifying weaknesses, and recommending enhancements to data structures, security, and access methods. 15% - Other Physical requirements: Office job Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions of this position. NEW Solutions is committed to promoting equal opportunity and to an environment free from discrimination and harassment in any form administering Experienced Worker Programs under cooperative agreements with federal agencies. It is NEW Solutions' policy to comply with all applicable laws that provide equal opportunity and to prohibit unlawful discrimination in enrolling participants in the federal programs. We need to remove boilerplate: equal opportunity statements, etc. The "Other Physical requirements" includes office job and reasonable accommodations. Also the equal opportunity statement is boilerplate; we should remove it. Also the "PLEASE NOTE" about enrollee not being federal employee is substantive? It's about the nature of the position; maybe keep as part of description. The "Positions listed here do not guarantee employment for any definite period." etc. Might be considered boilerplate but it's specific to the program; we can keep as part of description. We need to decide sections: Likely we will have sections: About the role (maybe a summary), Responsibilities (duties), Requirements/Qualifications (qualifications), Skills (maybe list Windows, MS Word, MS Excel), Benefits? Not given. Pay? Wage/Hr: $52.00 given. Schedule? Hours/Week: 40 given. So we have Pay and Schedule specifics. According to rules: include Pay and Schedule sections only if posting actually states them. Yes, we have wage/hours. So we should include Pay and Schedule sections. Benefits: not stated, so omit. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info: include location, program, wage, hours, minimum age, remote option, description of NEW Solutions, enrollee nature, qualifications, duties with percentages, physical requirements (office job, reasonable accommodations). Also maybe include that position open until filled. We need to format using
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide what constitutes a list. Duties have percentages and bullet-like statements; we can make a
with each duty as - . Requirements: maybe list qualifications: Minimum 5 years experience OR BA/BS, Experience with Windows, MS Word, MS Excel. Could be a list.
Skills: maybe list Windows, MS Word, MS Excel as skills.
But we need to avoid duplication: qualifications and skills may overlap. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section "Requirements". Or have separate sections if distinct. Let's think: Qualifications: experience/degree. Skills: specific software. Could be separate but might be thin. Better to combine into "Requirements" section covering both experience/degree and technical skills.
We need to include About the role: maybe a summary paragraph describing the role, mission, remote option, etc.
Responsibilities: duties with percentages.
Requirements: qualifications + skills.
Pay: wage/hour.
Schedule: hours/week.
Also maybe include Location, Program, Minimum Age, Remote option as part of About the role or a separate section like "Details". But we have no heading for Details; we could embed in About the role paragraph.
We must not repeat job title as heading. So no
Database Technical Expert
. Good.
We must not put Job ID/requisition numbers as headings; we can fold minor metadata into a short or drop it. So we can include ID, Location, Program, Minimum Age, Remote option in a paragraph under About the role or a separate "Details" section but we need a heading; maybe "Details" is okay as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists examples but not exhaustive; we could use other headings if needed but better to stick to those. So we could put location, program, etc inside About the role paragraph.
Thus structure:
About the role
... includes location, program, wage? Actually wage goes to Pay section. So About the role: description of NEW Solutions, remote option, enrollee nature, mission, etc.
Responsibilities
- Lead the architecture, design, and enhancement of ERS enterprise database environments to ensure optimal performance, reliability, and support for mission-critical research and data dissemination.
- Create, maintain, and ensure recovery of physical databases, including server software installation, database object creation, security implementation, data loading, and execution of backup and recovery activities. (35%)
- Develop database application solutions that support ERS research and publishing needs, including designing data structures, interrelationships, storage requirements, and data processing code. (35%)
- Provide systems analysis to improve database performance and efficacy, monitoring usage, evaluating procedural activities, identifying weaknesses, and recommending enhancements to data structures, security, and access methods. (15%)
- Analyzing and enhancing complex data environments, developing operational standards and procedures, coordinating across multiple technologies for high-impact projects, conducting advanced troubleshooting, implementing automation, supporting cloud integration, and improving database management practices to strengthen the production and delivery of ERS data products.
- The enrollee shall not sign federal documents, authorize the use of federal funds, nor initiate or conduct federally funded research projects.
- The enrollee shall not author articles for publication as a federal employee, nor coordinate scientific research between the Government and private industry.
- The enrollee shall not present themselves as a Government employee or Government representative at meetings both foreign and domestic or when coordinating federal agencies? areas of research.
- The enrollee shall not make decisions on federally based research on behalf of Government policy makers, and the enrollee shall not supervise any Government employees.
But we have some duplication: the first bullet (Lead architecture...) is similar to later bullet list. Might combine. However we need to preserve all substantive info; we can keep both but maybe combine to avoid redundancy. The original text: "Lead the architecture, design, and enhancement of ERS enterprise database environments to ensure optimal performance, reliability, and support for mission-critical research and data dissemination." Then percentages: 35% Create..., 35% Develop..., 15% Provide..., then earlier paragraph: "The functions of this role will include analyzing and enhancing complex data environments, developing operational standards and procedures, coordinating across multiple technologies for high-impact projects, conducting advanced troubleshooting, implementing automation, supporting cloud integration, and improving database management practices to strengthen the production and delivery of ERS data products." That seems like a summary of duties. We could keep that as a separate bullet.
We need to avoid too many thin sections; but responsibilities can be a list.
Now Requirements:
Requirements
- Minimum of 5 years of experience in Database Management field OR a BA/BS degree.
- Experience with Windows, MS Word, and MS Excel.
We could also include Minimum Age 55 as a requirement? It's a condition of the program; maybe include in About the role or Requirements. Since it's a eligibility criterion, we could add to Requirements: "Applicants must be age 55 or older." But the instruction says preserve all substantive info; we should include
for prose. We need to decide what constitutes a list. Duties have percentages and bullet-like statements; we can make a
- with each duty as
- . Requirements: maybe list qualifications: Minimum 5 years experience OR BA/BS, Experience with Windows, MS Word, MS Excel. Could be a list.
Skills: maybe list Windows, MS Word, MS Excel as skills.
But we need to avoid duplication: qualifications and skills may overlap. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section "Requirements". Or have separate sections if distinct. Let's think: Qualifications: experience/degree. Skills: specific software. Could be separate but might be thin. Better to combine into "Requirements" section covering both experience/degree and technical skills.
We need to include About the role: maybe a summary paragraph describing the role, mission, remote option, etc.
Responsibilities: duties with percentages.
Requirements: qualifications + skills.
Pay: wage/hour.
Schedule: hours/week.
Also maybe include Location, Program, Minimum Age, Remote option as part of About the role or a separate section like "Details". But we have no heading for Details; we could embed in About the role paragraph.
We must not repeat job title as heading. So no
Database Technical Expert
. Good. We must not put Job ID/requisition numbers as headings; we can fold minor metadata into a shortor drop it. So we can include ID, Location, Program, Minimum Age, Remote option in a paragraph under About the role or a separate "Details" section but we need a heading; maybe "Details" is okay as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists examples but not exhaustive; we could use other headings if needed but better to stick to those. So we could put location, program, etc inside About the role paragraph. Thus structure:
About the role
... includes location, program, wage? Actually wage goes to Pay section. So About the role: description of NEW Solutions, remote option, enrollee nature, mission, etc.
Responsibilities
- Lead the architecture, design, and enhancement of ERS enterprise database environments to ensure optimal performance, reliability, and support for mission-critical research and data dissemination.
- Create, maintain, and ensure recovery of physical databases, including server software installation, database object creation, security implementation, data loading, and execution of backup and recovery activities. (35%)
- Develop database application solutions that support ERS research and publishing needs, including designing data structures, interrelationships, storage requirements, and data processing code. (35%)
- Provide systems analysis to improve database performance and efficacy, monitoring usage, evaluating procedural activities, identifying weaknesses, and recommending enhancements to data structures, security, and access methods. (15%)
- Analyzing and enhancing complex data environments, developing operational standards and procedures, coordinating across multiple technologies for high-impact projects, conducting advanced troubleshooting, implementing automation, supporting cloud integration, and improving database management practices to strengthen the production and delivery of ERS data products.
- The enrollee shall not sign federal documents, authorize the use of federal funds, nor initiate or conduct federally funded research projects.
- The enrollee shall not author articles for publication as a federal employee, nor coordinate scientific research between the Government and private industry.
- The enrollee shall not present themselves as a Government employee or Government representative at meetings both foreign and domestic or when coordinating federal agencies? areas of research.
- The enrollee shall not make decisions on federally based research on behalf of Government policy makers, and the enrollee shall not supervise any Government employees.
Requirements
- Minimum of 5 years of experience in Database Management field OR a BA/BS degree.
- Experience with Windows, MS Word, and MS Excel.