Microsoft Orchestrator

Description

MUST HAVE: Microsoft Orchestrator 2016
4+ years of expertise in using Microsoft Orchestrator 2016
Excellent SQL skills.
Ability to debug/troubleshoot large sets of data or format related issues.
Experience creating runbooks, splitting runbooks into child runbooks, create a parent runbook encapsulating all the child runbooks
Experience in scheduling runbooks specifically around:
When and how often is the runbook going to run?
What steps make up the workflow?
What activities reflect the steps in the workflow?
What type of data is required to begin the workflow?
What data are generated from each activity?
What results are produced at the end of the workflow?
How are the runbook results reported?
Be able to distinguish between platform-code and domain-code (see next two points for more details)
Platform Code: common code shared by most activities and is used to run common tasks performed by Orchestrator activities. Platform code generates Common Published Data
Domain Code: Runs various tasks that are specific for the actions for each activity, which are typically not associated with the Orchestrator platform itself.
Understanding of how much time runbooks spend running domain code compared to running platform code
Estimate platform code costs and use the data as a reference in considering where to make improvements in runbook performance
Experience enabling logging for runbooks and using best practices in handling the size of data collected in the database
Experience with Runbook designer and how it communicates to Orchestrator database
Assess logging of Activity-specific Published Data in production environments (for debugging purposes)
Good communication and listening skills, willingness to learn
Good understanding of Project/Product management, SDLC and other methodologies
Good Documentation skills