Senior Epicor ERP Developer
for section headings. Use - for lists. Use
for prose.
We must not repeat job title as heading. No Job ID.
Let's craft.
First, maybe a short intro paragraph about role: "The Senior Epicor ERP Developer is responsible for the design, development, integration, support, and continuous improvement of LaundryLux’s Epicor Kinetic environment." That's from first paragraph.
Then sections:
About the role
maybe not needed because we already have intro? But we can include.
Better: About the role
...
Then Responsibilities: list bullet points from "What you will do". Could break into subcategories but we can just list.
Requirements: "What you should have" bullet list.
Preferred Qualifications: bullet list.
Benefits: bullet list from LaundryLux Benefits.
Education and Experience: maybe part of Requirements but we can separate.
Work Expectations maybe not needed as no specific pay/schedule.
We must not include sections with placeholder like "commensurate with experience". Not present.
Let's extract content.
Intro paragraph: "Join LaundryLux Laundrylux is the North American supplier of Electrolux Professional & Wascomat equipment for Laundromats, Coin Laundries & On-Premises Laundries. From financing to repairs, Laundrylux provides a comprehensive set of services to help with all elements of commercial laundry. Senior Epicor ERP Developer What we are looking for: The Senior Epicor ERP Developer is responsible for the design, development, integration, support, and continuous improvement of LaundryLux’s Epicor Kinetic environment. This role serves as a senior technical owner for Epicor solutions and ensures that enhancements are built from clearly defined business requirements, aligned with LaundryLux’s operating model, properly tested, documented, secured, and supportable over the long term. The position is expected to do more than execute configuration requests. The Senior Epicor ERP Developer will evaluate the underlying business need, recommend the appropriate solution, identify upstream and downstream impacts, challenge requests when necessary, and take ownership of the complete technical design through deployment and post-production support."
We can condense but must preserve all substantive info. Might be long but okay.
Then "Before we continue to dive into the requirements for the role let’s talk about Why you should join LaundryLux?" then bullet points: Career Advancement, Learning and Development, Diversity Initiatives, LaundryLux Benefits (list). We'll treat Benefits as separate section.
Then "Back to the role: What you will do:" then list responsibilities.
Then "What you should have:" list.
Then "Preferred Qualifications:" list.
Then "Education and Experience:" list.
Then "Work Expectations:" maybe include but not required; but we can include as it's substantive.
Physical Requirements and Travel Required maybe include but not required? They are substantive but not pay/schedule/benefits. Could include as a section "Work Details". But instruction: prefer few substantive sections over many thin ones. Could combine Work Expectations, Physical Requirements, Travel Required into a section "Work Details". But we need headings only for specific categories: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use others? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. So we should stick to those headings. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no Pay or Schedule info, so we omit those.
We have Benefits.
We have Requirements (what you should have). We have Qualifications (Preferred Qualifications). We have Skills maybe part of Requirements but we could separate? But we have strong C#/.NET etc as skills; could put under Skills. But we already have Requirements covering experience. Might be okay to have Requirements and Qualifications only.
We also need About the role.
Responsibilities.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
We must not create Skills if not needed.
Now extract content for each.
About the role: combine introductory paragraphs up to "Why you should join LaundryLux?" maybe exclude that part. Let's craft a paragraph summarizing role: The Senior Epicor ERP Developer is responsible for design, development, integration, support, continuous improvement of Epicor Kinetic environment; serves as senior technical owner; ensures enhancements built from business requirements; evaluates underlying need, recommends solution, identifies impacts, challenges requests, owns technical design through deployment and post-production support.
We'll put that in
.
Responsibilities: list from "What you will do:" bullet points.
We need to capture all bullet points under that heading.
Let's extract bullet points:
- Epicor Development and Solution Ownership
- Design, develop, test, deploy, and support solutions within Epicor Kinetic, including Business Process Management (BPM) directives, data directives, Epicor Functions, Business Activity Queries (BAQs), dashboards, reports, customizations, and Application Studio layers.
- Translate business requirements into complete technical solutions that are scalable, secure, maintainable, and aligned with Epicor standards and LaundryLux’s enterprise architecture.
- Own the end-to-end technical design for assigned solutions, including data flow, business logic, security, error handling, deployment, rollback, monitoring, and support documentation.
- Review existing customizations and technical debt; recommend where solutions should be corrected, simplified, retired, or replaced with standard Epicor functionality.
- Evaluate Epicor releases, patches, and Kinetic capabilities to determine their impact on custom solutions and business processes.
- Business Analysis and Cross-Functional Partnership
- Partner with Accounting, Finance, Sales, Customer Care, Purchasing, Warehouse, Logistics, Parts, Service, Warranty, and other business teams to understand current processes, pain points, controls, and future-state requirements.
- Lead or participate in discovery and requirements sessions; distinguish the stated request from the underlying business need before selecting a technical approach.
- Document functional requirements, technical specifications, process impacts, assumptions, dependencies, risks, and acceptance criteria before development begins.
- Provide clear recommendations and alternatives to stakeholders, including the operational and technical tradeoffs of each option.
- Coordinate user acceptance testing and obtain appropriate business approval before production deployment.
- Integrations, Data, and Reporting
- Develop and support integrations between Epicor and LaundryLux business platforms using Epicor REST services, APIs, webhooks, OData, middleware, secure file exchange, and other approved integration methods.
- Support integrations involving e-commerce, payment, tax, CRM, EDI, warehouse, shipping, reporting, and financial systems, including troubleshooting transactions across both endpoints.
- Develop efficient BAQs, data extracts, reports, and interfaces while protecting data integrity and avoiding unsupported direct database changes.
- Collaborate with data and reporting resources to ensure Epicor data definitions, calculations, and business rules are documented and consistently represented in downstream reporting.
- Establish appropriate logging, reconciliation, alerting, and recovery procedures for business-critical integrations and automated processes.
- Technical Governance, Quality, and Documentation
- Follow and help mature LaundryLux’s software development lifecycle, change control, source control, peer review, testing, release, and production support practices.
- Maintain clear technical documentation for all developed solutions, including purpose, owners, dependencies, data mappings, logic, security, deployment steps, test evidence, known limitations, and support procedures.
- Ensure changes are developed and validated in the appropriate non-production environment and are not moved into production without required review and approval.
- Apply role-based security, least-privilege access, segregation-of-duties considerations, and secure coding practices to Epicor solutions.
- Maintain an accurate inventory of Epicor customizations, integrations, scheduled processes, reports, and other IT-owned solution components.
- Production Support and Operational Reliability
- Serve as a senior escalation point for complex Epicor incidents, performance issues, data errors, failed integrations, and production defects.
- Perform structured root-cause analysis and implement durable corrective actions rather than repeated manual workarounds.
- Participate in Epicor ticket triage, provide realistic estimates and status updates, and ensure work is prioritized according to business impact and agreed service expectations.
- Coordinate with Epicor Support, implementation partners, and other vendors while retaining internal ownership of the issue and validating vendor-proposed solutions.
- Support planned maintenance, upgrades, deployments, and critical business periods as required.
- Technical Leadership
- Provide technical direction, code review, development standards, and mentoring to Epicor developers and other technical resources.
- Estimate effort, identify resource or dependency risks, and communicate delivery concerns early to IT leadership and stakeholders.
- Contribute to the Epicor roadmap and ERP evaluation initiatives by identifying functional gaps, customization dependencies, data considerations, and opportunities to reduce complexity.
- Promote knowledge transfer so that critical Epicor solutions are understood and supportable by the broader IT team.
We'll put each main bullet as
- maybe with sub-bullets? But we can just list each as
- with the detailed text.
Requirements: "What you should have:" bullet list:
- Strong experience with Epicor Kinetic or Epicor ERP 10/11, including BPMs, data directives, Epicor Functions, BAQs, dashboards, reporting, REST services, security, and deployment practices.
- Strong C#/.NET and SQL skills, with experience designing, debugging, and supporting production business applications.
- Demonstrated experience building and supporting enterprise integrations using REST APIs, webhooks, JSON/XML, OData, middleware, or secure file-based interfaces.
- Experience gathering requirements, producing technical designs, conducting unit and integration testing, supporting user acceptance testing, and managing controlled production releases.
- Strong troubleshooting skills across applications, integrations, data, infrastructure dependencies, and business processes.
- Ability to explain technical issues and solution choices clearly to both technical and non-technical stakeholders.
- Strong ownership, judgment, organization, documentation, and follow-through.
Qualifications: "Preferred Qualifications:" bullet list:
- Experience with Epicor Kinetic SaaS/cloud environments, Application Studio, Epicor Automation Studio, and Epicor upgrade-readiness practices.
- Experience supporting manufacturing, distribution, inventory, order management, purchasing, service, warranty, finance, or field-service operations.
- Experience with EDI transactions and trading-partner integrations, including order, shipment, invoice, and inventory-related documents.
- Experience with SSRS, Power BI, Azure services, source control, DevOps pipelines, and structured release management.
- Knowledge of financial controls, audit requirements, role-based security, segregation of duties, and data governance.
Education and Experience: maybe part of Requirements but we can include as separate? Not in list of headings but could be under Requirements. We'll incorporate into Requirements maybe as additional bullet.
But we have Education and Experience: Bachelor’s degree in Computer Science, Information Systems, Software Engineering, or a related field, or equivalent combination of education and relevant professional experience. Seven or more years of ERP development experience, including at least five years of hands-on Epicor ERP development and support experience. Epicor certification or comparable advanced Epicor implementation experience.
We'll add those under Requirements.
Benefits: list from LaundryLux Benefits:
- Health benefits package including medical, dental & vision plans
- Life Insurance
for prose. We must not repeat job title as heading. No Job ID. Let's craft. First, maybe a short intro paragraph about role: "The Senior Epicor ERP Developer is responsible for the design, development, integration, support, and continuous improvement of LaundryLux’s Epicor Kinetic environment." That's from first paragraph. Then sections:
About the role
maybe not needed because we already have intro? But we can include. Better:About the role
...
Then Responsibilities: list bullet points from "What you will do". Could break into subcategories but we can just list. Requirements: "What you should have" bullet list. Preferred Qualifications: bullet list. Benefits: bullet list from LaundryLux Benefits. Education and Experience: maybe part of Requirements but we can separate. Work Expectations maybe not needed as no specific pay/schedule. We must not include sections with placeholder like "commensurate with experience". Not present. Let's extract content. Intro paragraph: "Join LaundryLux Laundrylux is the North American supplier of Electrolux Professional & Wascomat equipment for Laundromats, Coin Laundries & On-Premises Laundries. From financing to repairs, Laundrylux provides a comprehensive set of services to help with all elements of commercial laundry. Senior Epicor ERP Developer What we are looking for: The Senior Epicor ERP Developer is responsible for the design, development, integration, support, and continuous improvement of LaundryLux’s Epicor Kinetic environment. This role serves as a senior technical owner for Epicor solutions and ensures that enhancements are built from clearly defined business requirements, aligned with LaundryLux’s operating model, properly tested, documented, secured, and supportable over the long term. The position is expected to do more than execute configuration requests. The Senior Epicor ERP Developer will evaluate the underlying business need, recommend the appropriate solution, identify upstream and downstream impacts, challenge requests when necessary, and take ownership of the complete technical design through deployment and post-production support." We can condense but must preserve all substantive info. Might be long but okay. Then "Before we continue to dive into the requirements for the role let’s talk about Why you should join LaundryLux?" then bullet points: Career Advancement, Learning and Development, Diversity Initiatives, LaundryLux Benefits (list). We'll treat Benefits as separate section. Then "Back to the role: What you will do:" then list responsibilities. Then "What you should have:" list. Then "Preferred Qualifications:" list. Then "Education and Experience:" list. Then "Work Expectations:" maybe include but not required; but we can include as it's substantive. Physical Requirements and Travel Required maybe include but not required? They are substantive but not pay/schedule/benefits. Could include as a section "Work Details". But instruction: prefer few substantive sections over many thin ones. Could combine Work Expectations, Physical Requirements, Travel Required into a section "Work Details". But we need headings only for specific categories: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use others? It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. So we should stick to those headings. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no Pay or Schedule info, so we omit those. We have Benefits. We have Requirements (what you should have). We have Qualifications (Preferred Qualifications). We have Skills maybe part of Requirements but we could separate? But we have strong C#/.NET etc as skills; could put under Skills. But we already have Requirements covering experience. Might be okay to have Requirements and Qualifications only. We also need About the role. Responsibilities. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We must not create Skills if not needed. Now extract content for each. About the role: combine introductory paragraphs up to "Why you should join LaundryLux?" maybe exclude that part. Let's craft a paragraph summarizing role: The Senior Epicor ERP Developer is responsible for design, development, integration, support, continuous improvement of Epicor Kinetic environment; serves as senior technical owner; ensures enhancements built from business requirements; evaluates underlying need, recommends solution, identifies impacts, challenges requests, owns technical design through deployment and post-production support. We'll put that in
. Responsibilities: list from "What you will do:" bullet points. We need to capture all bullet points under that heading. Let's extract bullet points: - Epicor Development and Solution Ownership - Design, develop, test, deploy, and support solutions within Epicor Kinetic, including Business Process Management (BPM) directives, data directives, Epicor Functions, Business Activity Queries (BAQs), dashboards, reports, customizations, and Application Studio layers. - Translate business requirements into complete technical solutions that are scalable, secure, maintainable, and aligned with Epicor standards and LaundryLux’s enterprise architecture. - Own the end-to-end technical design for assigned solutions, including data flow, business logic, security, error handling, deployment, rollback, monitoring, and support documentation. - Review existing customizations and technical debt; recommend where solutions should be corrected, simplified, retired, or replaced with standard Epicor functionality. - Evaluate Epicor releases, patches, and Kinetic capabilities to determine their impact on custom solutions and business processes. - Business Analysis and Cross-Functional Partnership - Partner with Accounting, Finance, Sales, Customer Care, Purchasing, Warehouse, Logistics, Parts, Service, Warranty, and other business teams to understand current processes, pain points, controls, and future-state requirements. - Lead or participate in discovery and requirements sessions; distinguish the stated request from the underlying business need before selecting a technical approach. - Document functional requirements, technical specifications, process impacts, assumptions, dependencies, risks, and acceptance criteria before development begins. - Provide clear recommendations and alternatives to stakeholders, including the operational and technical tradeoffs of each option. - Coordinate user acceptance testing and obtain appropriate business approval before production deployment. - Integrations, Data, and Reporting - Develop and support integrations between Epicor and LaundryLux business platforms using Epicor REST services, APIs, webhooks, OData, middleware, secure file exchange, and other approved integration methods. - Support integrations involving e-commerce, payment, tax, CRM, EDI, warehouse, shipping, reporting, and financial systems, including troubleshooting transactions across both endpoints. - Develop efficient BAQs, data extracts, reports, and interfaces while protecting data integrity and avoiding unsupported direct database changes. - Collaborate with data and reporting resources to ensure Epicor data definitions, calculations, and business rules are documented and consistently represented in downstream reporting. - Establish appropriate logging, reconciliation, alerting, and recovery procedures for business-critical integrations and automated processes. - Technical Governance, Quality, and Documentation - Follow and help mature LaundryLux’s software development lifecycle, change control, source control, peer review, testing, release, and production support practices. - Maintain clear technical documentation for all developed solutions, including purpose, owners, dependencies, data mappings, logic, security, deployment steps, test evidence, known limitations, and support procedures. - Ensure changes are developed and validated in the appropriate non-production environment and are not moved into production without required review and approval. - Apply role-based security, least-privilege access, segregation-of-duties considerations, and secure coding practices to Epicor solutions. - Maintain an accurate inventory of Epicor customizations, integrations, scheduled processes, reports, and other IT-owned solution components. - Production Support and Operational Reliability - Serve as a senior escalation point for complex Epicor incidents, performance issues, data errors, failed integrations, and production defects. - Perform structured root-cause analysis and implement durable corrective actions rather than repeated manual workarounds. - Participate in Epicor ticket triage, provide realistic estimates and status updates, and ensure work is prioritized according to business impact and agreed service expectations. - Coordinate with Epicor Support, implementation partners, and other vendors while retaining internal ownership of the issue and validating vendor-proposed solutions. - Support planned maintenance, upgrades, deployments, and critical business periods as required. - Technical Leadership - Provide technical direction, code review, development standards, and mentoring to Epicor developers and other technical resources. - Estimate effort, identify resource or dependency risks, and communicate delivery concerns early to IT leadership and stakeholders. - Contribute to the Epicor roadmap and ERP evaluation initiatives by identifying functional gaps, customization dependencies, data considerations, and opportunities to reduce complexity. - Promote knowledge transfer so that critical Epicor solutions are understood and supportable by the broader IT team. We'll put each main bullet as