Every job listed here is analyzed by our AI to identify worldwide hiring — not just “remote in the US.” Our classification is actively being improved, some results may be inaccurate.
Worldwide Remote
Jobs reviewed for worldwide hiring.
Real Hiring Data
Country flags show the countries where each company has team members
Updated Hourly
Fresh jobs synced from thousands of career pages
Location Remote – Europe preferred. We are especially interested in candidates based in Poland, Romania, Bulgaria, Serbia, or Ukraine. Role Type Full-time preferred. Contract may be considered for the right candidate. About the Role We are hiring a Technical Delivery Manager / Technical Product Manager to bring structure, accountability, and visibility to our software development process. This role sits between product, delivery, QA, release management, and stakeholder communication. You do not need to be a hands-on developer, but you must be technically literate, comfortable working with developers, and able to manage software delivery in a fast-moving environment. The main purpose of this role is to ensure the team knows what is being built, who owns each task, what is ready for testing, what is ready for reease, and what has been communicated to the business before changes reach production. This is not a passive coordination role. We need someone who can enforce process, hold people accountable, improve release discipline, and protect production stability. Key Responsibilities Project and Task Management • Maintain a centralised system for all development work. • Capture feature requests, bug reports, integration work, operational issues, and BAU development tasks. • Turn Slack discussions, stakeholder requests, and development conversations into clear, trackable tasks. • Assign ownership, priorities, deadlines, and delivery expectations. • Track progress across developers, testers, and external contributors. • Coordinate standups and follow up on blockers. • Ensure leadership can see what is in progress, delayed, blocked, ready for testing, and ready for release. • Reduce reliance on senior leadership to manually manage developer workloads. Delivery Coordination • Maintain a clear product and development backlog. • Support sprint planning, delivery planning, and weekly task planning. • Help prioritise work based on business impact, operational risk, customer/patient impact, compliance risk, and development capacity. • Clarify requirements and acceptance criteria before work begins. • Track feature commitments and ensure timelines are realistic. • Coordinate integrations, technical fixes, platform improvements, and ongoing product enhancements. • Ensure development work aligns with business priorities and roadmap direction. Release Management and Deployment Governance • Plan release schedules in advance. • Coordinate deployment windows with business operations. • Avoid releases during sensitive, active, or high-risk operational periods. • Manage deployment approvals before production release. • Ensure required checks are completed before a release proceeds. • Maintain a release calendar, deployment checklist, and approval record. • Coordinate deployment activities across development, QA, operations, and stakeholders. • Confirm releases have passed agreed release gates. • Prevent unplanned, undocumented, or poorly communicated production changes. • Ensure rollback plans are understood before major releases. You do not need to design deployment architecture, but you must understand common deployment and release strategies, including staging environments, production validation, rollback planning, release gates, feature flags, canary releases, blue-green deployments, CI/CD workflows, smoke testing, and regression testing. QA and Testing Oversight • Define the manual QA scope for each release. • Ensure happy-path user journeys are tested. • Include selected negative test cases where appropriate. • Avoid unnecessary exhaustive manual testing of every possible scenario. • Coordinate smoke testing before production deployment. • Coordinate regression testing for critical workflows. • Ensure critical user journeys and core transactions are covered. • Support automated end-to-end regression testing for common user paths. • Document test results and communicate release readiness. • Escalate or block releases where testing has not been completed to the agreed standard. BAU Testing • Establish a recurring BAU testing schedule for critical platform areas. • Identify critical modules, workflows, and user journeys requiring regular checks. • Coordinate testing across key business functions. • Document BAU test results and report issues to stakeholders. • Track fixes through to completion. • Use recurring testing to identify issues before they become production incidents. Release Notes and Stakeholder Communication • Publish release notes for every production deployment. • Notify relevant stakeholders before and after production changes. • Explain what has changed, what has been fixed, and what may affect users. • Communicate deployment timing, release scope, risks, and known issues. • Translate technical updates into plain English for non-technical stakeholders. • Provide visibility over roadmap direction, delivery progress, risks, blockers, and release status. • Create a reliable communication loop between development, operations, support, and leadership. Tooling and Workflow Management • Manage task boards, issue lists, release boards, sprint boards, or roadmap views. • Ensure tasks are clearly written, assigned, prioritised, and updated. • Create repeatable workflows for bugs, feature requests, releases, QA checks, and production incidents. • Use automation where appropriate to reduce manual task tracking. • Connect Slack, project management tools, and development workflows. • Maintain clean reporting views for leadership and stakeholders. Experience with Linear, Jira, ClickUp, Asana, Trello, Notion, GitHub Projects, Slack, or similar tools is highly relevant. Linear experience is highly regarded, especially where it is used with Slack to create issues, track development work, manage releases, and improve visibility across technical and business teams. Required Experience • Experience managing software development tasks across technical teams. • Experience coordinating releases, deployments, or production changes. • Strong understanding of QA processes, smoke testing, regression testing, and release gates. • Experience working with developers, testers, business stakeholders, and leadership. • Understanding of agile delivery, sprint planning, backlog management, and task tracking. • Experience using project management tools such as Linear, Jira, ClickUp, Asana, Trello, Notion, GitHub Projects, or similar. • Ability to write clear release notes, project updates, and stakeholder communications. • Strong organisational skills and attention to detail. • Ability to manage competing priorities in a fast-moving environment. • Confidence enforcing process and accountability across technical teams. • Strong written and spoken English. Highly Regarded Experience • Healthtech, telehealth, regulated industry, or patient-facing platform experience. • Linear experience for technical delivery, issue tracking, release planning, or Slack-based task creation. • Automated end-to-end testing coordination. • CI/CD workflow experience. • Structured release management or deployment governance experience. • Experience managing integrations between multiple systems. • Experience working with offshore or distributed development teams. • Experience building release management SOPs from scratch. • Experience improving production stability in a growing software business. Key Skills • Highly organised and process-driven. • Technically literate without needing to be a developer. • Clear, direct, and confident communicator. • Comfortable holding people accountable. • Strong at prioritisation and trade-off management. • Calm under pressure. • Detail-oriented with strong follow-through. • Able to translate technical issues into business language. • Strong at identifying operational risk before it becomes a production problem. • Confident enough to escalate or stop a release when process, testing, or communication standards have not been met. First 90 Days Success in the first 90 days will include: • A centralised task management process in place. • Active development tasks captured, prioritised, assigned, and tracked. • A release calendar and release approval process established. • Release notes published for production deployments. • Smoke testing and regression testing processes documented and followed. • BAU testing scheduled for critical workflows. • Leadership receiving clear visibility over progress, risks, blockers, and upcoming releases. Success Measures • Fewer production issues caused by untested or poorly communicated releases. • Clear ownership of development tasks. • Better visibility over priorities, workload, progress, and blockers. • Release notes published for production deployments. • Smoke testing and regression testing completed before releases. • BAU testing completed and reported regularly. • Reduced reliance on leadership to manually coordinate developers. • Better stakeholder awareness of production changes. • Cleaner task tracking and fewer undocumented requests sitting in Slack or verbal discussions. How to Apply Please apply with your resume and a short note outlining your experience managing technical delivery, release processes, QA coordination, and development team workflows. Candidates with experience in healthtech, telehealth, regulated environments, Linear, Slack-based workflows, release governance, or QA process improvement are strongly encouraged to apply.