寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 12,169

← 返回搜索结果

Technical Delivery Manager (PL7038)

Paralucent

远程工作

地点
Remote (India)
工作安排
Contractor
发布日期
2026年10月10日

申请前,请在雇主网站确认职位仍在招聘,并检查完整要求和条件。

职位描述

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

Technical Delivery Manager Fully Remote within India Long Term Contract Shift Timings: 2:00 pm to 11:00 pm IST Experienced Technical Delivery Manager - lead the end-to-end delivery of complex technology initiatives. The Technical Delivery Manager will be responsible for translating business objectives into executable technology delivery plans, establishing delivery governance, managing dependencies and risks, and ensuring projects and programs are delivered on time, within scope, within budget, and to the required quality standards. This role requires a strong combination of technical understanding, program/project management expertise, stakeholder leadership, and execution discipline. The candidate must be comfortable operating in a highly technical environment and working with engineering teams. A strong technical person with deep understanding of application architecture. Key Responsibilities End-to-End Delivery Management Own delivery of technology projects and programs from discovery and initiation through implementation, release, stabilization, and closure. Translate business requirements and strategic objectives into actionable delivery plans. Establish project objectives, milestones, deliverables, timelines, resources, and success criteria. Develop and maintain integrated delivery plans across multiple technical and business workstreams. Coordinate delivery across engineering, product, architecture, DevOps, infrastructure, data, security, QA, TNI, operations, and third-party teams. Ensure delivery remains aligned with business priorities and expected outcomes. Track progress against milestones, critical paths, dependencies, and key deliverables. Drive delivery decisions and remove blockers that could impact timelines or outcomes. 2. Technical Program Leadership Work closely with engineering and architecture leadership to understand technical scope, constraints, trade-offs, and delivery complexity. Translate technical concepts into clear business-level communication for executives and non-technical stakeholders. Understand system architecture, APIs, integrations, cloud infrastructure, data flows, security requirements, environments, CI/CD, testing, and production operations to manage technical delivery effectively. · Provide Architecture alignment and solution guidance. Challenge estimates, assumptions, dependencies, and technical delivery plans when appropriate. Facilitate technical decision-making. Identify technical risks early and ensure mitigation strategies are developed and executed. Coordinate cross-system and cross-team integration activities. Ensure non-functional requirements such as performance, scalability, availability, security, resilience, observability, and compliance are incorporated into delivery plans. 3. Planning and Execution Establish delivery methodology appropriate to the initiative Build realistic delivery schedules based on team capacity, technical complexity, dependencies, Manage sprint, release, milestone, and program-level planning. Coordinate planning across multiple engineering teams and vendors. Monitor delivery velocity, throughput, capacity, and milestone performance. Identify schedule slippage and implement recovery plans. Ensure delivery teams have clear priorities and understand expected outcomes. Maintain accurate delivery documentation and status reporting. 4. Risk, Issue, and Dependency Management Own the program-level risk, issue, assumption, action, and dependency management process. Identify delivery risks proactively rather than waiting for issues to materialize. Assess probability, impact, severity, and business consequences of risks. Establish mitigation, contingency, and recovery plans. Escalate material risks and issues at the appropriate time with clear recommendations. Manage cross-team dependencies and ensure dependency owners understand required dates and commitments. Track technical debt and delivery constraints that may affect future releases. 5. Stakeholder Management Serve as the primary delivery point of contact for key technology initiatives. Manage expectations across technical and non-technical audiences. Facilitate executive-level discussions and provide concise, fact-based updates. Communicate delivery status, risks, decisions, dependencies, and required actions clearly. Create transparency around delivery performance and emerging challenges. Resolve conflicts between teams and stakeholders constructively. Establish clear governance and escalation paths. 6. TDM as Scrum Master and Technical Delivery Facilitator The Technical Delivery Manager will apply Scrum Master practices while maintaining responsibility for effective technical delivery, cross-team coordination, and alignment with the approved solution architecture. Partner with the Product Owner to translate the product vision, business objectives, and technical architecture into prioritized epics, features, user stories, technical enablers, and clear acceptance criteria. Facilitate Product Backlog refinement and ensure backlog items are clear, appropriately prioritized, technically feasible, and ready for implementation. Facilitate Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and other agile delivery forums as required. Guide developers and delivery teams in understanding architectural intent, technical dependencies, non-functional requirements, security requirements, implementation priorities, and expected delivery outcomes. Identify, track, remove, or escalate technical and organizational impediments that affect delivery. Coordinate with the Product Owner, developers, architecture, security, TNI, DevOps, QA, infrastructure, and other stakeholders to resolve dependencies and delivery risks. Use sprint metrics, delivery outcomes, stakeholder feedback, and empirical evidence to improve backlog planning and delivery predictability. 7. Governance and Reporting Establish appropriate delivery governance based on project size, complexity, risk, and organizational requirements. Lead project/program steering committees wherever required. Maintain governance documentation, decision logs, action registers, and delivery artifacts. Ensure appropriate approvals and stage gates are completed. Maintain delivery documentation where required. 8 . Resource Management Support resource forecasting and capacity planning. Identify resource constraints and negotiate appropriate allocation. 9. Release and Production Readiness Own program-level release planning and coordination, including Program Increment Planning where a scaled Agile framework is used. Establish release readiness criteria and checkpoints. Coordinate technical, business, security, compliance, operational, and support readiness. Ensure testing, defect management, deployment planning, rollback strategies, monitoring, and support processes are established. Coordinate go-live planning and execution. Manage hypercare and post-production stabilization. Conduct post-implementation reviews and ensure lessons learned are incorporated into future delivery. 10. Quality Management Ensure quality is embedded throughout the delivery lifecycle. Partner with QA and engineering teams to establish appropriate testing strategies. Track defects, technical issues, performance concerns, and production incidents related to the program. Ensure quality gates are established before major releases. Monitor quality trends and recurring issues. Drive root-cause analysis where delivery or production problems occur. 11. Continuous Improvement Identify opportunities to improve delivery processes, engineering collaboration, governance, and organizational efficiency. Establish delivery standards, templates, playbooks, and best practices. Use delivery metrics and retrospective findings to drive measurable improvement. Promote a culture of accountability, transparency, ownership, and continuous improvement. Requirements 10+ years of experience in technical delivery, program management, or project leadership within technology consulting, professional services, or a complex enterprise environment. Strong technical understanding of solution architecture, enterprise applications, APIs, integrations, cloud platforms, data flows, security, environments, CI/CD, testing, and production operations. A strong technical person with deep understanding of application architecture. Proven experience leading the end-to-end delivery of complex technology initiatives, from discovery and planning through implementation, release, stabilization, and closure. Demonstrated ability to translate business objectives and solution architecture into delivery plans, epics, features, user stories, technical enablers, acceptance criteria, and implementation activities. Proven ability to guide engineering teams, facilitate technical decision-making, challenge estimates and assumptions, and ensure delivery remains aligned with the approved architecture and technical standards. Experience managing multiple technical and business workstreams involving engineering, product, architecture, security, infrastructure, DevOps, data, QA, operations, and third-party teams. Strong experience managing risks, issues, assumptions, actions, dependencies, technical debt, delivery constraints, and escalation paths. Demonstrated experience with Agile and Scrum delivery, including backlog refinement, Sprint Planning, Daily Scrum, Sprint Reviews, Sprint Retrospectives, release planning, and continuous improvement. Experience coordinating release readiness, testing, defect management, deployment planning, rollback planning, operational readiness, go-live, hypercare, and production stabilization. Strong understanding of the software development lifecycle, application lifecycle management, production support, and incident, problem, and change-management processes. Experience with delivery and service-management tools such as Azure DevOps and ServiceNow, or equivalent platforms. Nice to Have Project or program management certification, such as PMP, PRINCE2, or an equivalent credential. Scrum Master certification, such as PSM, CSM, or an equivalent Agile certification / Agile delivery certification or experience with scaled Agile delivery frameworks (SAFe). Experience with one or more major cloud platforms, including Microsoft Azure, AWS, or Google Cloud Platform. Familiarity with modern solution patterns, including microservices, API-led integration, event-driven architecture, and cloud-native applications. Experience with DevOps, CI/CD, infrastructure automation, observability, or Site Reliability Engineering practices. Familiarity with ITIL and IT service-management frameworks, including incident, problem, change, request, and release-management processes. Originally posted on Himalayas

查找职位、比较要求,再准备申请

从你希望从事的职位或运用的技能开始搜索。调整地点和职业筛选,打开职位比较工作职责。如果没有结果,可以使用更短的关键词,或逐一移除筛选条件。

区分必备要求和优先条件,检查已列出的工作安排、薪资和地点。远程职位也可能要求特定居住国家、工作许可或工作时间重合。请向雇主确认职位信息和完整条件。

选择能够回应职位要求的真实经历,说明你的贡献,只使用能够证实的数字。遵循雇主的申请说明,并在提交前检查联系方式、文档内容和 PDF。

提交申请前的检查清单

求职常见问题

为什么有些职位使用英文?

职位名称和描述由招聘企业撰写。为避免改变招聘要求或工作条件,我们保留原文。操作界面和本指南使用简体中文。如果中文搜索没有结果,可以尝试使用职位发布语言中的名称或技能,例如“software engineer”。搜索词不会自动翻译,界面语言也不代表企业要求的申请语言。

远程职位是否允许从任何国家工作?

不一定。企业可能对居住国家、工作许可或工作时段有要求。请查看原始招聘页面中的具体条件。如果未说明,应先向企业确认,再判断能否从你所在的地区工作。“远程”标签本身并不代表没有地点限制。

搜索没有结果时应该怎么办?

尝试更通用的职位名称或单个技能,并逐一移除筛选条件。不同企业可能用不同名称描述相似工作。如果某个职位已经消失,请在企业招聘页面搜索其职位编号。扩大搜索范围不会让已经关闭的职位重新开放。

申请会通过 ResumizeAI 直接提交吗?

申请按钮会打开外部网站。请按照企业或招聘服务的说明,在该网站完成并确认提交。在 ResumizeAI 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。