Decision Rules Engineering / Low-Code/No-Code Developer

Role: Decision Rules Engineering / Low Code Developer
Location: Remote
Duration: 6 month contract

Pre-screening Question s:

1. Can you walk me through a project where you used the Decisions platform? What was your role and what kind of rules did you author?
2. How do you typically approach building a new rule in Decisions from scratch?
3. Have you worked with Decisions rule engine to implement conditional logic based on user input (e.g., branching workflows)?
4. Have you used any scripting within Decisions? If so, what for, and how comfortable are you with it?

Need:

• Previously used two custom apps to do various business processes - recently switched to Decisions
• Decisions = low code Saas solution - rule engine platform
• Some developers have been the ones working on it so far - but this is not a highly technical role
• Want to get a low code engineer/analyst that has experience with Decisions to help them set this up and then coach the Clinical Rules Team on the tool to take over

Decisions:

• Elevated new rules engine - setting rules based on client standards
• Working with Decisions now to fully customize to their needs
• If any, will be very limited scripting to do small changes to the tool
• Bulk of work is authoring new rules and executing it in business operations
• Ex: Based on input - can they auto approve an authorization or needs to be routed to a specific team
• Some Q&A: Are you a smoker? Yes... How much?
• Workflow:
• Partner with Product to gather the business requirements
• Author rules
• Test
• Publish and Promote
• Any complex work, the development team will help on
• RVO still working through some of the data connections, storage, and APIs; again complex work will be done by devs - just good to know it is not 100% solidified

Must Haves:

• Decisions experience- have to have previous experience!
• Ability to coach/train team on tool