Software Engineer
TestEquity LLC · Houston, TX · 1 mo ago
HybridEngineeringFull-time
We need to output HTML fragment with sections only when content exists. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
From posting: Summary / Position Purpose (intro). Then Essential Duties, Functions, And/or Responsibilities (list). Then Qualifications (Education and/or Work Experience Requirements). Also there are Preferred Experience (maybe part of Qualifications or Skills). There's also "Success in This Role Looks Like" maybe could be part of Responsibilities or separate? Not a standard heading; we could incorporate into Responsibilities or maybe a separate section like "Expectations". But we only allowed headings from list; we should not create extra headings. So we need to fit content into allowed headings.
We have:
- About the role: could be the Summary / Position Purpose paragraph.
- Responsibilities: Essential Duties etc.
- Requirements: maybe the Qualifications (Education and/or Work Experience Requirements) plus maybe some required skills.
- Qualifications: maybe we could treat as same as Requirements? But we need distinct sections; we could put Education/Experience under Qualifications, and Skills under Skills.
But we have also "Preferred Experience" which could go under Skills or Qualifications as optional.
We have no explicit Benefits, Pay, Schedule info. So we should NOT include those sections.
We must not repeat job title as heading.
We must not include boilerplate like EEO, visa sponsorship, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tasks, technologies, etc.
We need to use
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
From posting: Summary / Position Purpose (intro). Then Essential Duties, Functions, And/or Responsibilities (list). Then Qualifications (Education and/or Work Experience Requirements). Also there are Preferred Experience (maybe part of Qualifications or Skills). There's also "Success in This Role Looks Like" maybe could be part of Responsibilities or separate? Not a standard heading; we could incorporate into Responsibilities or maybe a separate section like "Expectations". But we only allowed headings from list; we should not create extra headings. So we need to fit content into allowed headings.
We have:
- About the role: could be the Summary / Position Purpose paragraph.
- Responsibilities: Essential Duties etc.
- Requirements: maybe the Qualifications (Education and/or Work Experience Requirements) plus maybe some required skills.
- Qualifications: maybe we could treat as same as Requirements? But we need distinct sections; we could put Education/Experience under Qualifications, and Skills under Skills.
But we have also "Preferred Experience" which could go under Skills or Qualifications as optional.
We have no explicit Benefits, Pay, Schedule info. So we should NOT include those sections.
We must not repeat job title as heading.
We must not include boilerplate like EEO, visa sponsorship, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tasks, technologies, etc.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment.
Let's extract substantive content:
Summary / Position Purpose:
"We are seeking a Software Engineer – ERP Systems to join our growing IT team! In this role, you will design, develop, test, and maintain software applications that drive our distribution and warehousing business forward across the Infor ecosystem. Working alongside senior engineers and business teams, you’ll build, extend, and support the platforms that run the business—with a primary focus on Infor CloudSuite Distribution (CSD) and Total Warehouse Logistics (TWL). The ideal candidate has a passion for clean, scalable code, thrives in a collaborative team environment, and enjoys solving real-world distribution and warehouse problems (order-to-cash, procurement, inventory, receiving, putaway, replenishment, shipping, and fulfillment) with innovative solutions. This is a hands-on development role suited to an early-career engineer (roughly 1–3 years of experience)."
That's prose; put in
.
Responsibilities: Essential Duties, Functions, And/or Responsibilities includes several bullet-like paragraphs. We need to turn each duty into
- under a
. The content includes multiple sections: ERP Development & Customization, Warehouse Configuration & Support, Collaboration & Solution Design, Integrations & Data, Quality, Testing & Support, Continuous Improvement, Other duties as assigned.
We should capture each bullet as list item, preserving details.
Let's list them:
- ERP Development & Customization:
* Design, develop, test, and deploy high-quality customizations, extensions, and enhancements within Infor CloudSuite Distribution (CSD) and related distribution modules, in alignment with business needs and technical requirements.
* Write clean, efficient, and maintainable code—including business logic, reports, batch processes, and automation—using SQL, JavaScript, and Python.
* Develop and maintain custom programs supporting order management, purchasing, inventory control, pricing, and warehouse/fulfillment workflows.
* Help enhance and modernize legacy ERP code while preserving the stability of mission-critical systems.
- Warehouse Configuration & Support:
* Configure and support workflows and application settings across Total Warehouse Logistics (TWL) and CSD warehouse modules.
* Support core warehouse business processes: receiving, putaway, order selection, replenishment, inventory control, and shipping.
* Assist with system validation and testing ahead of releases and go-lives.
- Collaboration & Solution Design:
* Collaborate with product managers, business stakeholders, and fellow engineers to understand requirements and deliver impactful solutions.
* Translate business requirements into functional and technical designs, favoring solutions that fit the standard Infor product where possible and minimizing unnecessary customization.
* Document technical designs, configurations, data flows, and solution logic for maintainability and knowledge transfer.
- Integrations & Data:
* Build and support integrations between the ERP, TWL, finance, e-commerce, EDI, and third-party/back-office systems using RESTful APIs, middleware, and data interfaces.
* Develop reports, extracts, and data transformations to support operational and financial reporting.
* Help ensure data consistency and integrity across integrated platforms.
- Quality, Testing & Support:
* Participate in code reviews and contribute to team best practices and coding standards.
* Debug and resolve software defects and performance issues, providing root-cause analysis for production issues.
* Follow source control, CI/CD, testing, and deployment best practices to deliver predictable releases and reduce technical debt over time.
* Directly and indirectly responsible for product quality.
- Continuous Improvement:
* Stay current with emerging technologies and industry trends to continuously improve development practices.
* Other duties as assigned.
We could combine "Other duties as assigned" as a separate list item.
Now Requirements/Qualifications:
Qualifications Education and/or Work Experience Requirements:
- Bachelor’s degree in Computer Science, Software Engineering, or a related field (or equivalent work experience).
- 1–3 years of software development experience in a professional environment, ideally supporting ERP or business applications.
- Strong programming experience with SQL, JavaScript, and Python (required).
- Experience with version control systems (e.g., Git).
- Solid understanding of the software development life cycle (SDLC), agile methodologies, and DevOps practices.
- Experience with RESTful APIs, and familiarity with microservices architecture
- Experience with relational and/or NoSQL databases.
- Familiarity with cloud platforms (e.g., Azure, AWS, Google Cloud).
- Exposure to or experience with Infor CloudSuite Distribution (CSD) or a comparable distribution ERP.
- Familiarity with distribution and/or warehouse business processes: order management, procurement, inventory, receiving, putaway, replenishment, shipping, and pricing.
- Strong problem-solving and critical thinking skills; excellent verbal and written communication.
- Self-motivated with the ability to work independently or within a team, with strong attention to detail and a passion for quality.
Preferred Experience (could be under Skills or Qualifications as optional):
- OpenEdge ABL (Progress 4GL) development experience (a plus).
- Infor ION, PaaS, or workflow/automation experience (a plus).
- Experience with Total Warehouse Logistics (TWL) configuration and processes.
- Exposure to cloud-native architectures and modern enterprise integration frameworks.
- Experience in a multi-entity, multi-brand, or multi-warehouse environment.
We also have "Success in This Role Looks Like" which could be considered as expectations; maybe we could incorporate into Responsibilities or a separate section like "Expectations". But we only allowed headings list; we could put under Responsibilities as additional items, or maybe under a separate heading like "Expectations" not allowed. Better to incorporate into Responsibilities as additional bullet points.
Success in This Role Looks Like:
- Business needs are translated into stable, well-designed ERP and warehouse solutions.
- Customizations and integrations are delivered predictably and adopted well by end-users.
- Production issues are resolved efficiently with solid root-cause analysis.
- Technical debt and unnecessary customization decrease over time.
- ERP, warehouse, and connected systems integrate cleanly across the distribution operation.
We can add these as list items under Responsibilities or maybe under a separate section like "Expectations". Since not in allowed headings, we add to Responsibilities.
Also we have visa sponsorship statement and EEO etc which we must remove.
Now we need to decide which sections to output.
We have:
- About the role (summary)
- Responsibilities (duties + success criteria)
- Requirements (maybe mandatory qualifications)
- Skills (maybe technical skills list)
- Qualifications (maybe education/experience) but we have overlapping.
We need to avoid duplication. Let's map:
We could use:
About the role
...
Responsibilities
...
Requirements
...
(for mandatory qualifications)
Skills
...
(for preferred/experience plus technical skills)
We could also have Qualifications
but we already used Requirements; maybe we can combine education/experience under Requirements and skills under Skills. The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use any of those; we just need to not create empty sections.
We have content for About the role, Responsibilities, Requirements (education/experience), Skills (technical skills and preferred experience). We could also have Qualifications but maybe we can skip if we used Requirements for education/experience and Skills for technical skills. However we have also "Preferred Experience" which could go under Skills.
Thus we will output:
About the role
...
Responsibilities
- ...
...
Requirements
- Bachelor’s degree in Computer Science, Software Engineering, or a related field (or equivalent work experience).
- 1–3 years of software development experience in a professional environment, ideally supporting ERP or business applications.
- Strong programming experience with SQL, JavaScript, and Python (required).
- Experience with version control systems (e.g., Git).
- Solid understanding of the software development life cycle (SDLC), agile methodologies, and DevOps practices.
- Experience with RESTful APIs, and familiarity with microservices architecture.
- Experience with relational and/or NoSQL databases.
- Familiarity with cloud platforms (e.g., Azure, AWS, Google Cloud).
- Exposure to or experience with Infor CloudSuite Distribution (CSD) or a comparable distribution ERP.
- Familiarity with distribution and/or warehouse business processes: order management, procurement, inventory, receiving, putaway, replenishment, shipping, and pricing.
- Strong problem-solving and critical thinking skills; excellent verbal and written communication.
- Self-motivated with the ability to work independently or within a team, with strong attention to detail and a passion for quality.
Skills
- OpenEdge ABL (Progress 4GL) development experience (a plus).
- Infor ION, PaaS, or workflow/automation experience (a plus).
- Experience with Total Warehouse Logistics (TWL) configuration and processes.
- Exposure to cloud-native architectures and modern enterprise integration frameworks.
- Experience in a multi-entity, multi-brand, or multi-warehouse environment.
We should also include the success criteria items maybe under Responsibilities as additional list items.
Let's add them to Responsibilities list.
Responsibilities list items:
- Design, develop, test, and deploy high-quality customizations, extensions, and enhancements within Infor CloudSuite Distribution (CSD) and related distribution modules, in alignment with business needs and technical requirements.
- Write clean, efficient, and maintainable code—including business logic, reports, batch processes, and automation—using SQL, JavaScript, and Python.
- Develop and maintain custom programs supporting order management, purchasing, inventory control, pricing, and warehouse/fulfillment workflows.
- Help enhance and modernize legacy ERP
for prose. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's extract substantive content: Summary / Position Purpose: "We are seeking a Software Engineer – ERP Systems to join our growing IT team! In this role, you will design, develop, test, and maintain software applications that drive our distribution and warehousing business forward across the Infor ecosystem. Working alongside senior engineers and business teams, you’ll build, extend, and support the platforms that run the business—with a primary focus on Infor CloudSuite Distribution (CSD) and Total Warehouse Logistics (TWL). The ideal candidate has a passion for clean, scalable code, thrives in a collaborative team environment, and enjoys solving real-world distribution and warehouse problems (order-to-cash, procurement, inventory, receiving, putaway, replenishment, shipping, and fulfillment) with innovative solutions. This is a hands-on development role suited to an early-career engineer (roughly 1–3 years of experience)." That's prose; put in
. Responsibilities: Essential Duties, Functions, And/or Responsibilities includes several bullet-like paragraphs. We need to turn each duty into
- . The content includes multiple sections: ERP Development & Customization, Warehouse Configuration & Support, Collaboration & Solution Design, Integrations & Data, Quality, Testing & Support, Continuous Improvement, Other duties as assigned.
We should capture each bullet as list item, preserving details.
Let's list them:
- ERP Development & Customization:
* Design, develop, test, and deploy high-quality customizations, extensions, and enhancements within Infor CloudSuite Distribution (CSD) and related distribution modules, in alignment with business needs and technical requirements.
* Write clean, efficient, and maintainable code—including business logic, reports, batch processes, and automation—using SQL, JavaScript, and Python.
* Develop and maintain custom programs supporting order management, purchasing, inventory control, pricing, and warehouse/fulfillment workflows.
* Help enhance and modernize legacy ERP code while preserving the stability of mission-critical systems.
- Warehouse Configuration & Support:
* Configure and support workflows and application settings across Total Warehouse Logistics (TWL) and CSD warehouse modules.
* Support core warehouse business processes: receiving, putaway, order selection, replenishment, inventory control, and shipping.
* Assist with system validation and testing ahead of releases and go-lives.
- Collaboration & Solution Design:
* Collaborate with product managers, business stakeholders, and fellow engineers to understand requirements and deliver impactful solutions.
* Translate business requirements into functional and technical designs, favoring solutions that fit the standard Infor product where possible and minimizing unnecessary customization.
* Document technical designs, configurations, data flows, and solution logic for maintainability and knowledge transfer.
- Integrations & Data:
* Build and support integrations between the ERP, TWL, finance, e-commerce, EDI, and third-party/back-office systems using RESTful APIs, middleware, and data interfaces.
* Develop reports, extracts, and data transformations to support operational and financial reporting.
* Help ensure data consistency and integrity across integrated platforms.
- Quality, Testing & Support:
* Participate in code reviews and contribute to team best practices and coding standards.
* Debug and resolve software defects and performance issues, providing root-cause analysis for production issues.
* Follow source control, CI/CD, testing, and deployment best practices to deliver predictable releases and reduce technical debt over time.
* Directly and indirectly responsible for product quality.
- Continuous Improvement:
* Stay current with emerging technologies and industry trends to continuously improve development practices.
* Other duties as assigned.
We could combine "Other duties as assigned" as a separate list item.
Now Requirements/Qualifications:
Qualifications Education and/or Work Experience Requirements:
- Bachelor’s degree in Computer Science, Software Engineering, or a related field (or equivalent work experience).
- 1–3 years of software development experience in a professional environment, ideally supporting ERP or business applications.
- Strong programming experience with SQL, JavaScript, and Python (required).
- Experience with version control systems (e.g., Git).
- Solid understanding of the software development life cycle (SDLC), agile methodologies, and DevOps practices.
- Experience with RESTful APIs, and familiarity with microservices architecture
- Experience with relational and/or NoSQL databases.
- Familiarity with cloud platforms (e.g., Azure, AWS, Google Cloud).
- Exposure to or experience with Infor CloudSuite Distribution (CSD) or a comparable distribution ERP.
- Familiarity with distribution and/or warehouse business processes: order management, procurement, inventory, receiving, putaway, replenishment, shipping, and pricing.
- Strong problem-solving and critical thinking skills; excellent verbal and written communication.
- Self-motivated with the ability to work independently or within a team, with strong attention to detail and a passion for quality.
Preferred Experience (could be under Skills or Qualifications as optional):
- OpenEdge ABL (Progress 4GL) development experience (a plus).
- Infor ION, PaaS, or workflow/automation experience (a plus).
- Experience with Total Warehouse Logistics (TWL) configuration and processes.
- Exposure to cloud-native architectures and modern enterprise integration frameworks.
- Experience in a multi-entity, multi-brand, or multi-warehouse environment.
We also have "Success in This Role Looks Like" which could be considered as expectations; maybe we could incorporate into Responsibilities or a separate section like "Expectations". But we only allowed headings list; we could put under Responsibilities as additional items, or maybe under a separate heading like "Expectations" not allowed. Better to incorporate into Responsibilities as additional bullet points.
Success in This Role Looks Like:
- Business needs are translated into stable, well-designed ERP and warehouse solutions.
- Customizations and integrations are delivered predictably and adopted well by end-users.
- Production issues are resolved efficiently with solid root-cause analysis.
- Technical debt and unnecessary customization decrease over time.
- ERP, warehouse, and connected systems integrate cleanly across the distribution operation.
We can add these as list items under Responsibilities or maybe under a separate section like "Expectations". Since not in allowed headings, we add to Responsibilities.
Also we have visa sponsorship statement and EEO etc which we must remove.
Now we need to decide which sections to output.
We have:
- About the role (summary)
- Responsibilities (duties + success criteria)
- Requirements (maybe mandatory qualifications)
- Skills (maybe technical skills list)
- Qualifications (maybe education/experience) but we have overlapping.
We need to avoid duplication. Let's map:
We could use:
- ... ...
- Bachelor’s degree in Computer Science, Software Engineering, or a related field (or equivalent work experience).
- 1–3 years of software development experience in a professional environment, ideally supporting ERP or business applications.
- Strong programming experience with SQL, JavaScript, and Python (required).
- Experience with version control systems (e.g., Git).
- Solid understanding of the software development life cycle (SDLC), agile methodologies, and DevOps practices.
- Experience with RESTful APIs, and familiarity with microservices architecture.
- Experience with relational and/or NoSQL databases.
- Familiarity with cloud platforms (e.g., Azure, AWS, Google Cloud).
- Exposure to or experience with Infor CloudSuite Distribution (CSD) or a comparable distribution ERP.
- Familiarity with distribution and/or warehouse business processes: order management, procurement, inventory, receiving, putaway, replenishment, shipping, and pricing.
- Strong problem-solving and critical thinking skills; excellent verbal and written communication.
- Self-motivated with the ability to work independently or within a team, with strong attention to detail and a passion for quality.
- OpenEdge ABL (Progress 4GL) development experience (a plus).
- Infor ION, PaaS, or workflow/automation experience (a plus).
- Experience with Total Warehouse Logistics (TWL) configuration and processes.
- Exposure to cloud-native architectures and modern enterprise integration frameworks.
- Experience in a multi-entity, multi-brand, or multi-warehouse environment.
About the role
...
Responsibilities
- ...
Requirements
- ...
Skills
- ...
Qualifications
but we already used Requirements; maybe we can combine education/experience under Requirements and skills under Skills. The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use any of those; we just need to not create empty sections. We have content for About the role, Responsibilities, Requirements (education/experience), Skills (technical skills and preferred experience). We could also have Qualifications but maybe we can skip if we used Requirements for education/experience and Skills for technical skills. However we have also "Preferred Experience" which could go under Skills. Thus we will output:About the role
...