Senior STIBO Software Developer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a 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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
Content includes:
- Intro paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time."
- Position Summary: "CVS Health Digital is looking for hands-on, passionate people who want to join a high energy and growing team to make a difference in customers’ lives and who want to be on the forefront of digital innovation that aims to reinvent what a pharmacy and a health care company can be in the digital world. Currently, we are hiring for an experienced Senior STIBO Software Developer to support enterprise Master Data Management (MDM) initiatives in a fast-paced retail and healthcare environment. This Senior Developer focuses on building scalable data solutions to manage product, vendor, and customer master data across omnichannel systems while ensuring data quality, governance, and consistency."
- Expectations For The Role: bullet list (actually sentences). It includes many responsibilities: invest 15% mentoring, 15% working with product, 70% technical SME, develop and support STIBO STEP solutions, workflows, integrations, ensure data quality, governance, platform performance, troubleshoot and resolve complex platform and data issues, drive delivery through accurate estimates, ownership, communication, support production operations, SaaS upgrades, continuous improvements, design, develop, configure and customize the Stibo STEP platform, including workflows, WebUI interfaces, attributes and validation rules, support quarterly SaaS upgrades and release impact reviews, implement data governance, stewardship, and data quality frameworks, optimize platform performance, troubleshoot issues, and provide production support.
- Required Qualifications: list: 5+ years MDM/PIM development experience, 5+ years hands-on Stibo STEP development and administration experience, 3+ years experience with CI/CD tools including Azure DevOps, Jenkins and Git, 3+ years experience with Azure (preferred) or GCP cloud platforms.
- Preferred Qualifications: list: Experience with REST/SOAP APIs, XML, JSON, Kafka and Informatica, Retail or healthcare industry experience, Knowledge of product lifecycle and catalog management, Experience supporting omnichannel retail environments, Knowledge of supplier/vendor onboarding and healthcare regulatory data handling, Experience using AI for data maintenance in STEP, Strong knowledge of JavaScript, Web UI development, SQL and data modeling, Ability to drive master data governance and product/vendor lifecycle management, Strong collaboration and problem-solving skills.
- EDUCATION: Bachelor’s degree or equivalent experience (HS diploma + 4 years relevant experience)
- Business Overview: paragraphs about CVS Health purpose, Heart At Work Behaviors, diversity, inclusion, etc. This is generic corporate fluff but still substantive? Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Business Overview is not exactly EEO but it's generic corporate mission. Might be considered okay to keep as "About the role" or "Overview". However we need to avoid filler. It's not filler; it's specific to CVS Health. Could be included.
- Anticipated Weekly Hours 40, Time Type Full time: This is schedule info. Should we include a Schedule section? The posting states Anticipated Weekly Hours 40, Time Type Full time. That's specific schedule info. So we can include a Schedule section with that.
- Pay Range: The posting includes Pay Range: The Typical Pay Range For This Role Is $83,430.00 - $222,480.00. Also mentions bonus etc. So we can include Pay section.
- Benefits: "Great Benefits For Great People" paragraph describing benefits: medical, dental, vision, paid time off, retirement savings, wellness programs, etc. So we can include Benefits section.
- Additional details: application window close date 10/30/2026, Qualified applicants with arrest or conviction records will be considered... That's EEO/legal boilerplate? It's about hiring practice; might be considered legal boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is about arrest/conviction records, which is a kind of EEO statement. Likely should be removed.
- Also "We anticipate the application window for this opening will close on: 10/30/2026" is application instruction? It's a date; maybe we can keep as minor metadata in a short
or drop it. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short paragraph at end with that info, but not as a heading.
- Also "Our people fuel our future..." is part of benefits section? Already covered.
We need to avoid duplication. We'll produce sections: About the role (intro + position summary maybe), Responsibilities (Expectations For The Role), Qualifications (maybe combine Required and Preferred? Could separate but they said prefer few substantive sections over many thin ones. Could combine Required and Preferred into Qualifications section with subheadings? But we only allowed
headings; we could have multiple sections: Responsibilities, Qualifications, Benefits, Pay, Schedule. Also maybe Education as part of Qualifications.
We need to decide.
Let's extract substantive content:
About the role: The introductory paragraph and position summary.
Responsibilities: The Expectations For The Role bullet list.
Qualifications: Required Qualifications + Preferred Qualifications + Education.
Benefits: Great Benefits For Great People paragraph.
Pay: Pay Range paragraph.
Schedule: Anticipated Weekly Hours 40, Time Type Full time.
We should not include EEO boilerplate.
We need to format lists with - . For responsibilities, each sentence could be a list item. For qualifications, each bullet.
We need to preserve all substantive information; do not invent or summarize away detail. So we must keep each point exactly as written (or close). We can rephrase slightly? Probably better to keep the wording.
Let's list responsibilities exactly as in the posting:
- Invest 15% of your time mentoring less experienced engineers
- Invest 15% of your efforts working alongside Product as well as stakeholders on other teams
- Invest 70% of your time using your technical SME and coding skills in strategic planning, scoping, delivery, and working alongside the Senior Engineering Manager
- Develop and support STIBO STEP solutions, workflows, and integrations
- Ensure data quality, governance, and platform performance
- Troubleshoot and resolve complex platform and data issues
- Drive delivery through accurate estimates, ownership, and communication
- Support production operations, SaaS upgrades, and continuous improvements
- Design, develop, configure and customize the Stibo STEP platform, including workflows, WebUI interfaces, attributes and validation rules
- Support quarterly SaaS upgrades and release impact reviews
- Implement data governance, stewardship, and data quality frameworks
- Optimize platform performance, troubleshoot issues, and provide production support
Note: Some duplicates: troubleshoot appears twice; we keep both as they are separate points.
Now Required Qualifications:
- 5+ years of MDM/PIM development experience
- 5+ years of hands-on Stibo STEP development and administration experience
- 3+ years of experience with CI/CD tools including Azure DevOps, Jenkins and Git
- 3+ years of experience with Azure (preferred) or GCP cloud platforms
Preferred Qualifications:
- Experience with REST/SOAP APIs, XML, JSON, Kafka and Informatica
- Retail or healthcare industry experience
- Knowledge of product lifecycle and catalog management
- Experience supporting omnichannel retail environments
- Knowledge of supplier/vendor onboarding and healthcare regulatory data handling
- Experience using AI for data maintenance in STEP
- Strong knowledge of JavaScript, Web UI development, SQL and data modeling
- Ability to drive master data governance and product/vendor lifecycle management
- Strong collaboration and problem-solving skills
Education:
- Bachelor’s degree or equivalent experience (HS diploma + 4 years relevant experience)
Benefits: The paragraph: "Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments."
We need to keep that as prose (
). Could also list benefits as list? The instruction says use
- for any list of duties/requirements/benefits. Benefits are listed as items: medical, dental, vision coverage, paid time off, retirement savings options, wellness programs, and other resources. Could make a list. But the paragraph also includes introductory sentences. We could keep the paragraph and then a list for the benefits items. However to avoid duplication, we could just make a list of benefits and omit the intro sentences? But we must preserve ALL substantive information; we cannot drop the intro sentences. So we need to keep them. We could keep the paragraph as is, and then a
- for the specific benefits items. That would preserve all.
Pay: The paragraph: "Pay Range The Typical Pay Range For This Role Is $83,430.00 - $222,480.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above."
We need to keep that as prose (
). Could also note it's pay range.
Schedule: "Anticipated Weekly Hours 40 Time Type Full time". Could be a short paragraph.
Now About the role: combine intro paragraph and position summary.
Intro paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one
for prose. Do NOT repeat the job title as a 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. Content includes: - Intro paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time." - Position Summary: "CVS Health Digital is looking for hands-on, passionate people who want to join a high energy and growing team to make a difference in customers’ lives and who want to be on the forefront of digital innovation that aims to reinvent what a pharmacy and a health care company can be in the digital world. Currently, we are hiring for an experienced Senior STIBO Software Developer to support enterprise Master Data Management (MDM) initiatives in a fast-paced retail and healthcare environment. This Senior Developer focuses on building scalable data solutions to manage product, vendor, and customer master data across omnichannel systems while ensuring data quality, governance, and consistency." - Expectations For The Role: bullet list (actually sentences). It includes many responsibilities: invest 15% mentoring, 15% working with product, 70% technical SME, develop and support STIBO STEP solutions, workflows, integrations, ensure data quality, governance, platform performance, troubleshoot and resolve complex platform and data issues, drive delivery through accurate estimates, ownership, communication, support production operations, SaaS upgrades, continuous improvements, design, develop, configure and customize the Stibo STEP platform, including workflows, WebUI interfaces, attributes and validation rules, support quarterly SaaS upgrades and release impact reviews, implement data governance, stewardship, and data quality frameworks, optimize platform performance, troubleshoot issues, and provide production support. - Required Qualifications: list: 5+ years MDM/PIM development experience, 5+ years hands-on Stibo STEP development and administration experience, 3+ years experience with CI/CD tools including Azure DevOps, Jenkins and Git, 3+ years experience with Azure (preferred) or GCP cloud platforms. - Preferred Qualifications: list: Experience with REST/SOAP APIs, XML, JSON, Kafka and Informatica, Retail or healthcare industry experience, Knowledge of product lifecycle and catalog management, Experience supporting omnichannel retail environments, Knowledge of supplier/vendor onboarding and healthcare regulatory data handling, Experience using AI for data maintenance in STEP, Strong knowledge of JavaScript, Web UI development, SQL and data modeling, Ability to drive master data governance and product/vendor lifecycle management, Strong collaboration and problem-solving skills. - EDUCATION: Bachelor’s degree or equivalent experience (HS diploma + 4 years relevant experience) - Business Overview: paragraphs about CVS Health purpose, Heart At Work Behaviors, diversity, inclusion, etc. This is generic corporate fluff but still substantive? Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Business Overview is not exactly EEO but it's generic corporate mission. Might be considered okay to keep as "About the role" or "Overview". However we need to avoid filler. It's not filler; it's specific to CVS Health. Could be included. - Anticipated Weekly Hours 40, Time Type Full time: This is schedule info. Should we include a Schedule section? The posting states Anticipated Weekly Hours 40, Time Type Full time. That's specific schedule info. So we can include a Schedule section with that. - Pay Range: The posting includes Pay Range: The Typical Pay Range For This Role Is $83,430.00 - $222,480.00. Also mentions bonus etc. So we can include Pay section. - Benefits: "Great Benefits For Great People" paragraph describing benefits: medical, dental, vision, paid time off, retirement savings, wellness programs, etc. So we can include Benefits section. - Additional details: application window close date 10/30/2026, Qualified applicants with arrest or conviction records will be considered... That's EEO/legal boilerplate? It's about hiring practice; might be considered legal boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is about arrest/conviction records, which is a kind of EEO statement. Likely should be removed. - Also "We anticipate the application window for this opening will close on: 10/30/2026" is application instruction? It's a date; maybe we can keep as minor metadata in a short
or drop it. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short paragraph at end with that info, but not as a heading. - Also "Our people fuel our future..." is part of benefits section? Already covered. We need to avoid duplication. We'll produce sections: About the role (intro + position summary maybe), Responsibilities (Expectations For The Role), Qualifications (maybe combine Required and Preferred? Could separate but they said prefer few substantive sections over many thin ones. Could combine Required and Preferred into Qualifications section with subheadings? But we only allowed
headings; we could have multiple sections: Responsibilities, Qualifications, Benefits, Pay, Schedule. Also maybe Education as part of Qualifications.
We need to decide.
Let's extract substantive content:
About the role: The introductory paragraph and position summary.
Responsibilities: The Expectations For The Role bullet list.
Qualifications: Required Qualifications + Preferred Qualifications + Education.
Benefits: Great Benefits For Great People paragraph.
Pay: Pay Range paragraph.
Schedule: Anticipated Weekly Hours 40, Time Type Full time.
We should not include EEO boilerplate.
We need to format lists with - . For responsibilities, each sentence could be a list item. For qualifications, each bullet.
We need to preserve all substantive information; do not invent or summarize away detail. So we must keep each point exactly as written (or close). We can rephrase slightly? Probably better to keep the wording.
Let's list responsibilities exactly as in the posting:
- Invest 15% of your time mentoring less experienced engineers
- Invest 15% of your efforts working alongside Product as well as stakeholders on other teams
- Invest 70% of your time using your technical SME and coding skills in strategic planning, scoping, delivery, and working alongside the Senior Engineering Manager
- Develop and support STIBO STEP solutions, workflows, and integrations
- Ensure data quality, governance, and platform performance
- Troubleshoot and resolve complex platform and data issues
- Drive delivery through accurate estimates, ownership, and communication
- Support production operations, SaaS upgrades, and continuous improvements
- Design, develop, configure and customize the Stibo STEP platform, including workflows, WebUI interfaces, attributes and validation rules
- Support quarterly SaaS upgrades and release impact reviews
- Implement data governance, stewardship, and data quality frameworks
- Optimize platform performance, troubleshoot issues, and provide production support
Note: Some duplicates: troubleshoot appears twice; we keep both as they are separate points.
Now Required Qualifications:
- 5+ years of MDM/PIM development experience
- 5+ years of hands-on Stibo STEP development and administration experience
- 3+ years of experience with CI/CD tools including Azure DevOps, Jenkins and Git
- 3+ years of experience with Azure (preferred) or GCP cloud platforms
Preferred Qualifications:
- Experience with REST/SOAP APIs, XML, JSON, Kafka and Informatica
- Retail or healthcare industry experience
- Knowledge of product lifecycle and catalog management
- Experience supporting omnichannel retail environments
- Knowledge of supplier/vendor onboarding and healthcare regulatory data handling
- Experience using AI for data maintenance in STEP
- Strong knowledge of JavaScript, Web UI development, SQL and data modeling
- Ability to drive master data governance and product/vendor lifecycle management
- Strong collaboration and problem-solving skills
Education:
- Bachelor’s degree or equivalent experience (HS diploma + 4 years relevant experience)
Benefits: The paragraph: "Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments."
We need to keep that as prose (
). Could also list benefits as list? The instruction says use
- for any list of duties/requirements/benefits. Benefits are listed as items: medical, dental, vision coverage, paid time off, retirement savings options, wellness programs, and other resources. Could make a list. But the paragraph also includes introductory sentences. We could keep the paragraph and then a list for the benefits items. However to avoid duplication, we could just make a list of benefits and omit the intro sentences? But we must preserve ALL substantive information; we cannot drop the intro sentences. So we need to keep them. We could keep the paragraph as is, and then a
- for the specific benefits items. That would preserve all.
Pay: The paragraph: "Pay Range The Typical Pay Range For This Role Is $83,430.00 - $222,480.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above."
We need to keep that as prose (
). Could also note it's pay range.
Schedule: "Anticipated Weekly Hours 40 Time Type Full time". Could be a short paragraph.
Now About the role: combine intro paragraph and position summary.
Intro paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one
- . For responsibilities, each sentence could be a list item. For qualifications, each bullet.
We need to preserve all substantive information; do not invent or summarize away detail. So we must keep each point exactly as written (or close). We can rephrase slightly? Probably better to keep the wording.
Let's list responsibilities exactly as in the posting:
- Invest 15% of your time mentoring less experienced engineers
- Invest 15% of your efforts working alongside Product as well as stakeholders on other teams
- Invest 70% of your time using your technical SME and coding skills in strategic planning, scoping, delivery, and working alongside the Senior Engineering Manager
- Develop and support STIBO STEP solutions, workflows, and integrations
- Ensure data quality, governance, and platform performance
- Troubleshoot and resolve complex platform and data issues
- Drive delivery through accurate estimates, ownership, and communication
- Support production operations, SaaS upgrades, and continuous improvements
- Design, develop, configure and customize the Stibo STEP platform, including workflows, WebUI interfaces, attributes and validation rules
- Support quarterly SaaS upgrades and release impact reviews
- Implement data governance, stewardship, and data quality frameworks
- Optimize platform performance, troubleshoot issues, and provide production support
Note: Some duplicates: troubleshoot appears twice; we keep both as they are separate points.
Now Required Qualifications:
- 5+ years of MDM/PIM development experience
- 5+ years of hands-on Stibo STEP development and administration experience
- 3+ years of experience with CI/CD tools including Azure DevOps, Jenkins and Git
- 3+ years of experience with Azure (preferred) or GCP cloud platforms
Preferred Qualifications:
- Experience with REST/SOAP APIs, XML, JSON, Kafka and Informatica
- Retail or healthcare industry experience
- Knowledge of product lifecycle and catalog management
- Experience supporting omnichannel retail environments
- Knowledge of supplier/vendor onboarding and healthcare regulatory data handling
- Experience using AI for data maintenance in STEP
- Strong knowledge of JavaScript, Web UI development, SQL and data modeling
- Ability to drive master data governance and product/vendor lifecycle management
- Strong collaboration and problem-solving skills
Education:
- Bachelor’s degree or equivalent experience (HS diploma + 4 years relevant experience)
Benefits: The paragraph: "Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments."
We need to keep that as prose (
). Could also list benefits as list? The instruction says use
- for any list of duties/requirements/benefits. Benefits are listed as items: medical, dental, vision coverage, paid time off, retirement savings options, wellness programs, and other resources. Could make a list. But the paragraph also includes introductory sentences. We could keep the paragraph and then a list for the benefits items. However to avoid duplication, we could just make a list of benefits and omit the intro sentences? But we must preserve ALL substantive information; we cannot drop the intro sentences. So we need to keep them. We could keep the paragraph as is, and then a
- for the specific benefits items. That would preserve all.
Pay: The paragraph: "Pay Range The Typical Pay Range For This Role Is $83,430.00 - $222,480.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above."
We need to keep that as prose (
). Could also note it's pay range. Schedule: "Anticipated Weekly Hours 40 Time Type Full time". Could be a short paragraph. Now About the role: combine intro paragraph and position summary. Intro paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one
- for the specific benefits items. That would preserve all.
Pay: The paragraph: "Pay Range The Typical Pay Range For This Role Is $83,430.00 - $222,480.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above."
We need to keep that as prose (
- for any list of duties/requirements/benefits. Benefits are listed as items: medical, dental, vision coverage, paid time off, retirement savings options, wellness programs, and other resources. Could make a list. But the paragraph also includes introductory sentences. We could keep the paragraph and then a list for the benefits items. However to avoid duplication, we could just make a list of benefits and omit the intro sentences? But we must preserve ALL substantive information; we cannot drop the intro sentences. So we need to keep them. We could keep the paragraph as is, and then a