Sr. Staff Engineer -M3 Technical Consultant
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 (the page already shows it) and 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.
We have:
- About Client: description of client (specializes in delivering technology solutions...). That's substantive. Could be "About the role"? Actually "About Client" is about the client, not role. But we can use "About the role" heading? The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings? Probably we should stick to those headings if appropriate. "About the role" could encompass description of role and client? Might be okay. But we have "About Client" which is about the client company. Could be placed under "About the role" or maybe we create a section "About the client"? Not in list but maybe allowed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we can create sections like "About the client", "Responsibilities", "Required Skills", "Preferred Skills", "Pay", "Benefits". However we must only create Pay/Schedule/Benefits sections if posting actually states them. We have Rate Range: $70-$73/Hr. That's pay. So we can include a Pay section. Benefits: The posting says "Non-benefitted (other than those mandated under state or federal law). Please note that this position does not include paid time off benefits. ApTask offers subsidized insurance coverage to our employees." That's benefits info (though limited). So we can include Benefits section. Schedule: Not mentioned. So we omit Schedule.
We also have "About ApTask" repeated twice; that's boilerplate about the staffing agency. Might be considered not substantive? It's about the employer (ApTask). Could be included as "About the company"? But we already have About Client. Might be considered duplication; we should remove duplicated lines. The repeated About ApTask appears twice exactly; we should keep only one instance. Also there are legal disclaimers about data collection, applicant consent etc. Those are boilerplate; we should remove them.
Thus we need to extract substantive content:
- About Client: description of client specializing in technology solutions, digital transformation, software development, IT consulting, custom software development across platforms, helps businesses modernize IT systems, adopt new technologies, transform operations, emphasis on innovation, agility, collaborative work culture, encourages employees to explore creative solutions, stay updated with latest tech trends.
- Rate Range: $70-$73/Hr.
- Job Description: Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications.
- Key Responsibilities: list bullet points.
- Required Skills: list bullet points.
- Preferred: list bullet points.
- Must have skills: Infor M3 & H5 scripting (maybe redundant with required skills). Could be considered a summary; we might incorporate into Required Skills.
- Benefits: Non-benefitted (other than those mandated under state or federal law). Position does not include paid time off benefits. ApTask offers subsidized insurance coverage to our employees.
- About ApTask: description of ApTask as leading global provider of workforce solutions, talent acquisition, African American-owned and Veteran-owned, offers staffing, recruitment, managed services, IT consulting, project management, focus on excellence, collaboration, innovation, provides opportunities for professional growth, connect businesses with top-tier professionals, optimize workforce performance, drive success across diverse industries, mission to empower organizations to thrive while fostering diverse and inclusive work environment.
We should avoid duplication: The About ApTask appears twice; we keep one.
We need to format using headings and - for lists,
for prose.
We need to decide which headings to use. Likely:
About the Client
(or About the role?). Since they gave example About the role, but we have About Client. Could use About the role to include both client and role description? Might be confusing. Better to use About the Client as heading; it's not in examples but likely acceptable. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are typical but not exclusive. So we can use About the Client.
We also need Pay section: Pay
with p containing "$70-$73 per hour".
Benefits section: Benefits
with p describing non-benefitted, no PTO, subsidized insurance.
Responsibilities: Responsibilities
with ul.
Required Skills: Required Skills
with ul.
Preferred Skills: Preferred Skills
with ul.
Maybe also a section "About ApTask" as About the Company
or About ApTask
. Since they gave example About the role, but we can use About the Company. We'll include.
We must not include headings with filler text. All sections have real content.
We must remove duplicated lines: The About ApTask appears twice; we keep one. Also the legal disclaimers etc removed.
We must preserve all substantive information: ensure we don't lose any details from the lists.
Let's extract the exact bullet points.
From the text:
Key Responsibilities:
- Design, develop, and maintain Infor M3 integrations using Infor OS, ION, MEC, APIs, and Web Services.
- Configure and support ION workflows, document flows, API Gateway, and event-driven integrations.
- Develop and troubleshoot custom solutions, extensions, SQL queries, reports, and data migration activities.
- Analyze integration issues, perform root cause analysis, and provide L2/L3 production support.
- Collaborate with functional consultants and business users to translate requirements into technical solutions.
- Support application upgrades, cloud migrations, testing, deployments, and release management.
- Prepare technical documentation, integration specifications, and knowledge transfer materials.
Required Skills:
- Knowledge of M3 Business Engine, H5 scripting (JavaScript, Angular JS, Node JS), workflows, and integration architecture.
- 5-7 years of Infor M3 technical development and integration experience.
- Strong expertise in Infor OS, ION, MEC, M3 APIs, Data Lake, and Enterprise Collaborator.
- Experience with SQL, XML, JSON, REST/SOAP APIs, and middleware technologies.
- Experience in troubleshooting integrations, performance optimization, and production support.
- Strong communication and stakeholder management skills.
Preferred:
- Experience with Infor CloudSuite M3.
- Exposure to Azure integration services, EDI, and data migration projects.
- Infor OS / ION technical certifications.
Must have skills: Infor M3 & H5 scripting (maybe redundant). We could note as part of Required Skills but we already have H5 scripting in Required Skills. Could ignore duplicate.
Now About Client paragraph: Let's capture exactly:
"About Client: The client specializes in delivering technology solutions and services to help businesses with digital transformation, software development, and IT consulting. It provides custom software development services across various platforms and technologies, catering to different industries and domains. The client helps businesses modernize their IT systems, adopt new technologies, and transform their operations to stay competitive in the digital age. Client is known for its emphasis on innovation, agility, and a collaborative work culture. The company encourages its employees to explore creative solutions and stay updated with the latest technology trends."
We need to strip the "About Client:" label maybe keep as prose.
Rate Range: "Rate Range: $70-$73/Hr". We'll put as Pay.
Job Description: "Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications."
We could incorporate this into About the role or Responsibilities? It's a summary; we could include as a brief paragraph under About the role.
But we have Responsibilities section already with detailed list. The job description summary could be placed under About the role.
We'll create sections:
About the Client
...
About the Role
Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications.
Responsibilities
...
Required Skills
...
Preferred Skills
...
Pay
$70-$73 per hour
Benefits
Non-benefitted (other than those mandated under state or federal law). This position does not include paid time off benefits. ApTask offers subsidized insurance coverage to employees.
About ApTask
ApTask is a leading global provider of workforce solutions and talent acquisition services, dedicated to shaping the future of work. As an African American-owned and Veteran-owned company, ApTask offers a comprehensive suite of services, including staffing and recruitment solutions, managed services, IT consulting, and project management. With a focus on excellence, collaboration, and innovation, ApTask provides unparalleled opportunities for professional growth and development. As a member of the ApTask team, you will have the chance to connect businesses with top-tier professionals, optimize workforce performance, and drive success across diverse industries. Join us at ApTask and be part of our mission to empower organizations to thrive while fostering a diverse and inclusive work environment.
We must ensure we didn't include any boilerplate like "Applicants may be required
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. 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. We have: - About Client: description of client (specializes in delivering technology solutions...). That's substantive. Could be "About the role"? Actually "About Client" is about the client, not role. But we can use "About the role" heading? The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings? Probably we should stick to those headings if appropriate. "About the role" could encompass description of role and client? Might be okay. But we have "About Client" which is about the client company. Could be placed under "About the role" or maybe we create a section "About the client"? Not in list but maybe allowed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we can create sections like "About the client", "Responsibilities", "Required Skills", "Preferred Skills", "Pay", "Benefits". However we must only create Pay/Schedule/Benefits sections if posting actually states them. We have Rate Range: $70-$73/Hr. That's pay. So we can include a Pay section. Benefits: The posting says "Non-benefitted (other than those mandated under state or federal law). Please note that this position does not include paid time off benefits. ApTask offers subsidized insurance coverage to our employees." That's benefits info (though limited). So we can include Benefits section. Schedule: Not mentioned. So we omit Schedule.
We also have "About ApTask" repeated twice; that's boilerplate about the staffing agency. Might be considered not substantive? It's about the employer (ApTask). Could be included as "About the company"? But we already have About Client. Might be considered duplication; we should remove duplicated lines. The repeated About ApTask appears twice exactly; we should keep only one instance. Also there are legal disclaimers about data collection, applicant consent etc. Those are boilerplate; we should remove them.
Thus we need to extract substantive content:
- About Client: description of client specializing in technology solutions, digital transformation, software development, IT consulting, custom software development across platforms, helps businesses modernize IT systems, adopt new technologies, transform operations, emphasis on innovation, agility, collaborative work culture, encourages employees to explore creative solutions, stay updated with latest tech trends.
- Rate Range: $70-$73/Hr.
- Job Description: Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications.
- Key Responsibilities: list bullet points.
- Required Skills: list bullet points.
- Preferred: list bullet points.
- Must have skills: Infor M3 & H5 scripting (maybe redundant with required skills). Could be considered a summary; we might incorporate into Required Skills.
- Benefits: Non-benefitted (other than those mandated under state or federal law). Position does not include paid time off benefits. ApTask offers subsidized insurance coverage to our employees.
- About ApTask: description of ApTask as leading global provider of workforce solutions, talent acquisition, African American-owned and Veteran-owned, offers staffing, recruitment, managed services, IT consulting, project management, focus on excellence, collaboration, innovation, provides opportunities for professional growth, connect businesses with top-tier professionals, optimize workforce performance, drive success across diverse industries, mission to empower organizations to thrive while fostering diverse and inclusive work environment.
We should avoid duplication: The About ApTask appears twice; we keep one.
We need to format using headings and - for lists,
for prose.
We need to decide which headings to use. Likely:
About the Client
(or About the role?). Since they gave example About the role, but we have About Client. Could use About the role to include both client and role description? Might be confusing. Better to use About the Client as heading; it's not in examples but likely acceptable. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are typical but not exclusive. So we can use About the Client.
We also need Pay section: Pay
with p containing "$70-$73 per hour".
Benefits section: Benefits
with p describing non-benefitted, no PTO, subsidized insurance.
Responsibilities: Responsibilities
with ul.
Required Skills: Required Skills
with ul.
Preferred Skills: Preferred Skills
with ul.
Maybe also a section "About ApTask" as About the Company
or About ApTask
. Since they gave example About the role, but we can use About the Company. We'll include.
We must not include headings with filler text. All sections have real content.
We must remove duplicated lines: The About ApTask appears twice; we keep one. Also the legal disclaimers etc removed.
We must preserve all substantive information: ensure we don't lose any details from the lists.
Let's extract the exact bullet points.
From the text:
Key Responsibilities:
- Design, develop, and maintain Infor M3 integrations using Infor OS, ION, MEC, APIs, and Web Services.
- Configure and support ION workflows, document flows, API Gateway, and event-driven integrations.
- Develop and troubleshoot custom solutions, extensions, SQL queries, reports, and data migration activities.
- Analyze integration issues, perform root cause analysis, and provide L2/L3 production support.
- Collaborate with functional consultants and business users to translate requirements into technical solutions.
- Support application upgrades, cloud migrations, testing, deployments, and release management.
- Prepare technical documentation, integration specifications, and knowledge transfer materials.
Required Skills:
- Knowledge of M3 Business Engine, H5 scripting (JavaScript, Angular JS, Node JS), workflows, and integration architecture.
- 5-7 years of Infor M3 technical development and integration experience.
- Strong expertise in Infor OS, ION, MEC, M3 APIs, Data Lake, and Enterprise Collaborator.
- Experience with SQL, XML, JSON, REST/SOAP APIs, and middleware technologies.
- Experience in troubleshooting integrations, performance optimization, and production support.
- Strong communication and stakeholder management skills.
Preferred:
- Experience with Infor CloudSuite M3.
- Exposure to Azure integration services, EDI, and data migration projects.
- Infor OS / ION technical certifications.
Must have skills: Infor M3 & H5 scripting (maybe redundant). We could note as part of Required Skills but we already have H5 scripting in Required Skills. Could ignore duplicate.
Now About Client paragraph: Let's capture exactly:
"About Client: The client specializes in delivering technology solutions and services to help businesses with digital transformation, software development, and IT consulting. It provides custom software development services across various platforms and technologies, catering to different industries and domains. The client helps businesses modernize their IT systems, adopt new technologies, and transform their operations to stay competitive in the digital age. Client is known for its emphasis on innovation, agility, and a collaborative work culture. The company encourages its employees to explore creative solutions and stay updated with the latest technology trends."
We need to strip the "About Client:" label maybe keep as prose.
Rate Range: "Rate Range: $70-$73/Hr". We'll put as Pay.
Job Description: "Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications."
We could incorporate this into About the role or Responsibilities? It's a summary; we could include as a brief paragraph under About the role.
But we have Responsibilities section already with detailed list. The job description summary could be placed under About the role.
We'll create sections:
About the Client
...
About the Role
Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications.
Responsibilities
...
Required Skills
...
Preferred Skills
...
Pay
$70-$73 per hour
Benefits
Non-benefitted (other than those mandated under state or federal law). This position does not include paid time off benefits. ApTask offers subsidized insurance coverage to employees.
About ApTask
ApTask is a leading global provider of workforce solutions and talent acquisition services, dedicated to shaping the future of work. As an African American-owned and Veteran-owned company, ApTask offers a comprehensive suite of services, including staffing and recruitment solutions, managed services, IT consulting, and project management. With a focus on excellence, collaboration, and innovation, ApTask provides unparalleled opportunities for professional growth and development. As a member of the ApTask team, you will have the chance to connect businesses with top-tier professionals, optimize workforce performance, and drive success across diverse industries. Join us at ApTask and be part of our mission to empower organizations to thrive while fostering a diverse and inclusive work environment.
We must ensure we didn't include any boilerplate like "Applicants may be required
headings and - for lists,
for prose.
We need to decide which headings to use. Likely:
About the Client
(or About the role?). Since they gave example About the role, but we have About Client. Could use About the role to include both client and role description? Might be confusing. Better to use About the Client as heading; it's not in examples but likely acceptable. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are typical but not exclusive. So we can use About the Client.
We also need Pay section: Pay
with p containing "$70-$73 per hour".
Benefits section: Benefits
with p describing non-benefitted, no PTO, subsidized insurance.
Responsibilities: Responsibilities
with ul.
Required Skills: Required Skills
with ul.
Preferred Skills: Preferred Skills
with ul.
Maybe also a section "About ApTask" as About the Company
or About ApTask
. Since they gave example About the role, but we can use About the Company. We'll include.
We must not include headings with filler text. All sections have real content.
We must remove duplicated lines: The About ApTask appears twice; we keep one. Also the legal disclaimers etc removed.
We must preserve all substantive information: ensure we don't lose any details from the lists.
Let's extract the exact bullet points.
From the text:
Key Responsibilities:
- Design, develop, and maintain Infor M3 integrations using Infor OS, ION, MEC, APIs, and Web Services.
- Configure and support ION workflows, document flows, API Gateway, and event-driven integrations.
- Develop and troubleshoot custom solutions, extensions, SQL queries, reports, and data migration activities.
- Analyze integration issues, perform root cause analysis, and provide L2/L3 production support.
- Collaborate with functional consultants and business users to translate requirements into technical solutions.
- Support application upgrades, cloud migrations, testing, deployments, and release management.
- Prepare technical documentation, integration specifications, and knowledge transfer materials.
Required Skills:
- Knowledge of M3 Business Engine, H5 scripting (JavaScript, Angular JS, Node JS), workflows, and integration architecture.
- 5-7 years of Infor M3 technical development and integration experience.
- Strong expertise in Infor OS, ION, MEC, M3 APIs, Data Lake, and Enterprise Collaborator.
- Experience with SQL, XML, JSON, REST/SOAP APIs, and middleware technologies.
- Experience in troubleshooting integrations, performance optimization, and production support.
- Strong communication and stakeholder management skills.
Preferred:
- Experience with Infor CloudSuite M3.
- Exposure to Azure integration services, EDI, and data migration projects.
- Infor OS / ION technical certifications.
Must have skills: Infor M3 & H5 scripting (maybe redundant). We could note as part of Required Skills but we already have H5 scripting in Required Skills. Could ignore duplicate.
Now About Client paragraph: Let's capture exactly:
"About Client: The client specializes in delivering technology solutions and services to help businesses with digital transformation, software development, and IT consulting. It provides custom software development services across various platforms and technologies, catering to different industries and domains. The client helps businesses modernize their IT systems, adopt new technologies, and transform their operations to stay competitive in the digital age. Client is known for its emphasis on innovation, agility, and a collaborative work culture. The company encourages its employees to explore creative solutions and stay updated with the latest technology trends."
We need to strip the "About Client:" label maybe keep as prose.
Rate Range: "Rate Range: $70-$73/Hr". We'll put as Pay.
Job Description: "Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications."
We could incorporate this into About the role or Responsibilities? It's a summary; we could include as a brief paragraph under About the role.
But we have Responsibilities section already with detailed list. The job description summary could be placed under About the role.
We'll create sections:
About the Client
...
About the Role
Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications.
Responsibilities
...
Required Skills
...
Preferred Skills
...
Pay
$70-$73 per hour
Benefits
Non-benefitted (other than those mandated under state or federal law). This position does not include paid time off benefits. ApTask offers subsidized insurance coverage to employees.
About ApTask
ApTask is a leading global provider of workforce solutions and talent acquisition services, dedicated to shaping the future of work. As an African American-owned and Veteran-owned company, ApTask offers a comprehensive suite of services, including staffing and recruitment solutions, managed services, IT consulting, and project management. With a focus on excellence, collaboration, and innovation, ApTask provides unparalleled opportunities for professional growth and development. As a member of the ApTask team, you will have the chance to connect businesses with top-tier professionals, optimize workforce performance, and drive success across diverse industries. Join us at ApTask and be part of our mission to empower organizations to thrive while fostering a diverse and inclusive work environment.
We must ensure we didn't include any boilerplate like "Applicants may be required
for prose. We need to decide which headings to use. Likely:
About the Client
(or About the role?). Since they gave example About the role, but we have About Client. Could use About the role to include both client and role description? Might be confusing. Better to use About the Client as heading; it's not in examples but likely acceptable. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are typical but not exclusive. So we can use About the Client.
We also need Pay section: Pay
with p containing "$70-$73 per hour".
Benefits section: Benefits
with p describing non-benefitted, no PTO, subsidized insurance.
Responsibilities: Responsibilities
with ul.
Required Skills: Required Skills
with ul.
Preferred Skills: Preferred Skills
with ul.
Maybe also a section "About ApTask" as About the Company
or About ApTask
. Since they gave example About the role, but we can use About the Company. We'll include.
We must not include headings with filler text. All sections have real content.
We must remove duplicated lines: The About ApTask appears twice; we keep one. Also the legal disclaimers etc removed.
We must preserve all substantive information: ensure we don't lose any details from the lists.
Let's extract the exact bullet points.
From the text:
Key Responsibilities:
- Design, develop, and maintain Infor M3 integrations using Infor OS, ION, MEC, APIs, and Web Services.
- Configure and support ION workflows, document flows, API Gateway, and event-driven integrations.
- Develop and troubleshoot custom solutions, extensions, SQL queries, reports, and data migration activities.
- Analyze integration issues, perform root cause analysis, and provide L2/L3 production support.
- Collaborate with functional consultants and business users to translate requirements into technical solutions.
- Support application upgrades, cloud migrations, testing, deployments, and release management.
- Prepare technical documentation, integration specifications, and knowledge transfer materials.
Required Skills:
- Knowledge of M3 Business Engine, H5 scripting (JavaScript, Angular JS, Node JS), workflows, and integration architecture.
- 5-7 years of Infor M3 technical development and integration experience.
- Strong expertise in Infor OS, ION, MEC, M3 APIs, Data Lake, and Enterprise Collaborator.
- Experience with SQL, XML, JSON, REST/SOAP APIs, and middleware technologies.
- Experience in troubleshooting integrations, performance optimization, and production support.
- Strong communication and stakeholder management skills.
Preferred:
- Experience with Infor CloudSuite M3.
- Exposure to Azure integration services, EDI, and data migration projects.
- Infor OS / ION technical certifications.
Must have skills: Infor M3 & H5 scripting (maybe redundant). We could note as part of Required Skills but we already have H5 scripting in Required Skills. Could ignore duplicate.
Now About Client paragraph: Let's capture exactly:
"About Client: The client specializes in delivering technology solutions and services to help businesses with digital transformation, software development, and IT consulting. It provides custom software development services across various platforms and technologies, catering to different industries and domains. The client helps businesses modernize their IT systems, adopt new technologies, and transform their operations to stay competitive in the digital age. Client is known for its emphasis on innovation, agility, and a collaborative work culture. The company encourages its employees to explore creative solutions and stay updated with the latest technology trends."
We need to strip the "About Client:" label maybe keep as prose.
Rate Range: "Rate Range: $70-$73/Hr". We'll put as Pay.
Job Description: "Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications."
We could incorporate this into About the role or Responsibilities? It's a summary; we could include as a brief paragraph under About the role.
But we have Responsibilities section already with detailed list. The job description summary could be placed under About the role.
We'll create sections:
About the Client
...
About the Role
Experienced Infor M3 Technical Consultant with 5-7 years of expertise in Infor M3 development, Infor OS, ION integrations, APIs, MEC, and cloud/on-premise system integrations. Responsible for designing, developing, troubleshooting, and supporting enterprise integrations while ensuring seamless data exchange across business applications.
Responsibilities
- ...
Required Skills
- ...
Preferred Skills
- ...
Pay
$70-$73 per hour
Benefits
Non-benefitted (other than those mandated under state or federal law). This position does not include paid time off benefits. ApTask offers subsidized insurance coverage to employees.
About ApTask
ApTask is a leading global provider of workforce solutions and talent acquisition services, dedicated to shaping the future of work. As an African American-owned and Veteran-owned company, ApTask offers a comprehensive suite of services, including staffing and recruitment solutions, managed services, IT consulting, and project management. With a focus on excellence, collaboration, and innovation, ApTask provides unparalleled opportunities for professional growth and development. As a member of the ApTask team, you will have the chance to connect businesses with top-tier professionals, optimize workforce performance, and drive success across diverse industries. Join us at ApTask and be part of our mission to empower organizations to thrive while fostering a diverse and inclusive work environment.
We must ensure we didn't include any boilerplate like "Applicants may be required