Maximo Application Suite (MAS) Technical Engineer
Leidos · Wallops Island, VA · 3 wk ago
On-siteEngineering$108k–$195k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent. Remove boilerplate.
We need to parse the description.
Key sections:
- About the role: The description includes "The AEGIS program at Leidos seeking a highly skilled Maximo Application Suite (MAS) Technical Engineer with 8+ years of Maximo experience and advanced Linux proficiency. This role provides architectural leadership, technical direction, and hands on implementation expertise to ensure a secure, scalable, and high performing MAS environment supporting NASA’s Enterprise operations. The engineer will work closely with cross organizational leadership, stakeholders, vendors, and technical teams to ensure consistent platform reliability and adherence to Enterprise integration standards."
That's about the role.
- Responsibilities: List of primary responsibilities (bulleted). We need to extract each bullet.
List:
- Prepare and present project‑related information to executive, leadership, and center teams.
- Lead installation, configuration, upgrades, patching, and troubleshooting activities for MAS.
- Lead technical design of Enterprise integration architecture supporting NASA Enterprise systems.
- Lead implementation and configuration of secure API management and authentication standards.
- Define API messages, error handling, and monitoring strategies for integrations.
- Perform complex application configuration and develop automation scripts using Python, XML, JavaScript, and JSON.
- Develop and maintain complex scripting for MAS configurations across multiple environments.
- Configure and support Maximo Mobile, including SSO authentication implementations.
- Create application configurations in Maximo Mobile using the Maximo Application Framework (MAF) Configuration application to modify MAS configurations.
- Manage and support Maximo Application Suite user synchronization with Microsoft Entra ID.
- Perform data modeling to support Business Intelligence (BI) reporting needs.
- Utilize Jira Service Management (or comparable ticketing systems) to manage and track technical issues and service requests.
- Requirements: Basic Qualifications list.
List:
- Bachelor’s degree in Information Systems, Computer Science, Engineering, or related field.
- 8+ years of Maximo technical engineering experience.
- Demonstrated advanced expertise in IBM Maximo architecture, automation scripting, the Maximo Integration Framework (MIF), and REST API integrations.
- Extensive hands-on experience with BIRT reporting and Microsoft Power BI, including expertise in reporting requirements and data modeling.
- Demonstrated advanced knowledge and hands-on experience with Linux operating systems and architecture, including scripting, system operations, and performance management.
- Hands‑on experience with MAS installation, configuration, troubleshooting, and patching.
- Demonstrated working knowledge of OpenShift Container Platform and containerization, with a strong understanding of enterprise Maximo Application Suite (MAS) deployments.
- Working knowledge of Maximo Mobile, SSO solutions, and MAF configuration.
- Experience developing automation scripts using Python, XML, JavaScript, and JSON.
- Familiarity with secure API management and authentication frameworks.
- Strong written and verbal communication skills and proven ability to interface with cross‑functional technical and leadership teams.
- Experience using Jira Service Management or similar platforms for issue tracking.
- Ability to work on-site five (5) days per week.
- Qualifications: Preferred Qualifications list.
List:
- Experience supporting NASA or other federal enterprise Maximo environments.
- Experience designing and maintaining Enterprise‑level integration architectures.
- Experience with Enterprise(multi-org, multi-site)reporting platforms and data segregation enforcement via Row-Level Security (RLS).
- Familiarity with MAS licensing models, user synchronization methods, or large‑scale environment deployments.
- Experience with performance tuning, high‑availability configurations, or MAS observability tools.
- Experience with IBM TRIRIGA and/or Maximo Real Estate and Facilities (MREF) module.
- IBM Maximo Certifications: Certified Deployment Professional or IBM Certified Administrator.
- Skills: Might be covered in responsibilities/qualifications but we could extract specific skill mentions: Linux, Python, XML, JavaScript, JSON, MAS, Maximo Mobile, SSO, MAF, Jira, etc. However we should not duplicate content. The instruction: Use sections only when posting has real specific content. We have content for About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred), Skills? Could combine skills into Requirements or Qualifications. But we could create a Skills section if there is explicit skill list. The posting includes many skill mentions but they are within qualifications. Might be better to not create a separate Skills section to avoid thin sections. However we could create Skills if we have distinct skill list not covered elsewhere. The posting includes "Strong written and verbal communication skills", "Experience developing automation scripts using Python, XML, JavaScript, and JSON", "Familiarity with secure API management and authentication frameworks". Those are skills. But they are already in Basic Qualifications. So we could keep them under Requirements (Basic Qualifications). The instruction: Prefer a few substantive sections over many thin ones. So we likely will have About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred), Pay, Benefits? Benefits: The posting includes a Pay And Benefits section later: "Pay and benefits are fundamental to any career decision... Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." That's generic but still specific benefits list. It mentions competitive compensation, health and wellness, income protection, paid leave, retirement. That's substantive enough for Benefits section. Also Pay: The posting includes Pay Range: "$107,900.00 - $195,050.00". Also note that it's a guideline. So we can include Pay section with that range. Schedule: The posting includes "Ability to work on-site five (5) days per week." That's schedule info. So we can include Schedule section with that.
We must not include boilerplate like EEO, scam warnings, etc.
Now produce HTML fragment with headings for each section. Use
for each section. Use - for lists. Use
for prose.
We need to ensure we don't repeat job title. Not include any extra.
Let's craft:
About the role
The AEGIS program at Leidos is seeking a highly skilled Maximo Application Suite (MAS) Technical Engineer with 8+ years of Maximo experience and advanced Linux proficiency. This role provides architectural leadership, technical direction, and hands‑on implementation expertise to ensure a secure, scalable, and high‑performing MAS environment supporting NASA’s Enterprise operations. The engineer will work closely with cross‑organizational leadership, stakeholders, vendors, and technical teams to ensure consistent platform reliability and adherence to Enterprise integration standards.
Responsibilities
- Prepare and present project‑related information to executive, leadership, and center teams.
- Lead installation, configuration, upgrades, patching, and troubleshooting activities for MAS.
- Lead technical design of Enterprise integration architecture supporting NASA Enterprise systems.
- Lead implementation and configuration of secure API management and authentication standards.
- Define API messages, error handling, and monitoring strategies for integrations.
- Perform complex application configuration and develop automation scripts using Python, XML, JavaScript, and JSON.
- Develop and maintain complex scripting for MAS configurations across multiple environments.
- Configure and support Maximo Mobile, including SSO authentication implementations.
- Create application configurations in Maximo Mobile using the Maximo Application Framework (MAF) Configuration application to modify MAS configurations.
- Manage and support Maximo Application Suite user synchronization with Microsoft Entra ID.
- Perform data modeling to support Business Intelligence (BI) reporting needs.
- Utilize Jira Service Management (or comparable ticketing systems) to manage and track technical issues and service requests.
Requirements
- Bachelor’s degree in Information Systems, Computer Science, Engineering, or related field.
- 8+ years of Maximo technical engineering experience.
- Demonstrated advanced expertise in IBM Maximo architecture, automation scripting, the Maximo Integration Framework (MIF), and REST API integrations.
- Extensive hands‑on experience with BIRT reporting and Microsoft Power BI, including expertise in reporting requirements and data modeling.
- Demonstrated advanced knowledge and hands‑on experience with Linux operating systems and architecture, including scripting, system operations, and performance management.
- Hands‑on experience with MAS installation, configuration, troubleshooting, and patching.
- Demonstrated working knowledge of OpenShift Container Platform and containerization, with a strong understanding of enterprise Maximo Application Suite (MAS) deployments.
- Working knowledge of Maximo Mobile, SSO solutions, and MAF configuration.
- Experience developing automation scripts using Python, XML, JavaScript, and JSON.
- Familiarity with secure API management and authentication frameworks.
- Strong written and verbal communication skills and proven ability to interface with cross‑functional technical and leadership teams.
- Experience using Jira Service Management or similar platforms for issue tracking.
- Ability to work on‑site five (5) days per week.
Qualifications
- Experience supporting NASA or other federal enterprise Maximo environments.
- Experience designing and maintaining Enterprise‑level integration architectures.
- Experience with Enterprise (multi‑org, multi‑site) reporting platforms and data segregation enforcement via Row‑Level Security (RLS).
- Familiarity with MAS licensing models, user synchronization methods, or large‑scale environment deployments.
- Experience with performance tuning, high‑availability configurations, or MAS observability tools.
- Experience with IBM TRIRIGA and/or Maximo Real Estate and Facilities (MREF) module.
- IBM Maximo Certifications: Certified Deployment Professional or IBM Certified Administrator.
Pay
Pay Range: $107,900.00 - $195,050.00 (Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary.)
Benefits
- Competitive compensation
- Health and Wellness programs
- Income Protection
- Paid Leave
- Retirement
Schedule
Ability to work on‑site five (5) days per week.
Check for any duplicated content: The schedule line also appears in Requirements (Ability to work on-site five days per week). That's duplicated. We should avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we include schedule section, we still need to keep that info somewhere. Could we remove it from Requirements to avoid duplication? But then we would be omitting that requirement. The requirement is a substantive detail; we need to keep it. We could keep it in Requirements and not have a separate Schedule section, or we could keep both but that would duplicate. The instruction says "Preserve ALL substantive information". Duplication is not prohibited explicitly, but we should avoid unnecessary duplication? It didn't forbid duplication, but better to avoid redundancy. However the schedule is a requirement; we could keep it under Requirements and not create a separate Schedule section. But the instruction says to include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (ability to work on-site five days per week). So we could include Schedule section with that info, and we could also keep it in Requirements? That would be duplication. To avoid duplication, we could move it to Schedule and remove from Requirements. But then we lose it from Requirements which is a qualification. However the requirement is about ability to work on-site; it's more of a schedule requirement than a qualification. It could be considered under Requirements but also schedule. The instruction: "Prefer a few substantive
for prose. We need to ensure we don't repeat job title. Not include any extra. Let's craft:
About the role
The AEGIS program at Leidos is seeking a highly skilled Maximo Application Suite (MAS) Technical Engineer with 8+ years of Maximo experience and advanced Linux proficiency. This role provides architectural leadership, technical direction, and hands‑on implementation expertise to ensure a secure, scalable, and high‑performing MAS environment supporting NASA’s Enterprise operations. The engineer will work closely with cross‑organizational leadership, stakeholders, vendors, and technical teams to ensure consistent platform reliability and adherence to Enterprise integration standards.
Responsibilities
- Prepare and present project‑related information to executive, leadership, and center teams.
- Lead installation, configuration, upgrades, patching, and troubleshooting activities for MAS.
- Lead technical design of Enterprise integration architecture supporting NASA Enterprise systems.
- Lead implementation and configuration of secure API management and authentication standards.
- Define API messages, error handling, and monitoring strategies for integrations.
- Perform complex application configuration and develop automation scripts using Python, XML, JavaScript, and JSON.
- Develop and maintain complex scripting for MAS configurations across multiple environments.
- Configure and support Maximo Mobile, including SSO authentication implementations.
- Create application configurations in Maximo Mobile using the Maximo Application Framework (MAF) Configuration application to modify MAS configurations.
- Manage and support Maximo Application Suite user synchronization with Microsoft Entra ID.
- Perform data modeling to support Business Intelligence (BI) reporting needs.
- Utilize Jira Service Management (or comparable ticketing systems) to manage and track technical issues and service requests.
Requirements
- Bachelor’s degree in Information Systems, Computer Science, Engineering, or related field.
- 8+ years of Maximo technical engineering experience.
- Demonstrated advanced expertise in IBM Maximo architecture, automation scripting, the Maximo Integration Framework (MIF), and REST API integrations.
- Extensive hands‑on experience with BIRT reporting and Microsoft Power BI, including expertise in reporting requirements and data modeling.
- Demonstrated advanced knowledge and hands‑on experience with Linux operating systems and architecture, including scripting, system operations, and performance management.
- Hands‑on experience with MAS installation, configuration, troubleshooting, and patching.
- Demonstrated working knowledge of OpenShift Container Platform and containerization, with a strong understanding of enterprise Maximo Application Suite (MAS) deployments.
- Working knowledge of Maximo Mobile, SSO solutions, and MAF configuration.
- Experience developing automation scripts using Python, XML, JavaScript, and JSON.
- Familiarity with secure API management and authentication frameworks.
- Strong written and verbal communication skills and proven ability to interface with cross‑functional technical and leadership teams.
- Experience using Jira Service Management or similar platforms for issue tracking.
- Ability to work on‑site five (5) days per week.
Qualifications
- Experience supporting NASA or other federal enterprise Maximo environments.
- Experience designing and maintaining Enterprise‑level integration architectures.
- Experience with Enterprise (multi‑org, multi‑site) reporting platforms and data segregation enforcement via Row‑Level Security (RLS).
- Familiarity with MAS licensing models, user synchronization methods, or large‑scale environment deployments.
- Experience with performance tuning, high‑availability configurations, or MAS observability tools.
- Experience with IBM TRIRIGA and/or Maximo Real Estate and Facilities (MREF) module.
- IBM Maximo Certifications: Certified Deployment Professional or IBM Certified Administrator.
Pay
Pay Range: $107,900.00 - $195,050.00 (Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary.)
Benefits
- Competitive compensation
- Health and Wellness programs
- Income Protection
- Paid Leave
- Retirement
Schedule
Ability to work on‑site five (5) days per week.
Check for any duplicated content: The schedule line also appears in Requirements (Ability to work on-site five days per week). That's duplicated. We should avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we include schedule section, we still need to keep that info somewhere. Could we remove it from Requirements to avoid duplication? But then we would be omitting that requirement. The requirement is a substantive detail; we need to keep it. We could keep it in Requirements and not have a separate Schedule section, or we could keep both but that would duplicate. The instruction says "Preserve ALL substantive information". Duplication is not prohibited explicitly, but we should avoid unnecessary duplication? It didn't forbid duplication, but better to avoid redundancy. However the schedule is a requirement; we could keep it under Requirements and not create a separate Schedule section. But the instruction says to include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (ability to work on-site five days per week). So we could include Schedule section with that info, and we could also keep it in Requirements? That would be duplication. To avoid duplication, we could move it to Schedule and remove from Requirements. But then we lose it from Requirements which is a qualification. However the requirement is about ability to work on-site; it's more of a schedule requirement than a qualification. It could be considered under Requirements but also schedule. The instruction: "Prefer a few substantive