Business Rules Developer

CoSourcing Partners Inc.; Miami (FL); Hybride; USD 90 000 - 130 000; Plein temps

Résumé du poste

CoSourcing Partners Inc. is seeking a Business Rules Developer for a 3-Month Contract-to-Hire in Miami, FL with remote options.

You will analyze requirements and design, develop, test, deploy, and improve rule-based solutions for the Trident program, collaborating with Product Owners, stakeholders, Enterprise Architecture, and delivery teams to translate requirements into scalable rules. You will assess existing rules, improve automation, support implementations, and resolve production issues.

Responsabilités

• Deliver Reliable Business-Rule Solutions within the first 3–6 months, translating approved requirements into tested, deployable rules in the Trident rules-management environment.
• Improve Rule Quality and Operational Efficiency within 6–9 months by simplifying logic, reducing duplication, improving data quality, and increasing automation while minimizing disruption to dependent systems.
• Strengthen Rules-Management Operations over the first year by documenting configurations, testing artifacts, procedures, and knowledge-transfer materials; ensuring smoother releases and better long-term support.

Description du poste

Position

Business Rules Developer

Department

Workflow / Business Process Management and Case Management

Location

Miami, FL / Remote

Employment Type

3-Month Contract-to-Hire

Role Overview

The Business Rules Developer will analyze business requirements, operating processes, and system functionality to design, develop, test, deploy, and improve business rules supporting the Trident program. This role partners with Product Owners, business stakeholders, Enterprise Architecture, and delivery teams to translate requirements into scalable, maintainable rule-based solutions. The developer will also assess existing rules, improve automation and decision consistency, support implementations and releases, and resolve production issues. Strong documentation, testing discipline, and cross-functional collaboration are essential. Success will be measured by rule quality, delivery reliability, production stability, and the ability to improve business-process efficiency.

Employee Value Proposition

Purpose: Help improve how important business decisions and processes are executed by creating reliable, scalable rules that increase automation, consistency, and operational effectiveness.

Growth: Build deeper expertise across business rules, workflow, business process management, case management, architecture, testing, and production operations while working with cross-functional teams on high-impact initiatives.

Motivators: This role is ideal for someone who enjoys translating complex business needs into logical solutions, improving existing processes, solving production problems, and seeing measurable results from their work.

Major Performance Objectives

1. 1. Deliver Reliable Business-Rule Solutions. During the first three to six months, translate approved business requirements into configured, tested, and deployable business rules within the designated rules-management environment. Work closely with stakeholders and delivery teams to ensure solutions are accurate, scalable, and aligned with workflow and case-management processes. Success will be measured by on-time delivery, stakeholder acceptance, successful testing, and low post-release defect levels.

2. 2. Improve Rule Quality and Operational Efficiency. Within the first six to nine months, review existing business rules and identify opportunities to simplify logic, eliminate duplication, improve data quality, increase automation, and strengthen decision consistency. Implement approved enhancements while minimizing disruption to dependent systems and processes. Success will be measured by fewer defects, fewer recurring issues, reduced manual intervention, and improved maintainability.

3. 3. Strengthen Rules-Management Operations. Over the first year, improve the way business rules are documented, tested, released, supported, and maintained. Develop clear configuration specifications, testing artifacts, operating procedures, and knowledge-transfer materials. Success will be measured by smoother releases, faster issue resolution, stronger documentation, and improved long-term supportability.

Critical Subtasks

1. 1. Assess the Current Environment. During the first 30 to 60 days, build a working understanding of the Trident program, major workflows, case-management processes, existing rules, dependencies, and current production issues. Review available documentation, testing artifacts, and change history and identify immediate risks and improvement opportunities. Success will be measured by a clear assessment and agreed-upon priorities.

2. 2. Establish a 30-60-90 Day Plan. Within the first 30 days, create a practical action plan covering knowledge acquisition, assigned rule development, testing, documentation, and upcoming release commitments. Update the plan as priorities and technical findings evolve. Success will be measured by timely completion of commitments and increasing ownership of assigned work.

3. 3. Translate Requirements into Rule Designs. Work with Product Owners, business stakeholders, architects, and delivery teams to clarify requirements and convert them into logical, scalable, and maintainable rule structures. Identify conflicting requirements, dependencies, edge cases, and unclear logic before development begins. Success will be measured by stakeholder alignment and reduced rework.

4. 4. Execute Development, Testing, and Release Activities. Configure and develop business rules, perform unit testing, support system integration testing, correct defects, and participate in deployment activities. Maintain traceability between requirements, rule logic, testing evidence, and final implementation. Success will be measured by schedule adherence, testing completeness, and successful production releases.

5. 5. Resolve Production Issues. Investigate rule behavior, data conditions, workflow dependencies, and recent changes to determine root causes of business-rule-related incidents. Implement corrective actions, validate the solution, and document findings. Success will be measured by resolution speed and reduction in repeat issues.

6. 6. Maintain Documentation and Knowledge Transfer. Maintain business-rule documentation, configuration specifications, test artifacts, release information, operational procedures, and support materials. Participate in release planning, change management, production readiness, and ongoing rule administration. Success will be measured by documentation quality, smoother handoffs, and reduced support gaps.

7. 7. Continuously Evaluate and Integrate AI to Improve Performance. Within the first 90 to 180 days, identify ways AI and automation can improve requirements analysis, rule optimization, test-case generation, documentation, and production support. Pilot appropriate tools, validate outputs, and incorporate useful solutions into daily work. Success will be measured by improvements in development speed, testing coverage, documentation quality, or operational efficiency while maintaining appropriate human review.