Technical Delivery Manager (Client-Facing TPM)
# Technical Delivery Manager (Client-Facing TPM) **Cappital** · Irvine, CA 92618 · `On-site` 🕒 **Статус:** *Опубликовано: 8 дней назад* · *Источник: Indeed* --- ### About the Role Location: Remote, United States Travel: Approximately one to three trips per year to Irvine, California, or a client location Employment type: Full-time Compensation: $100,000–$150,000 base salary, depending on experience and location Travel: Occasional travel to Irvine, California, and client locations About Cappital Cappital is a product strategy and software development firm. We help organizations define, design, build, and continuously improve custom digital products. We are a small, highly collaborative U.S.-based team that works closely with a long-standing engineering organization in India. People here work across functions, stay close to the work, and take personal responsibility for helping clients succeed. About the role We are hiring a hands-on Technical Delivery Manager to support one of our largest and most strategically important client relationships. You will serve as a stateside bridge among the client’s product and engineering stakeholders, other technology vendors, and Cappital’s engineering team in India. You will frequently participate in client meetings with engineers when no Cappital engineer is present. You must be able to understand the discussion, ask useful questions, identify dependencies and unresolved decisions, represent established engineering positions accurately, and keep work moving without making unsupported technical commitments. This is a client-facing technical program and delivery role. It is not a software engineering or architecture position, but it is also not a nontechnical project-management role. What this role is—and is not - It is a hands-on individual-contributor role. You will personally lead meetings, clarify requirements, document decisions, maintain delivery details, and follow up with stakeholders. - It is not a portfolio-governance, executive-oversight, or large-team management position. - You will not independently set software architecture or override the engineers responsible for technical decisions. - You will be expected to understand technical issues well enough to improve the discussion, recognize missing information, and accurately communicate what engineering has decided. - Success depends on creating clarity in an environment where priorities, processes, and stakeholder expectations may change frequently. What you will do Lead client-facing technical delivery - Serve as a trusted and responsive technical-delivery contact during U.S. business hours. - Facilitate discussions involving requirements, integrations, implementation status, technical constraints, risks, incidents, and delivery tradeoffs. - Build productive relationships with client engineers, product stakeholders, other vendors, and Cappital team members. - Communicate uncertainty candidly without losing credibility, creating unnecessary alarm, or implying commitments that engineering has not made. - Identify emerging concerns and expectation gaps before they become escalations. Translate between stakeholders and engineering - Translate client objectives, questions, and concerns into clear technical and delivery inputs. - Translate engineering constraints, dependencies, risks, and recommendations into language appropriate for the audience. - Represent established engineering decisions accurately while recognizing when an engineer or specialist needs to participate directly. - Ask technically informed questions that expose assumptions, missing requirements, failure modes, and decision boundaries. - Adapt your communication for engineers, product leaders, executives, and external partners. Create and maintain delivery clarity - Maintain a dependable source of truth across roadmap documents, technical decisions, tickets, milestones, and client commitments. - Identify contradictions among product goals, architecture decisions, delivery plans, and implementation status; bring the right people together to resolve them. - Proactively trace the likely technical and operational implications of new requests. Understand the platform well enough to recognize when a change to one feature, integration, data flow, analytics implementation, or workflow may affect another system or team; involve the appropriate stakeholders before incomplete or conflicting direction reaches engineering. - Distinguish among proposed, decided, implemented, tested, approved, released, and operationally ready. - Turn ambiguous requests into sufficiently defined problems, requirements, acceptance criteria, owners, dependencies, and next actions. - Maintain clear records of decisions, assumptions, risks, unresolved questions, and follow-up commitments. - Keep handoffs moving between U.S. stakeholders and the India engineering team with minimal avoidable delay. Support reliable delivery and handoffs - Maintain visibility into milestones, risks, dependencies, approvals, and delivery health. - Coordinate handoffs involving code, CMS content, assets, configuration, analytics, environments, testing evidence, and release requirements. - Help distinguish defects, requirements gaps, scope changes, technical debt, infrastructure issues, and unvalidated assumptions. - Coordinate technical and delivery escalations across client, engineering, product, vendors, and Cappital leadership. - Protect engineering velocity while helping stakeholders make timely, informed decisions. - Improve lightweight working practices when useful without forcing the environment to conform to a preferred methodology. The technical environment Current work involves a modern web platform with cloud hosting, content management, databases, APIs and third-party integrations, preview and production environments, Git-based delivery, CI/CD, feature flags and experimentation, analytics, caching and rendering behavior, access controls, and AI-assisted development workflows. The exact tools may change. Experience with every product in our stack is not required. You should, however, be comfortable learning and discussing comparable concepts such as modern web applications, APIs and data flows, CMS platforms, cloud infrastructure, environments and deployments, observability, release processes, experimentation, security, rollback, and production readiness. What we are looking for - At least five years of recent, hands-on experience delivering complex software products, platforms, integrations, or enterprise applications in a technical program management, technical delivery, implementation, solutions, or comparable role. - Experience serving as an accountable delivery contact for an external client, consulting customer, or similarly demanding stakeholder group. - Demonstrated ability to explain a real technical system coherently, including its major components, dependencies, data movement, failure points, and relevant tradeoffs. - Experience working closely enough with engineers to understand technical concerns while respecting the boundaries of engineering authority. - Ability to reason across an interconnected technical system, identify likely downstream impacts and cross-team dependencies, and know which assumptions require validation—without overstepping into architecture decisions. - Strong meeting leadership, written communication, requirements clarification, decision documentation, and follow-through. - Experience coordinating distributed or offshore engineering teams across significant time-zone differences. - Sound judgment when information is incomplete and stakeholders have competing priorities. - Ability to remain calm, curious, humble, and precise under pressure. - Comfort working as a hands-on individual contributor in a small organization without layers of project-management or business-analysis support. - Practical curiosity about AI-assisted work and an ability to evaluate outputs, limitations, risks, and appropriate human review. Especially relevant backgrounds - Technical program or delivery manager with recent external-client responsibility and strong software-development fluency. - Software engineer who moved into technical delivery, implementation, consulting, or client leadership and still enjoys hands-on coordination. - Solutions engineer or implementation architect whose responsibilities extended beyond presales into delivery and stakeholder ownership. - Technical consultant or application leader who personally coordinated complex integrations, releases, and distributed engineering teams. - Delivery leader from a digital product agency, technology consultancy, or enterprise-software implementation organization. Working style that succeeds here - You listen carefully and get to the point. - You separate facts, assumptions, decisions, and unresolved questions. - You can disagree or surface risk without becoming combative or dramatic. - You are comfortable saying, “I need to confirm that with engineering,” and then reliably closing the loop. - You notice details, prepare for meetings, and follow through without repeated reminders. - You use enough process to create clarity but do not add ceremony for its own sake. - You adapt when the client changes priorities or working practices rather than insisting that everyone adopt your preferred system. - You care about both the client’s outcome and the sustainability of the engineering team. What success looks like During the first 30 days - Learn the client environment, current platform, active work, major stakeholders, and established decision boundaries. - Join the relevant client and engineering meetings, ask strong questions, and begin maintaining clear follow-up and decision records. - Accurately route or respond to client requests while being transparent about what still requires engineering input. - Establish a dependable communication rhythm with Cappital’s engineering lead and CTO. Within 60–90 days - Independently facilitate routine client discussions involving technical delivery. - Recognize contradictions, missing decisions, and emerging risks early enough to act. - Help technical questions and delivery decisions move efficiently across teams and time zones. - Improve the clarity of requirements, ownership, acceptance criteria, and commitments. - Reduce the routine coordination and escalation burden on senior Cappital leaders without reducing technical accuracy. Compensation and benefits The anticipated base salary range is $100,000–$150,000, depending on relevant experience, technical background, geographic location, and demonstrated client-delivery capability. The position also includes Cappital’s standard employee benefits. Working environment This is a remote position open to candidates authorized to work in the United States without employer sponsorship now or in the future. Occasional travel—generally one to three trips per year—may be required for client meetings, team planning, or visits to our Irvine, California, office. Our client environment Our clients include commercial businesses, nonprofit organizations, faith-based organizations, and organizations working in political media. Their missions, viewpoints, cultures, and meeting practices may differ from your own. Employees are not required to share a client’s beliefs, make statements of faith, lead prayer, or participate in religious observances. This role does require respectful and professional service to every client and colleague. Equal opportunity Pay: $100,000.00 - $150,000.00 per year Benefits: - Dental insurance - Health insurance - Life insurance - Vision insurance Experience: - software engineering: 4 years (Preferred) - technical delivery: 4 years (Preferred) - solutions engineering: 4 years (Preferred) - technical program management: 4 years (Preferred) Work Location: Hybrid remote in Irvine, CA 92618
Наблюдалась 2026-10-15, впервые 2026-10-06, источник — Indeed.