Position Details
Technical Project Manager Ui Path Rpa Apply
Job Title: Technical Project Manager(Ui Path/RPA)
Job Location: Mountain View, CA 94043
Job Type: Contract
Job Location: Mountain View, CA 94043
Job Type: Contract
Introduction
Technical Project Manager that has extensive work experience with the completion of technical artifacts and partnering with Engineering teams to collect recommendations and approvals for the advancement of product and AI projects.
To be successful in this role, the candidate must be self-sufficient, internally driven, views constant change as a challenge and is motivated to overcome blockers. Framework is provided, however no micro-management will occur, therefore candidates need to be independent and enthusiastic about advancing a heavy project load rapidly. Virtual networking, navigating numerous internal resources and efficient project plan building will be the consistent experience and candidates proficient in these areas will be successful.
Our Engineering and Product team members will provide direction of what is desired and how they intend to advance the solution, however the completion of paperwork and collection of approvals will be the primary duty of the Technical Project Manager.
Required Skills
High-Level Design
This is the primary document that will need to be produced as the Technical Project Manager. The Technical Project Manager will be the (D)river within the DACIE (Driver, Approvers, Contributors, Informed and Escalation). Partnering with our Project Requestors, Product Manager, Process Architects and Program Manager on the Problem Statement, Constraints, Proposed Solution and Solution Design will be content that the Technical Project Manager is accountable to produce rapidly for all projects. This will include Architectural Decisions, Capability Architecture, Design Assumptions, Non Functional Requirements/Examples along with Security, SOX Compliance and Infosec Compliance.
Low-Level Design
This is the secondary document that will need to be produced as the Technical Project Manager. Similar to the High-Level Design, the Technical Project Manager will be the (D)river within the DACIE (Driver, Approvers, Contributors, Informed and Escalation). This document starts with a concise Executive Summary, advances to a Detailed Component Design, Decisions & Justifications, Operational & Quality Aspects and concludes with Risks, Open Questions & Future Work. The creation, collection and explanation of this content will be the responsibility of the Technical Project Manager.
Product Requirements Document
- Focusing on the "Why" and not just the "What", being concise and collaborating early and often are the key fundamentals to a quality Product Requirements Document. There are 12 key areas that are covered and the best candidate will not only be familiar with all of these areas, but have recent past experience that verifies the ability to produce this content.
- Introduction & Vision - Big picture, elevator pitch that is easily understood by technical and functional team members
- Problem Statement - Pain points, users problem, "Jobs to be Done" framework
- Goals & Objectives - What will this accomplish, clear/measureable goals, why is this worth the time and resources invested
- Success Metrics - Not only what will be measured, but the creation of the dashboard/report views
- Personas & Scenarios - Who are we building this for, user-centric decisions, tell the story of what "before" is and what "after" will be and why this matters to each persona
- Process Flows - Current 'AS IS' and future 'TO BE' workflows, must be end-to-end and in most cases is multi-org impacting
- Requirements & User Stories - Features, functions and user-facing behaviors
- Design & User Experience
- Dependencies & Risks
- Out of Scope, Future Work & Deferrals
- Launch Plan / Project Plan
- Q&A / Open Questions
