Zorky CRMZorky CRM
EN|RU
@termdocs
← All jobs

Cross-Functional Product Lifecycle Process Lead

Seniorremote8,958 USDRemote: United States; UTC-10 to UTC-5, USScore 73/100today
Market insights
📊 Product Management: salaries and demand on the market
Stack
awsazureclouddevsecopsenterprise architectgcpgoogle cloudgoogle cloud platformitilitsmlucidchartsalesforce
Apply
Upload your CV — we will connect you with the employer directly through our pool.
Send your CV →
Description
Position Title: Cross -Functional Product Lifecycle Process Lead – Project Manager Location: Remote (In the U.S) Other Considerations: U.S. Citizen or Permanent Resident (Required) POSITION SUMMARY This role leads and manages functions within the Product Lifecycle, with responsibility for the people, processes, and documentation that keep work moving cleanly from one team to the next. You would be assigned areas directly while also serving as the connection point between functions that too often operate in isolation — Intake and Triage, Discovery, Reuse, and SaaS governance among them. The "Cross-Functional" designation is deliberate: assigned areas may shift over time as program priorities change. The role sits within the Product Lifecycle team and reports to the team lead. It exists because the lifecycle depends on a level of connective work, institutional knowledge, and process discipline that no single existing function owns. Much of that knowledge currently lives with individuals rather than in written procedure, and handoffs between teams generate avoidable rework. You would be accountable for changing that — standing up durable structure, documentation, and quality practices in areas that have historically run on tribal knowledge. Success calls for someone senior enough to manage a technical team, redesign how multiple teams work together, and advise leadership with credibility. The right candidate brings a track record in two things at once: building working relationships across teams and building process and documentation where little exists. Expected outcomes include shorter cycle times, cleaner handoffs,defensible documentation, and institutional knowledge that survives beyond any one person. RESPONSIBILITIES Manage assigned Product Lifecycle area(s) directly — setting priorities, managing performance, developing staff, and establishing clear ownership and accountability Serve as escalation point for complex, high-priority, or high-profile items within managed functions, applying sound technical and analytical judgment Balance competing priorities across assigned areas while holding the line on delivery and quality Act as the connection point across lifecycle functions and their interfaces (e.g., Discovery, Reuse, SaaS governance), building relationships and removing the communication barriers that keep teams siloed Establish shared intake criteria, handoff standards, and communication touchpoints so work passes between teams with full context and minimal rework Facilitate recurring syncs across teams to surface blockers, clarify ownership, and align on prioritization Represent managed functions in modernization and organizational discussions, positioning them as repeatable models other teams can adopt Build and maintain a documentation baseline — SOPs, process maps, handoff criteria, decision logic, and knowledge-base articles — for functions that currently rely on undocumented knowledge Capture historical process context, timelines, and program history so institutional knowledge lives in written procedure rather than with individuals Set documentation standards and a maintenance cadence that keep artifacts current and defensible over time Track and report performance and process-health metrics (e.g., request volume, resolution time, data error rate, audit outcomes) to leadership Analyze request and program trends to recommend process improvements, tooling changes, or new service offerings Advise leadership directly, providing recommendations and guidance grounded in program and lifecycle expertise Provide oversight and advisory support for governance, compliance, and quality within assigned areas, including quality-control review of data, deliverables, and processes Ensure alignment with applicable security frameworks, VA cloud strategy, and enterprise architecture standards, and compliance with applicable federal regulations and VA policies (e.g., FedRAMP, FISMA, ATO processes, VA Handbook 6500) QUALIFICATIONS Must be able to pass a federal background investigation/suitability determination as required for VA contractor personnel Bachelor's degree in Computer Science, Business Management, or a related field, or equivalent experience Minimum 5 years of experience in cloud services, IT service management, or product/program operations Minimum 3–5 years in a leadership, team-lead, or cross-functional program role Demonstrated track record in both (a) building working relationships across teams and (b) building process structure and documentation from the ground up, with measurable gains in efficiency, cycle time, or handoff quality Hands-on experience with SaaS products and PaaS platforms (e.g., AWS, Microsoft Azure, Google Cloud Platform, ServiceNow, Salesforce) Working knowledge of ITSM frameworks (e.g., ITIL) and triage/ticketing systems Experience in federal government environments, preferably with VA or another large federal agency Familiarity with federal cloud security and compliance requirements (FedRAMP, FISMA, ATO processes) Clear written and verbal communication, including the ability to translate technical concepts for non-technical stakeholders Strong analytical and problem-solving skills with a record of practical, compliant solutions Preferred PMP — active certification, demonstrated progress toward it, or equivalent hands-on project/process management experience Additional certifications such as ITIL Foundation, Lean Six Sigma, AWS/Azure/GCP, or CISSP Prior experience within VA OIT or supporting VA cloud initiatives Direct experience with Reuse, SaaS Memo/Attestation, or ISO governance processes Experience with business process management, workflow automation, or process-mapping tools (e.g., Visio, Lucidchart, ServiceNow Workflow), or building knowledge-management/documentation programs WORKING CONDITIONS Standard Business hours are Monday through Friday. Occasional extended or weekend hours may be required based on o
Source: HimalayasView on Himalayas →
Employer contacts (email/phone/telegram) are hidden from the public preview — send your CV, and we will connect you directly.
Urgent question? Message @termdocs