ZipRecruiter

Log In

1

Dell Boomi Developer Jobs Near Me

Stantec

Senior Data Architect

Columbus, OH · On-site

$65 - $87/hr

... e.g., MuleSoft, Dell Boomi). Company : Stantec is a professional services company that provides engineering, architecture, design, and consulting services. Founded in 1954, the company is ...

All JobsDell Boomi Developer JobsDell Boomi Developer Jobs Near Me

Dell Boomi Developer information

See salary details

$40K

$129.3K

$158.5K

How much do dell boomi developer jobs pay per year?

As of Aug 23, 2026, the average yearly pay for dell boomi developer in the United States is $129,348.00, according to ZipRecruiter salary data. Most workers in this role earn between $106,000.00 and $157,000.00 per year, depending on experience, location, and employer.

What are popular job titles related to Dell Boomi Developer jobs?

For Dell Boomi Developer jobs, the most frequently searched job titles are:

What job categories do people searching Dell Boomi Developer jobs look for?

The top searched job categories for Dell Boomi Developer jobs are:

What cities are hiring for Dell Boomi Developer jobs?

Cities with the most Dell Boomi Developer job openings:

What states have the most Dell Boomi Developer jobs?

States with the most job openings for Dell Boomi Developer jobs include:

Dell Boomi Developer jobs near you
A map of the United States highlighting the number of Dell Boomi Developer job openings by state according to ZipRecruiter. The image is accompanied by a detailed chart listing the number of Dell Boomi Developer job openings in each state, with California having the most at 2 and Hawaii the least at 0.

Senior Middleware Architect / Engineer

HR Pundits

Columbus, OH • On-site

Other

Posted 4 days ago

Job description

Key Responsibilities:

Design, build, and maintain middleware integration layers connecting OT systems (SCADA, smart meter/AMI, outage management) with enterprise IT (billing, CRM, SAP/ERP, data warehouse).

Implement and operate enterprise integration platforms MuleSoft, IBM WebMethods/IIB, TIBCO, Dell Boomi, or Azure Integration Services (platform per candidate specialization).

Build and maintain REST/SOAP APIs, event-driven architectures, and message queues (Kafka, IBM MQ, RabbitMQ) for real-time and batch data exchange.

Ensure integration security, reliability, and compliance with NERC CIP and other utility regulatory standards.

Modernize and troubleshoot legacy-to-modern integrations, including mainframe and SAP PI/PO connections.

Partner with grid operations, billing, customer service, and data teams to translate business requirements into integration architecture.

Produce architecture and data-flow documentation sufficient for audit and regulatory review.

Required Qualifications:

12+ years of middleware/integration engineering experience, with demonstrable delivery in utilities or another regulated industry (financial services, healthcare, energy).

Hands-on expertise in at least one major enterprise integration platform: MuleSoft, IBM WebMethods, TIBCO, Boomi, or Azure Logic Apps/Integration Services.

Direct experience integrating OT/SCADA or IoT/AMI systems with enterprise IT non-negotiable for this utility environment.

Strong API design (REST/SOAP) and event-streaming/message-queue experience (Kafka, RabbitMQ, IBM MQ).

Working knowledge of regulatory/compliance frameworks relevant to utilities (NERC CIP) or equivalent regulated-industry standards.

Bachelor s degree in computer science, Engineering, or related field, or equivalent hands-on experience.

Preferred Qualifications:

SAP PI/PO or SAP Integration Suite experience.

Cloud integration experience on Azure or AWS.

Prior direct employment or delivery experience at a utility, energy, or critical-infrastructure company.

Interview Requirement Use Case Presentation:

Every candidate must present 3 real-world middleware integration use cases they personally designed or delivered, ideally in a utility or other regulated-industry setting. For each use case, candidates should address:

Business problem and context what systems needed to connect and why.

Technical approach and platform used architecture, tools, and integration pattern.

Integration complexity systems connected, data volume, latency/throughput requirements.

Outcome and business impact measurable result.

Compliance/security considerations addressed, if applicable (e.g., NERC CIP, data protection, access control).

Apply