Implementation Manager OR Senior Implementation Manager

KeyBank•Cleveland, OH

1d•$71,000 - $125,000•Remote

About The Position

We are seeking an Implementation Manager to join KeyBank’s Institutional Bank to drive transformational change with the CWA Replacement, Underwriting Templates (Banking Group Portfolio Management) and/or other technology projects (KeyBank Real Estate Capital). This is a hands-on, product role for someone who can blend product ownership, business analysis, technical acumen, and project management skills with the technical curiosity to dig into systems, data, and tools directly. The right candidate needs to be decisive, organized, and proficient with communication. This person will be able to engage technology leads and engineers early, ask probing questions, and keep both the business and tech teams aligned with clear documentation and knowledge-sharing practices--all while maintaining clear lines of communication with business and technology stakeholders. The role will help drive agile ceremonies, keep the backlog clean, track progress across sprints, and focus the team on the right outcomes. This role sits squarely in the line of business, and success of the position requires demonstration of technical delivery and focus upon meeting business Key Performance Indicators (KPIs) and goals. This role is ideal for someone with 1–5 years of Product Management, BA, or project management experience who wants to build a deeper technical foundation while shaping digital banking products at scale. Having firsthand technical experience (coding, DevOps, SQL, etc.) is a plus.

Requirements

Experience: One plus years in Product Management, Business Analysis, or Project Management (preferably in fintech, banking, or SaaS)
Technical Aptitude: Comfort (or strong willingness to learn) working with data, logs, APIs, and cloud-based environments; solid grasp of how web traffic flows and modern systems interact.
Agile Delivery: Proven experience running agile ceremonies and keeping teams accountable.
Project Management: Organized, methodical, able to create clear plans (and Plan B’s), delegate tasks, and parallelize work streams.
Analytics: Ability to leverage reporting and analytics tools to validate assumptions, measure outcomes, and inform product decisions
Tools: Familiar with Jira and Confluence; disciplined about ticket cleanliness and documentation
Writing Skills: Excellent written communication — able to produce clean requirements, design docs, diagrams, and executive updates
Business & Systems Awareness: Ability to map requirements to the systems and teams involved; not “that’s another team,” but someone who takes ownership across boundaries.
Education: Bachelor’s degree in computer science, Engineering, Business, or related field preferred, but firsthand experience is valued over formal education.

Nice To Haves

Having firsthand technical experience (coding, DevOps, SQL, etc.) is a plus.

Responsibilities

Product & Requirements Management Provide project leadership support for any/all Institutional Bank projects: CWA Replacement, Moody’s, and/or Underwriting Templates
Translate client and business needs into actionable user stories with acceptance criteria.
Ensure requirements are clean: estimated, well-described, assigned, and updated.
Maintain and prioritize product backlogs in collaboration with technology product/platform owners, business stakeholders, and engineering leads.
Map business requirements cleanly to the actual technology product modules and systems involved.
Execution & Agile Leadership Support Business Process Owners and Technology Platform/Product Owners with the work of delivering effective standups, retrospectives, sprint planning, and stakeholder meetings. A strong bias towards value delivery to the enterprise.
Document retrospectives with clear action items (e.g., Start/Stop/Continue, carryover tracking)
Keep stakeholder check-ins scheduled and documented in Confluence.
Recognize and address lagging areas in (business or technology) process (e.g., QA bottlenecks, gaps in communication or tooling) by documenting for improvements in retrospectives.
Technical Fluency & Direct Work Develop and maintain a strong understanding of how technology works (e.g., an understanding of all the technical systems and functions at play when a browser hits a webpage)
Be comfortable working directly with data, logs, APIs, and system outputs.
Use tools like system diagrams, and monitoring dashboards to validate or troubleshoot issues before escalating.
Maintain awareness of enterprise system architecture.
Collaboration & Communication Engage Technology Product Owners/Platform Owners early to flesh out design and implementation details.
Maintain strong documentation and knowledge-sharing practices, including active ticket commenting, UML diagrams, and up-to-date Confluence pages.
Function as the bridge between technical teams and business stakeholders, articulating business problems clearly and avoiding jargon or buzzwords.
Balance business priorities with technical realities — negotiating trade-offs and setting realistic expectations.