Robotic Process Automation UiPath Developer II; Remote in WA,

Company Overview

Take a leap and join our team! At Gesa, we believe in the power of our people. Coming from all walks of life, our team members’ individual stories and unique experiences are our most valuable asset. It’s how we come together, igniting our collective compassion and commitment to empowering our communities, that makes us succeed. Because we know we go further when we go together.

Here you can join a team that is passionate about serving others, has a desire to do good, and shares a deep love of people. You can engage in meaningful work that impacts your community, challenge yourself and grow in your career, and rest assured that your wellbeing and prosperity are our priority.

The Robotic Process Automation UiPath Developer II position has the ability to work fully remote from Washington, Oregon or Idaho.*

Under the supervision of the PMO Program Manager/Team Leader, the RPA UiPath Developer II is responsible for the design, development, implementation, and documentation of RPA solutions using the UiPath Automation platform. This position works closely with the RPA Champion and Product Owner to implement bots that reduce Team Member workload throughout the Credit Union. Secondarily, this position will work with Business Analysts, Project Managers, and Product Owners to identify opportunities to replace existing bots through the requirements development process for upgrades to existing systems or replacements.

As part of the Process Improvement/Quality Assurance (PIQA) team, this role is expected to contribute to tactical process improvement initiatives that are strategically aligned with the goals of the organization.

• Execute RPA development tasks in coordination with Business Analysts, Product Owners, Subject Matter Experts, and business stakeholders.
• Stay up to date with the latest RPA trends and technologies. Identify opportunities for process improvement and optimization.
• Promote the Quality Assurance process across the company through active participation on teams supporting initiatives for strategic business improvements.
• Advocate for escalation of reported issues.
• Must consistently display and maintain integrity, courtesy, tact, and diplomacy with current and potential members, peers, staff, and vendors.
• Member- and relationship-centered in perspective.
• Build and grow a network of Subject Matter Experts (SMEs) across the organization.
• Collaborate with Quality Assurance team members to improve the Quality Assurance process on a continuous basis.
• Collaborate with multi-disciplinary teams during RPA development, sustainment, and retirement.
• Technical/Professional writing skills essential to document bots, system dependencies, and bugs.
• Adept at managing communications both vertically and horizontally across the organization, as well as with vendors.
• Promote established governance standards for approved process improvements and change control.
• Identify and communicate risks and issues that may require changes to bot or associated systems.
• As part of the PIQA team, communicate governance standards for approved process improvements and change control.
• Proficiency with Microsoft Office 365:
  Word, Excel, Teams, One Note, PowerPoint.
• A capable independent contributor, as well as a team player.
• Multi-task and work separate projects in a fast-paced and dynamic environment under extremely tight timelines (demonstrated time management skills).
• Must demonstrate a tolerance for ambiguity when making decisions and executing work.
• Strong understanding and adherence to industry best practices, compliance standards, and regulations for RPA, data security and privacy.
• Proficiency in analytical thinking and information sourcing.
• Excellent problem-solving skills to address technical challenges and optimize automation solutions.
• Review system documentation to ensure technical accuracy, compliance, and completeness.
• Use methodologies specific to quality review functions in the system life cycle that spell out what to do, and when.
• Utilize stories, system requirements, design specifications, and any other relevant documentation as a basis to plan,…