OpenText Exstream Developer
or drop. The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
with Position Type, Location, Experience, Clearance. We need sections only when posting has real specific content. We have: - Position Summary (we can call it About the role) - Key Responsibilities (Responsibilities) - Required Qualifications (Requirements or Qualifications) - Preferred Qualifications (maybe Skills? but we could include as Qualifications or separate Skills? The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About the role = Position Summary. Responsibilities = Key Responsibilities. Requirements = Required Qualifications. Qualifications maybe Preferred Qualifications? Or we could put Preferred Qualifications under Skills? But better to have Qualifications section for both required and preferred? However they said prefer a few substantive sections over many thin ones. Could combine Required and Preferred into one Qualifications section, but we need to preserve all info. Could have two subsections? But we cannot add extra headings not in list. Could use
- inside Qualifications to list both required and preferred, maybe with labels. But we need to preserve detail; we can include both required and preferred bullet points under Qualifications.
Benefits: we have Benefits section.
Pay and Schedule: not mentioned, so omit.
Thus sections: About the role, Responsibilities, Qualifications, Benefits.
We also may include a short
- inside
- .
Now Qualifications: we need to include Required Qualifications and Preferred Qualifications.
Required Qualifications list:
- 7+ years of related professional experience.
- Demonstrated hands-on experience creating notices using OpenText Exstream.
- Experience working with technical and business stakeholders to understand and implement requirements.
- Ability to work effectively with client and project teams across multiple geographic locations.
- Strong analytical, problem-solving, and troubleshooting skills.
- Excellent written and verbal communication skills.
- Bachelor's degree from an accredited college or university.
- Education substitution: A high school diploma may be accepted with an additional four years of related experience.
Preferred Qualifications list:
- Experience with OpenText xPression, particularly migration or conversion of notices, forms, or templates from xPression to Exstream.
- Current IRS MBI.
- Experience reviewing, analyzing, and translating business and technical requirements.
- Previous experience supporting federal government projects or environments.
- Candidates Must Be Either a U.S. Citizen, or Permanent Resident who has lived in the United States for at least three years.
We can combine into one Qualifications section, maybe with subheadings? But we cannot add extra headings not in list. Could we embed two
- Coordinate and engage with technical and business stakeholders to gather requirements, conduct analysis, validate requirements, produce user stories, diagrams, process flows, and other outputs.
- Create Exstream applications and pages using customer supplied specifications
- Migrate notices/forms/templates from xPression to Exstream
- Assist in the creation or redesign, and testing of IRS notices for multiple output formats that are 508 compliant.
- Create, update, and manage high-quality project documentation that meets IRS acceptance criteria, use cases, or executive briefings. Create and review reports.
- Work with teams dispersed across geographical sites
- Foster collaboration and communication between team members on technical issues, on process improvements, and in addressing and escalating project risks and issues
- Provide status reports, attend meetings and take/distribute minutes
- 7+ years of related professional experience.
- Demonstrated hands-on experience creating notices using OpenText Exstream.
- Experience working with technical and business stakeholders to understand and implement requirements.
- Ability to work effectively with client and project
- with a preceding
indicating Required and Preferred? That's okay. Now Benefits: list: - paid holidays and paid time off - medical insurance including health, vision, dental insurance - 401K matching - Flexible Spending Account - flexible schedules, as per business needs. - training and professional certification plans that benefit the employee. We need to preserve exactly as in text: "We offer a competitive benefits package that includes paid holidays and paid time off, medical insurance including health, vision, dental insurance, 401K matching, Flexible Spending Account and flexible schedules, as per business needs. We also work with our employees on training and professional certification plans that benefit the employee." We can turn into list items. Now ensure we don't include EEO boilerplate. Now output HTML. Let's craft:
About the role
Position Type: Full-Time. Location: Remote / New Carrollton, MD. Experience: 7+ years of related experience. Clearance: Must be able to obtain and maintain an IRS Minimum Background Investigation (MBI); current IRS MBI strongly preferred.
We are seeking an experienced OpenText Exstream Developer to support a federal client in the development, modernization, and migration of customer notices, forms, and templates. The developer will be responsible for creating applications and pages using OpenText Exstream, as well as supporting the migration of existing notices, forms, and templates from OpenText xPression to OpenText Exstream. The role will work closely with technical and business stakeholders to gather and analyze requirements, develop and test Section 508-compliant notices, troubleshoot technical issues, and produce supporting project documentation. The ideal candidate will have strong hands-on OpenText Exstream development experience, experience working with complex document and notice-generation solutions, excellent communication skills, and the ability to collaborate effectively with geographically dispersed technical and business teams.
Headquartered in Leesburg, Virginia, Zenius Corporation is a HUBZone-certified small business. Zenius specializes in providing Grants Management, IT Modernization, Acquisition Management, and Financial Management services to Federal agencies. Zenius is selected by Inc 5000 as one of the fastest-growing companies in the DC Metro Area, awarded in 2025, 2024, 2021, and 2020. Zenius is also listed by Financial Times as one of the fastest-growing companies in the Americas in 2021. Zenius is an awardee of 2019 Best of Leesburg winner (Business Management Consultant category).
Responsibilities
Qualifications
Required Qualifications:
for metadata: Position Type: Full-Time; Location: Remote / New Carrollton, MD; Experience: 7+ years; Clearance: Must be able to obtain and maintain an IRS Minimum Background Investigation (MBI); current IRS MBI strongly preferred. We must not include boilerplate like EEO, etc. Remove Equal Opportunity Employer text. Also remove About The Company? The instruction: we can include About the role heading for Position Summary; About The Company could be considered extra but not in allowed headings list. Could we include it under About the role? Probably not; we should drop About The Company as it's not required heading and may be considered boilerplate? It's substantive but not in allowed headings list; we could incorporate into About the role? But the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says use those for section headings; likely we should stick to those. So we should not add a heading for About The Company. We could incorporate company description into About the role paragraph? Might be okay but risk of adding unrelated content. Better to drop it as it's not required; but we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop company description if it's substantive. However we could include it as a
without a heading, maybe after About the role? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but they gave examples; but safer to stick to those. We could embed company description in a
under About the role section (since it's about the role/company). That would preserve info. Thus About the role section will contain Position Summary plus company description. Now Benefits: we have benefits list. Now we need to output only HTML fragment, no /, no markdown. Let's craft:
About the role
Position Type: Full-Time. Location: Remote / New Carrollton, MD. Experience: 7+ years of related experience. Clearance: Must be able to obtain and maintain an IRS Minimum Background Investigation (MBI); current IRS MBI strongly preferred.
[Position Summary text]... [About The Company text]...
But we need to preserve the Position Summary exactly: "We are seeking an experienced OpenText Exstream Developer to support a federal client in the development, modernization, and migration of customer notices, forms, and templates. The developer will be responsible for creating applications and pages using OpenText Exstream, as well as supporting the migration of existing notices, forms, and templates from OpenText xPression to OpenText Exstream. The role will work closely with technical and business stakeholders to gather and analyze requirements, develop and test Section 508-compliant notices, troubleshoot technical issues, and produce supporting project documentation. The ideal candidate will have strong hands-on OpenText Exstream development experience, experience working with complex document and notice-generation solutions, excellent communication skills, and the ability to collaborate effectively with geographically dispersed technical and business teams." Then About The Company: "Headquartered in Leesburg, Virginia, Zenius Corporation is a HUBZone-certified small business. Zenius specializes in providing Grants Management, IT Modernization, Acquisition Management, and Financial Management services to Federal agencies. Zenius is selected by Inc 5000 as one of the fastest-growing companies in the DC Metro Area, awarded in 2025, 2024, 2021, and 2020. Zenius is also listed by Financial Times as one of the fastest-growing companies in the Americas in 2021. Zenius is an awardee of 2019 Best of Leesburg winner (Business Management Consultant category)." We can combine into one paragraph or two. Now Responsibilities: list each bullet. We need to preserve all bullet points exactly as given. Key Responsibilities list: - Coordinate and engage with technical and business stakeholders to gather requirements, conduct analysis, validate requirements, produce user stories, diagrams, process flows, and other outputs. - Create Exstream applications and pages using customer supplied specifications - Migrate notices/forms/templates from xPression to Exstream - Assist in the creation or redesign, and testing of IRS notices for multiple output formats that are 508 compliant. - Create, update, and manage high-quality project documentation that meets IRS acceptance criteria, use cases, or executive briefings. Create and review reports. - Work with teams dispersed across geographical sites - Foster collaboration and communication between team members on technical issues, on process improvements, and in addressing and escalating project risks and issues - Provide status reports, attend meetings and take/distribute minutes We need to put each as