次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 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で応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。