Your job is more than a job • Analysts are limited to 10 hours of operational meetings each week. Should their meeting time exceed this limit, they will coordinate with their lead or manager to adjust their schedules or have the lead attend additional meetings on their behalf. This rule does not include meetings related to tickets. • Document notes/minutes from calls in OneNote/related SNOW ticket/SLG and share summary from meetings with team at EOD/internal calls. • Attend all mandatory meetings, communicating and coordinating with team Lead/Manager if unable to attend. Mandatory meetings include but are not limited to: Service Now Ticket Review calls with end users; department meetings; application EOD calls; internal pod/work sessions. • Attend all assigned integrated team calls and update team on regular EOD calls and/or Pod calls. • All meeting invites and operational emails must be copied to the lead. Calendars can be shared "with Edit" if preferred. • Time for meetings attended will be tracked correctly in SNOW. In preparation for planned outages, identify appropriate back up for scheduled calls. • For build work, documentation should include the SNOW ticket/project number, description of request, summary of discovery, peer reviewer's name, Content Management Ticket number, and the end-user who validated the build, all of which are prerequisites for migrating the build to Epic PRD. Meetings related to operations that contribute to ticket or project work should also be documented. • Positive and Negative Test plan should be documented with outcomes in OneNote. • Summary of efforts logged in OneNote should be added to SNOW ticket/project as a Work Note. (Copy/Paste from OneNote is acceptable) • Tickets/Project will be updated weekly in Service Now with current priority placed at the beginning of the Short Description; a summary of ticket's current standings with next steps as a Work Note; and appropriate ticket status. • Weekly update to be shared with end user via weekly application ticket review call and/or SNOW/email notification. • Escalate high revenue/high volume or end user satisfaction concerns to lead/manager. • Maintain related SLGs • Time worked and related meetings will be tracked in SNOW in real time. • Copy lead and manager on correspondence when needed, i.e. problems, delays in response, delays in information being received, lead/manager request, correspondence prior to upcoming outage. • Collaborate with additional application teams as needed. • Creates test plans to support thorough application and integrated testing scenarios. • Completes testing and validates change logs. • Submit system build for peer review prior to migration to PRD. • Resolves post installation technical problems in a timely manner. · Maintains appropriate certifications. · Analysts are expected to dedicate 2 hours per week for working session(1 hour) and daily review during downtime(total time of 1 hour) to IT application responsible workflows in Epic. May include but is not limited to the following: • Watch List and Project Team WQs. Should Watch List or Project Team WQ totals require more attention, manager/lead may increase required number of hours. · Participate in division/department meetings and attend all in person/onsite meetings/days. · Analyst will attend calls with the goal to provide great customer service and to represent Information Technology in a respectful and professional manner. · Seek and accept feedback from Senior Analysts, Functional Architect, Lead, and Manager on meeting facilitation and participation. · Attend meetings with application lead weekly, transitioning to bi-weekly and then monthly meetings as the analysts' proficiency improves. These meetings aim to assist with time management, provide guidance, support growth, and offer resources, etc. · Attend meetings with manager quarterly. These meetings are in place to support the analyst's overall development and alignment on goals. Manager will also share and receive feedback and highlight successes. · Participate in onboarding and knowledge sharing opportunities (transition and pod meetings). · Alerts senior staff members of any outages, problems, or delays. · Utilize Epic sponsored Webinars as well as LCMC's Learning Center content for continued learning opportunities. • Analysts will become an expert in application fundamentals. They will be assigned a smaller number of complex tickets compared to senior analysts or FAs. The work of an Application Analyst should challenge them to develop skills; consistent organization/communication practices; and a strong foundation in the assigned application. • The team leads are tasked with ensuring the quality of build work and helping the team improve efficiency over time. They will distribute the workload evenly among analysts, taking into account the complexity of tickets. • Analyst will provide system build solutions; workflow design; and great customer service while working to cultivate consistent practices that ultimately contribute to their development. • Other duties as needed
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
Job Type
Full-time
Career Level
Entry Level
Education Level
No Education Listed