Senior Tech Product Manager
Optum · Barrington, RI · 1 mo ago
$92k–$164k/yrFull-time
We need to produce HTML fragment with sections: About the role? The posting includes introductory paragraph about Optum, then description of role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse content.
First, we have an introductory paragraph: "Optum is a global organization ...". That could be "About the role" or maybe "About Optum". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section with that intro.
Then "Primary Responsibilities" list: bullet points. So Responsibilities section.
Then "You'll be rewarded and recognized ..." maybe part of Benefits? Actually it's about rewards and recognition, could be Benefits. But we also have explicit Benefits paragraph later: "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution". So Benefits section.
Then "Required Qualifications" list: Required Qualifications.
Then "Preferred Qualifications" list: Preferred Qualifications.
Then "All Telecommuters will be required to adhere..." maybe part of Schedule? Actually telecommuting flexibility: "You will enjoy the flexibility to telecommute* from anywhere within the U.S." That's Schedule/Work arrangement. Could be Schedule section.
Pay: "The salary for this role will range from $91,700 to $163,700 annually based on full-time employment." Also earlier: "Pay is based on several factors ...". So Pay section.
Skills: maybe we can extract from qualifications: experience with EDI ANSI X12, SAP EDI, markup languages JSON/XML, Axway B2Bi, MS Office Excel/PowerPivot. Those are skills. Could put under Skills.
We need to avoid duplication. Also we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out the EEO statement, drug test, etc. Also remove "Application Deadline:" etc. Also remove "#RPO #GREEN". Also remove "All Telecommuters will be required to adhere to UnitedHealth Group's Telecommuter Policy." maybe keep as part of Schedule? But it's a policy statement; maybe we can keep as part of Schedule but it's not specific content? It's a requirement. Might keep but it's not boilerplate? It's a policy statement; could be considered boilerplate? It's specific to telecommuting. Might keep as part of Schedule.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details: e.g., "Establish and support AS2/SFTP connections", etc.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section with that intro.
Then "Primary Responsibilities" list: bullet points. So Responsibilities section.
Then "You'll be rewarded and recognized ..." maybe part of Benefits? Actually it's about rewards and recognition, could be Benefits. But we also have explicit Benefits paragraph later: "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution". So Benefits section.
Then "Required Qualifications" list: Required Qualifications.
Then "Preferred Qualifications" list: Preferred Qualifications.
Then "All Telecommuters will be required to adhere..." maybe part of Schedule? Actually telecommuting flexibility: "You will enjoy the flexibility to telecommute* from anywhere within the U.S." That's Schedule/Work arrangement. Could be Schedule section.
Pay: "The salary for this role will range from $91,700 to $163,700 annually based on full-time employment." Also earlier: "Pay is based on several factors ...". So Pay section.
Skills: maybe we can extract from qualifications: experience with EDI ANSI X12, SAP EDI, markup languages JSON/XML, Axway B2Bi, MS Office Excel/PowerPivot. Those are skills. Could put under Skills.
We need to avoid duplication. Also we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out the EEO statement, drug test, etc. Also remove "Application Deadline:" etc. Also remove "#RPO #GREEN". Also remove "All Telecommuters will be required to adhere to UnitedHealth Group's Telecommuter Policy." maybe keep as part of Schedule? But it's a policy statement; maybe we can keep as part of Schedule but it's not specific content? It's a requirement. Might keep but it's not boilerplate? It's a policy statement; could be considered boilerplate? It's specific to telecommuting. Might keep as part of Schedule.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details: e.g., "Establish and support AS2/SFTP connections", etc.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat the job title as a heading. The job title is "EDI Technical Support Specialist". Not to be used as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's structure:
About the role
Optum is a global organization that delivers care, aided by technology, to help millions of people live healthier lives. The work you do with our team will directly improve health outcomes by connecting people with the care, pharmacy benefits, data and resources they need to feel their best. Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities. Come make an impact on the communities we serve as you help us advance health optimization on a global scale. Join us to start Caring. Connecting. Growing together. The EDI Technical Support Specialist will contribute to the Optum Rx Technology team performing analysis and support of all EDI activities between internal users, customers, distributors, and software partners. The person in this role will collaborate with other information technology team members, operations, customer support, and finance team members towards building, maintaining, and monitoring EDI solutions across the SAP ERP and Axway platforms as well as related business processes. You will enjoy the flexibility to telecommute* from anywhere within the U.S. as you take on some tough challenges.
Then Responsibilities:
Responsibilities
- Establish and support AS2/SFTP connections
- Assist in the design, development, testing, implementation, and training of supported EDI formats
- Establish effective communication with clients and trading partners in a fast-paced, deadline-driven environment
- Act as a liaison with Supply Chain customers, trading partners, and software vendors
- Proactively monitor EDI system health and provide timely responses to alerts
- Support data validation and delivery of reports
- Assist in creating and maintaining detailed documentation and process flows for all EDI processes
- Work with appropriate internal staff and third parties to resolve and document tickets in specialized areas requiring their skills
- Use enterprise-approved AI tools to streamline workflows, automate tasks, and drive continuous improvement
- Evaluate emerging trends to inform solution design and strategic innovation
- Leverage enterprise-approved AI tools to streamline workflows, automate tasks, and drive continuous improvement
Note duplicate AI tools lines appear twice; we should keep both? It's duplicated in posting. We should not repeat duplicated lines? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate the AI tools line. Keep only one.
Thus Responsibilities list will have one "Use enterprise-approved AI tools to streamline workflows, automate tasks, and drive continuous improvement". Also we have "Evaluate emerging trends to inform solution design and strategic innovation". Good.
Now Requirements? The posting has "Required Qualifications" and "Preferred Qualifications". Could combine into Requirements section? But we have separate headings: Requirements, Qualifications, Skills. We need to decide.
We could have:
Requirements
5+ years of experience in EDI ANSI X12 support and development
5+ years of experience in SAP EDI creation and processing
5+ years of experience with markup languages such as JSON and XML
4+ years of experience with Axway B2Bi Software
4+ years of experience in Axway B2Bi EDI development
Advanced level of proficiency in MS Office skills, particularly with Excel and PowerPivot
But these are lists; better to use .
Similarly Preferred Qualifications as separate section maybe under Qualifications? The instruction: Use headings like Requirements, Qualifications, Skills. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and then Skills maybe from those? But we already have skills in Required Qualifications (MS Office). Could also separate Skills section for technical skills like programming languages, ServiceNow, etc. However we risk duplication.
Better to follow the posting: Have Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Then maybe Skills not needed if covered. But we need to decide if we should include Skills section. The posting includes "Preferred Qualifications" includes experience with programming languages such as C++ or Java, ServiceNow, reports, distribution/3PL inventory practices, SAP S/4 PO/SO processing, ability to manage multiple projects, attention to detail, flexibility. Those could be considered Skills. But we could put them under Qualifications (Preferred). The instruction says we can have Skills section; but we should only include if posting has real specific content for it. The posting does have specific content under Preferred Qualifications that could be considered skills. However we already have a Qualifications section for Preferred Qualifications. If we also add Skills, we would duplicate content. Better to not add Skills if we already have Qualifications covering both required and preferred? But we have separate headings: Requirements and Qualifications. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications. Then we don't need Skills.
Pay section: we have salary range and statement about pay based on factors.
Schedule section: telecommuting flexibility and policy.
Benefits section: comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution.
We also have earlier sentence: "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear directions on what it takes to succeed in your role as well as provide development for other roles you may be interested in." That's about rewards and recognition, could be part of Benefits. We'll include that in Benefits.
Now we need to remove boilerplate: EEO statement, drug test, etc. Also remove "Application Deadline:" etc. Also remove "#RPO #GREEN". Also remove "We comply with all minimum wage laws as applicable." maybe keep? It's a legal statement; could be considered boilerplate. Probably remove. Also remove "Pursuant to the San Francisco Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records." That's EEO/legal; remove. Also remove "At UnitedHealth Group, our mission is to help people live healthier lives and make the health system work better for everyone." That's mission statement; could be considered boilerplate? It's somewhat generic but appears in posting; maybe we should keep? It's not about the role specifically. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement might be considered boilerplate but not explicitly listed. However it's generic; but it's part of the introductory fluff. The earlier introductory paragraph already includes similar content about Optum's mission. The mission statement repeats similar ideas. Might be considered duplicated? Safer to remove it.
Also remove "We believe everyone-of every race, gender, sexuality, age, location, and income-deserves the opportunity to live their healthiest life." etc. That's EEO/diversity statement; remove.
Also remove "We are committed to mitigating our impact on the environment and enabling and delivering equitable care that addresses health disparities and improves health outcomes - an enterprise priority reflected in our mission." Remove.
Also remove "UnitedHealth Group is an Equal Employment Opportunity employer under applicable law..." Remove.
Also remove "UnitedHealth Group is a drug - free workplace. Candidates are required to pass a drug test before beginning employment." Remove.
Now we need to ensure we keep all substantive info: The telecommute flexibility sentence, the policy sentence maybe keep as part of Schedule.
Now let's craft HTML.
We'll have:
About the role
...
Responsibilities
...
Requirements
...
Qualifications
...
Benefits
...
Pay
...
Schedule
...
Check for duplication: In Benefits we need to include "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear directions on what it takes to succeed in your role as well as provide development for other roles you may be interested in." plus "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements)." Also "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." That's also benefits. We'll combine.
Pay: "Pay is based on several factors including but not limited to local labor markets, education, work experience
for prose. We must not repeat the job title as a heading. The job title is "EDI Technical Support Specialist". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's structure:
About the role
Optum is a global organization that delivers care, aided by technology, to help millions of people live healthier lives. The work you do with our team will directly improve health outcomes by connecting people with the care, pharmacy benefits, data and resources they need to feel their best. Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities. Come make an impact on the communities we serve as you help us advance health optimization on a global scale. Join us to start Caring. Connecting. Growing together. The EDI Technical Support Specialist will contribute to the Optum Rx Technology team performing analysis and support of all EDI activities between internal users, customers, distributors, and software partners. The person in this role will collaborate with other information technology team members, operations, customer support, and finance team members towards building, maintaining, and monitoring EDI solutions across the SAP ERP and Axway platforms as well as related business processes. You will enjoy the flexibility to telecommute* from anywhere within the U.S. as you take on some tough challenges.
Then Responsibilities:Responsibilities
- Establish and support AS2/SFTP connections
- Assist in the design, development, testing, implementation, and training of supported EDI formats
- Establish effective communication with clients and trading partners in a fast-paced, deadline-driven environment
- Act as a liaison with Supply Chain customers, trading partners, and software vendors
- Proactively monitor EDI system health and provide timely responses to alerts
- Support data validation and delivery of reports
- Assist in creating and maintaining detailed documentation and process flows for all EDI processes
- Work with appropriate internal staff and third parties to resolve and document tickets in specialized areas requiring their skills
- Use enterprise-approved AI tools to streamline workflows, automate tasks, and drive continuous improvement
- Evaluate emerging trends to inform solution design and strategic innovation
- Leverage enterprise-approved AI tools to streamline workflows, automate tasks, and drive continuous improvement
Requirements
5+ years of experience in EDI ANSI X12 support and development
5+ years of experience in SAP EDI creation and processing
5+ years of experience with markup languages such as JSON and XML
4+ years of experience with Axway B2Bi Software
4+ years of experience in Axway B2Bi EDI development
Advanced level of proficiency in MS Office skills, particularly with Excel and PowerPivot
But these are lists; better to use- .
Similarly Preferred Qualifications as separate section maybe under Qualifications? The instruction: Use headings like Requirements, Qualifications, Skills. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and then Skills maybe from those? But we already have skills in Required Qualifications (MS Office). Could also separate Skills section for technical skills like programming languages, ServiceNow, etc. However we risk duplication.
Better to follow the posting: Have Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Then maybe Skills not needed if covered. But we need to decide if we should include Skills section. The posting includes "Preferred Qualifications" includes experience with programming languages such as C++ or Java, ServiceNow, reports, distribution/3PL inventory practices, SAP S/4 PO/SO processing, ability to manage multiple projects, attention to detail, flexibility. Those could be considered Skills. But we could put them under Qualifications (Preferred). The instruction says we can have Skills section; but we should only include if posting has real specific content for it. The posting does have specific content under Preferred Qualifications that could be considered skills. However we already have a Qualifications section for Preferred Qualifications. If we also add Skills, we would duplicate content. Better to not add Skills if we already have Qualifications covering both required and preferred? But we have separate headings: Requirements and Qualifications. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications. Then we don't need Skills.
Pay section: we have salary range and statement about pay based on factors.
Schedule section: telecommuting flexibility and policy.
Benefits section: comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution.
We also have earlier sentence: "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear directions on what it takes to succeed in your role as well as provide development for other roles you may be interested in." That's about rewards and recognition, could be part of Benefits. We'll include that in Benefits.
Now we need to remove boilerplate: EEO statement, drug test, etc. Also remove "Application Deadline:" etc. Also remove "#RPO #GREEN". Also remove "We comply with all minimum wage laws as applicable." maybe keep? It's a legal statement; could be considered boilerplate. Probably remove. Also remove "Pursuant to the San Francisco Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records." That's EEO/legal; remove. Also remove "At UnitedHealth Group, our mission is to help people live healthier lives and make the health system work better for everyone." That's mission statement; could be considered boilerplate? It's somewhat generic but appears in posting; maybe we should keep? It's not about the role specifically. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement might be considered boilerplate but not explicitly listed. However it's generic; but it's part of the introductory fluff. The earlier introductory paragraph already includes similar content about Optum's mission. The mission statement repeats similar ideas. Might be considered duplicated? Safer to remove it.
Also remove "We believe everyone-of every race, gender, sexuality, age, location, and income-deserves the opportunity to live their healthiest life." etc. That's EEO/diversity statement; remove.
Also remove "We are committed to mitigating our impact on the environment and enabling and delivering equitable care that addresses health disparities and improves health outcomes - an enterprise priority reflected in our mission." Remove.
Also remove "UnitedHealth Group is an Equal Employment Opportunity employer under applicable law..." Remove.
Also remove "UnitedHealth Group is a drug - free workplace. Candidates are required to pass a drug test before beginning employment." Remove.
Now we need to ensure we keep all substantive info: The telecommute flexibility sentence, the policy sentence maybe keep as part of Schedule.
Now let's craft HTML.
We'll have:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
...
Pay
...
Schedule
...
Check for duplication: In Benefits we need to include "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear directions on what it takes to succeed in your role as well as provide development for other roles you may be interested in." plus "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements)." Also "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." That's also benefits. We'll combine. Pay: "Pay is based on several factors including but not limited to local labor markets, education, work experience