Boomi RunTime Support Specialist (REMOTE)
Donnelly & Moore Corporation · New York, NY · 1 mo ago
RemoteRemoteOTHRFull-time
We need to output only HTML fragment, using for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. We need to preserve all substantive info, remove boilerplate. The posting includes sections: description, responsibilities, required qualifications, preferred qualifications. Also mention remote role, 12+ month, need to visit headquarters once for identity verification. Also mention on-call support mandatory. Also mention Boomi Runtime Support Specialist role.
We need to decide sections: About the role (maybe summary), Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (maybe combine?), Benefits (none given), Pay (none), Schedule (maybe mention remote, on-call, 12+ month). Since we should only include sections when posting has real specific content. There's no explicit benefits, pay, schedule details besides remote and on-call and duration. Could put schedule under "Schedule" maybe mention remote, on-call, 12+ month contract, occasional HQ visit. But schedule is not explicitly given; but we can infer schedule: remote role, on-call support mandatory, 12+ month contract, occasional HQ visit. That's schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state remote, on-call, 12+ month, occasional HQ visit. That's schedule info. So we can include a Schedule section.
Benefits: none stated, so omit.
Pay: none stated, omit.
Skills: we could list required qualifications as skills? But we have Required Qualifications and Preferred Qualifications sections. Could map to Requirements and Qualifications. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which headings to use. We have content for About the role (summary), Responsibilities (key responsibilities), Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe we could combine required and preferred? But we already have Requirements and Qualifications). Could also have Skills separate but we might not have explicit skills list beyond qualifications. Might be better to not create Skills if no explicit skill list beyond qualifications. However we could treat required qualifications as Requirements, preferred as Qualifications. That seems fine.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
We must not repeat job title as heading. So About the role heading
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. We need to preserve all substantive info, remove boilerplate. The posting includes sections: description, responsibilities, required qualifications, preferred qualifications. Also mention remote role, 12+ month, need to visit headquarters once for identity verification. Also mention on-call support mandatory. Also mention Boomi Runtime Support Specialist role.
We need to decide sections: About the role (maybe summary), Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (maybe combine?), Benefits (none given), Pay (none), Schedule (maybe mention remote, on-call, 12+ month). Since we should only include sections when posting has real specific content. There's no explicit benefits, pay, schedule details besides remote and on-call and duration. Could put schedule under "Schedule" maybe mention remote, on-call, 12+ month contract, occasional HQ visit. But schedule is not explicitly given; but we can infer schedule: remote role, on-call support mandatory, 12+ month contract, occasional HQ visit. That's schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state remote, on-call, 12+ month, occasional HQ visit. That's schedule info. So we can include a Schedule section.
Benefits: none stated, so omit.
Pay: none stated, omit.
Skills: we could list required qualifications as skills? But we have Required Qualifications and Preferred Qualifications sections. Could map to Requirements and Qualifications. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which headings to use. We have content for About the role (summary), Responsibilities (key responsibilities), Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe we could combine required and preferred? But we already have Requirements and Qualifications). Could also have Skills separate but we might not have explicit skills list beyond qualifications. Might be better to not create Skills if no explicit skill list beyond qualifications. However we could treat required qualifications as Requirements, preferred as Qualifications. That seems fine.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
We must not repeat job title as heading. So About the role heading About the role
.
Now we need to extract substantive info.
About the role: Our Utility Client in NYC is looking for a Boomi Runtime Support Specialist for a 12+month REMOTE role. While the work will be remote the hired candidate will need to visit our headquarters once for identity verification purposes as per our cyber security guidelines. Any additional required on site visit will be announced with plenty of lead time if required.
Also mention that the role focuses on day-to-day reliability, availability, security, performance, operational health of established Runtimes and Runtime Clusters. Provide production support, troubleshoot, manage access, monitor, coordinate, recommend improvements.
We can summarize but must preserve all substantive info; we cannot invent or summarize away detail. However we can condense but must keep all details. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details. We need to include all details from the posting. So we need to include everything: remote, 12+ month, HQ visit once, additional on-site visits announced, role responsibilities list, required qualifications list, preferred qualifications list.
Thus we need to output all those details in the HTML. We can keep them as paragraphs or lists.
We must not repeat job title as heading. So we will not have a heading "Boomi Runtime Support Specialist". We'll just have sections.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, required qualifications, preferred qualifications we should use lists.
We need to use
for prose.
Thus structure:
About the role
Our Utility Client in NYC is looking for a Boomi Runtime Support Specialist for a 12+month REMOTE role. While the work will be remote the hired candidate will need to visit our headquarters once for identity verification purposes as per our cyber security guidelines. Any additional required on site visit will be announced with plenty of lead time if required.
Maybe also include that the role focuses on day-to-day reliability, availability, security, performance, operational health of already-established Runtimes and Runtime Clusters. That's from the description. Could be part of About the role or Responsibilities. Probably better to put in About the role: a brief summary of role purpose.
But we must preserve all details; we can include that sentence in About the role.
Now Responsibilities: we have a big list under "Key Responsibilities" with subheadings: Existing Runtime Environment Support, Runtime Administration and Maintenance, Monitoring and Performance, Security and Access Management, Disaster Recovery and Business Continuity, Collaboration and Continuous Improvement. Each has bullet-like sentences. We need to turn each duty into - . We could group under subheadings? The instruction only says use
for section headings; we could also use for subheadings? Not specified but we can still use if needed, but they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just make a flat list of responsibilities without subheadings, but we might lose some grouping. However we must preserve all substantive information; grouping is not required. So we can just list each responsibility as a
- . Ensure we capture all sentences.
Let's extract responsibilities bullet points:
From "Existing Runtime Environment Support":
- Provide day-to-day operational support for Client’s existing Boomi Runtimes, Runtime Clusters, and associated platform components.
- This role requires oncall support for the production environment.
- Maintain the current Boomi Runtime architecture and Atom topology, making controlled improvements as business and technical requirements evolve.
- Support production, test, and development Runtime environments while meeting company SLA's.
- Investigate and resolve Runtime availability, deployment, execution, connectivity, and configuration issues.
- Respond to incidents and service requests related to the Boomi platform.
- Coordinate with application and integration developers when issues involve process design, deployment, connectivity, or runtime execution.
- Support change management activities, including configuration updates, maintenance, upgrades, and controlled platform changes.
- Maintain operational runbooks, support procedures, architecture diagrams, and configuration documentation
From "Runtime Administration and Maintenance":
- Manage the installation, configuration, patching, upgrades, and ongoing maintenance of existing Boomi Runtimes and Runtime Clusters.
- Oversee Runtime configuration and high-availability settings.
- Validate Runtime health following maintenance, configuration changes, deployments, or infrastructure updates.
- Review Runtime logs, system metrics, process execution information, and error conditions.
- Coordinate with Infrastructure teams on operating system, server, network, storage, certificate, and connectivity dependencies.
- Ensure Runtime configurations remain consistent with approved standards and operational requirements.
From "Monitoring and Performance":
- Monitor the health, availability, capacity, and performance of the existing Boomi Runtime environment.
- Proactively identify resource constraints, recurring errors, capacity concerns, and other conditions that could affect operations.
- Evaluate and tune Runtime performance parameters based on Client’s integration workload.
- Review processing volumes, execution times, queue behavior, resource utilization, and failure patterns.
- Develop and maintain monitoring, alerting, and escalation procedures.
- Resolve issues before they result in user impact or business disruption.
From "Security and Access Management":
- Manage Boomi user access, roles, permissions, and custom role creation.
- Troubleshoot user access, authentication, authorization, and platform functionality issues.
- Review access requests and configuration changes in accordance with established security and governance procedures.
- Ensure the existing Runtime architecture and operational practices comply with applicable security standards and access-control requirements.
- Collaborate with IT Security on access reviews, security findings, vulnerability remediation, audit requests, and compliance requirements.
- Support the secure management of certificates, credentials, endpoints, and other Runtime dependencies
From "Disaster Recovery and Business Continuity":
- Maintain and improve disaster recovery strategies for the existing Boomi Runtime environment.
- Document Runtime recovery procedures, dependencies, recovery objectives, and escalation paths.
- Participate in disaster recovery exercises and validate the ability to restore or fail over Runtime services.
- Identify gaps in the current recovery approach and recommend corrective actions.
- Coordinate with Infrastructure, application, and security teams during recovery planning and testing.
From "Collaboration and Continuous Improvement":
- Collaborate with Infrastructure, application developers, IT Security, and other technology teams to resolve platform issues and fulfill operational requirements.
- Provide technical guidance on Runtime-related incidents, changes, and integration deployments.
- Review recurring incidents and recommend permanent fixes.
- Identify opportunities to improve monitoring, automation, documentation, platform resilience, and support processes.
- Assist with future Runtime architecture changes, expansions, migrations, or capacity planning as needed.
Now Required Qualifications list:
- Experience providing production support for an existing Production Boomi environment.
- On call support is mandatory.
- Hands-on experience administering Boomi Runtimes, Runtime Clusters, and Atom topology.
- Experience troubleshooting Runtime availability, deployment, execution, connectivity, configuration, and performance issues.
- Experience with Runtime installation, configuration, maintenance, upgrades, and high-availability settings.
- Experience monitoring enterprise integration platforms and responding to operational incidents.
- Experience managing users, roles, permissions, custom roles, and access-related issues in Boomi.
- Knowledge of disaster recovery and business continuity concepts for integration platforms.
- Understanding of enterprise security standards, access controls, certificates, credentials, and compliance requirements.
- Experience working with Infrastructure, application development, and IT Security teams.
- Strong incident management, troubleshooting, documentation, and communication skills.
Preferred Qualifications list:
- Experience supporting Boomi in a large enterprise, utility, or regulated environment.
- Experience supporting clustered, highly available, or distributed Runtime environments.
- Familiarity with enterprise monitoring, logging, alerting, and IT service management tools.
- Understanding of networking concepts, including DNS, firewalls, proxies, certificates, and connectivity troubleshooting.
- Experience with infrastructure automation or configuration management.
- Boomi certification or equivalent integration-platform experience.
- Experience developing operational runbooks, knowledge articles, and disaster recovery procedures.
Now Schedule: we have remote, 12+ month, on-call support mandatory, occasional HQ visit for identity verification, additional on-site visits announced with lead time.
We can put in Schedule section:
Schedule
- Remote work (12+ month contract)
- On-call support required
- One-time headquarters visit for identity verification (additional on-site visits announced with lead time as needed)
Now we need to ensure we don't include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not repeat job title as heading. We didn't.
We must not put Job ID/requisition numbers as headings. There's "#IND1" at end; that's likely a tag; we should drop it.
Now output only HTML fragment.
Let's craft:
About the role
Our Utility Client in NYC is looking for a Boomi Runtime Support Specialist for a 12+month REMOTE role. While the work will be remote the hired candidate will need to visit our headquarters once for identity verification purposes as per our cyber security guidelines. Any additional required on site visit will be announced with plenty of lead time if required. The role focuses on the day-to-day reliability, availability, security, performance, and operational health of already-established Boomi Runtimes and Runtime Clusters, providing production support, troubleshooting Runtime and integration issues, managing access and configuration changes, monitoring platform health, and coordinating with Infrastructure, application development, and IT Security teams to resolve problems and maintain compliance. The specialist will also recommend and implement improvements to the existing Boomi architecture without disrupting active integrations.
Responsibilities
for prose. Thus structure:
About the role
Our Utility Client in NYC is looking for a Boomi Runtime Support Specialist for a 12+month REMOTE role. While the work will be remote the hired candidate will need to visit our headquarters once for identity verification purposes as per our cyber security guidelines. Any additional required on site visit will be announced with plenty of lead time if required.
Maybe also include that the role focuses on day-to-day reliability, availability, security, performance, operational health of already-established Runtimes and Runtime Clusters. That's from the description. Could be part of About the role or Responsibilities. Probably better to put in About the role: a brief summary of role purpose. But we must preserve all details; we can include that sentence in About the role. Now Responsibilities: we have a big list under "Key Responsibilities" with subheadings: Existing Runtime Environment Support, Runtime Administration and Maintenance, Monitoring and Performance, Security and Access Management, Disaster Recovery and Business Continuity, Collaboration and Continuous Improvement. Each has bullet-like sentences. We need to turn each duty into for section headings; we could also use for subheadings? Not specified but we can still use if needed, but they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just make a flat list of responsibilities without subheadings, but we might lose some grouping. However we must preserve all substantive information; grouping is not required. So we can just list each responsibility as a
if needed, but they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just make a flat list of responsibilities without subheadings, but we might lose some grouping. However we must preserve all substantive information; grouping is not required. So we can just list each responsibility as a
Schedule
- Remote work (12+ month contract)
- On-call support required
- One-time headquarters visit for identity verification (additional on-site visits announced with lead time as needed)
About the role
Our Utility Client in NYC is looking for a Boomi Runtime Support Specialist for a 12+month REMOTE role. While the work will be remote the hired candidate will need to visit our headquarters once for identity verification purposes as per our cyber security guidelines. Any additional required on site visit will be announced with plenty of lead time if required. The role focuses on the day-to-day reliability, availability, security, performance, and operational health of already-established Boomi Runtimes and Runtime Clusters, providing production support, troubleshooting Runtime and integration issues, managing access and configuration changes, monitoring platform health, and coordinating with Infrastructure, application development, and IT Security teams to resolve problems and maintain compliance. The specialist will also recommend and implement improvements to the existing Boomi architecture without disrupting active integrations.