Interim CTO vs Deputy CTO: Authority and When to Hire

• Start with the gap, not the replacement title
• The practical distinction between interim and deputy
• When an interim CTO is the better fit
• When a deputy CTO is the better fit
• Worked example: a CTO leaves before a major release
• Define authority before the first difficult decision
• Interview for the actual transition or delegation
• Handle the internal communication carefully
• Copyable mandate for either appointment
• Prepare a handover that another leader can use

An interim CTO holds a technology leadership mandate for a temporary period. A deputy CTO supports the CTO through a defined delegation of responsibility and may cover particular decisions or functions. These describe different aspects of a role: interim concerns tenure, while deputy concerns the relationship to another leader. A deputy can be appointed acting or interim CTO, but that authority should be made explicit.

Use this comparison when a CTO leaves, needs support or cannot cover the company's expanding responsibilities. It includes a decision table, a worked transition scenario, candidate questions and a copyable mandate. The interim CTO guide covers the temporary engagement in more depth, while the CTO role guide describes the broader leadership responsibilities.

Start with the gap, not the replacement title

A departure creates several possible gaps. The company may lose executive decision authority, knowledge of a critical system, management capacity or trusted relationships with investors and customers. Those are related problems, but one appointment does not necessarily solve all of them. Write down what has actually become unowned and what the existing team can continue to handle.

An interim CTO can provide a named executive owner while the company recruits, reorganizes or completes a transition. A deputy may be appropriate when the CTO remains in place but needs another senior leader to own a defined part of the work. If the real problem is daily engineering management, a head of engineering or engineering manager may be a more precise answer.

Avoid using a senior title as compensation for an unclear mandate. A respected architect who becomes deputy CTO still needs a clear account of management responsibilities and delegated decisions. An external interim executive still needs access, internal support and a realistic remit. The title should summarize an agreed arrangement rather than carry expectations nobody has written down.

Discuss the situation with the people already leading delivery. A rushed appointment can unintentionally remove authority from existing managers or create a second route for every decision. Preserve working responsibilities where possible, identify the gaps that need attention and explain how the new arrangement will change escalation. Continuity includes the team's ability to understand who can decide what.

The practical distinction between interim and deputy

The comparison below describes common uses of the terms. It is not a legal definition, a universal reporting structure or a promise about working hours. The company's appointment, employment or engagement documents establish the actual authority and conditions. Review those documents with the appropriate internal owners for the organization and jurisdiction involved.

Question	Interim CTO	Deputy CTO
What does the title emphasize?	A temporary CTO mandate	A supporting or delegated relationship to the CTO
Is another CTO necessarily in post?	Not necessarily; often fills a leadership gap	Usually works within an arrangement involving a CTO
How broad is the responsibility?	Whatever CTO scope is explicitly assigned	Defined functions, decisions or coverage delegated to the deputy
Is the role automatically full time?	No; availability must match the mandate	No; working pattern depends on the appointment
Does the title establish signing authority?	No; reserved and delegated matters need documentation	No; deputy status alone is insufficient
What ends or changes the arrangement?	An agreed transition, review or completion condition	Changes in scope, organization design or a new appointment

A company can have an interim CTO and a deputy at the same time. For example, the interim executive may own the leadership transition while a deputy continues to manage architecture across product groups. That can work when both people understand their responsibilities. It becomes confusing when each assumes they have the final say over the same investment or personnel decision.

An internal deputy may be well placed to take an acting appointment because they already know the people and systems. That familiarity is an advantage to assess, not proof that every broader responsibility is covered. The company should review the additional executive work, the support available and whether the individual wants the appointment before treating promotion as an automatic response.

When an interim CTO is the better fit

Consider an interim mandate when the company needs a temporary owner for CTO-level decisions. A planned departure, extended absence, acquisition integration or leadership reorganization can create that need. Define which commitments must continue, which decisions cannot wait and which changes should remain for the permanent leader. A transition does not automatically justify redesigning the whole technology function.

CTO Academy's onboarding and power-transfer guide discusses temporary leadership, access to existing information and stakeholder introductions. Those are useful preparation topics. The specific duration, authority and workload still depend on the company's circumstances; a published description of an interim role is not a standard contract.

An interim leader should be able to enter an unfamiliar environment without pretending to understand it immediately. Ask how they establish a factual baseline, identify urgent decisions and test competing accounts of the situation. The strongest early contribution may be separating a genuine operational risk from a long-standing disagreement about preferred tools or team structure.

Reserve disruptive decisions for the appropriate approval process. Some changes may be necessary during the transition, but the interim executive should explain their urgency, reversibility and effect on the next leader. Document the alternatives. The aim is to leave a company with understandable decisions and workable continuity, not an unexplained set of commitments signed just before handover.

When a deputy CTO is the better fit

A deputy can help when the CTO's mandate is durable but too broad for one person to cover effectively. The delegated scope might include architecture across teams, internal technical governance, a portfolio of delivery responsibilities or a particular operating region. Specify what the deputy owns and what remains with the CTO. A vague instruction to help with everything makes performance difficult to evaluate.

The deputy's relationship with functional managers matters. If engineering managers report to a head of engineering, a deputy should not quietly become a competing line manager through informal executive access. Explain whether the role sets technical direction, coordinates priorities, manages people or performs a combination of those responsibilities. Then check that the arrangement fits the actual organization.

A deputy appointment can support succession development, but it should not be presented as a guaranteed future promotion unless that commitment genuinely exists. The current role must be valuable on its own terms. Discuss how the person will develop broader judgment, which decisions they will observe and how their readiness for additional responsibility will be assessed.

If the CTO is absent, define the coverage mechanism in advance. List decisions the deputy can make immediately, those requiring another executive's approval and those that can wait. Communicate the arrangement to relevant teams and suppliers. “Everyone knows who is in charge” is a fragile assumption during an incident, contract deadline or disagreement about a release.

Worked example: a CTO leaves before a major release

Imagine a hypothetical software company with four engineering teams. Its CTO will leave in six weeks, and a major customer release is planned for the following month. An existing deputy leads architecture reviews, while the head of engineering manages delivery. The example is invented to illustrate decision ownership; it is not a client story or a recommended transition timetable.

The first question is not who should inherit the title. It is which responsibilities the departing CTO currently performs. Perhaps the CTO approves material architecture exceptions, explains delivery tradeoffs to the CEO and maintains a key vendor relationship. The deputy may already understand the architecture work but have had limited involvement in commercial commitments or executive communication.

The company has at least three options: appoint the deputy acting CTO with appropriate support, bring in an interim executive with a defined relationship to the deputy, or divide a narrow set of responsibilities among existing leaders while recruiting. Each option has costs and dependencies. None should be chosen solely because it avoids an uncomfortable discussion about the current structure.

Suppose the planned release requires 12 review decisions, but only seven have a named accountable owner. The immediate issue is five unowned decisions, not an abstract lack of leadership. List each decision, its evidence, deadline and approval route. The resulting map may show that some can remain with established engineering managers while others require temporary executive authority.

If the deputy takes the acting appointment, reduce or reassign existing work where necessary. Adding all CTO responsibilities to an already full architecture workload creates an invisible capacity problem. Agree which meetings, reviews or projects the deputy will stop doing, and identify who will cover them. A temporary title without a change in capacity can increase risk rather than resolve it.

If the company appoints an external interim CTO, introduce the arrangement directly to the deputy and head of engineering. Establish how architecture recommendations, delivery estimates and customer commitments meet in one decision process. The interim executive should help the team make the release decision with evidence, including the option to change scope or timing, rather than promising that a new leader guarantees delivery.

Define authority before the first difficult decision

Create a short delegation record. Name the executive sponsor, the technology responsibilities assigned and the matters reserved to the CEO, board or another authorized person. Include spending, supplier commitments, personnel decisions and material changes to technical direction where those are relevant. Do not assume that access to a system or meeting creates approval authority.

For shared decisions, identify how participants contribute. An engineer may assess a technical option, a finance leader may evaluate the budget and the CTO may recommend a course of action. The final approval can still sit elsewhere. A useful responsibility map distinguishes preparing evidence, recommending, approving and implementing instead of putting several names in an undifferentiated owner column.

Make escalation practical. State who receives an unresolved issue, what information they need and which decisions require immediate attention. Define a backup contact for absence. The process should work under pressure without requiring everyone to reconstruct the organizational chart or infer permission from an old email conversation.

Review the delegation when the arrangement changes. If an interim engagement is extended, the responsibilities may have expanded beyond the original transition. If a deputy begins covering the CTO regularly, that may require a revised mandate and capacity discussion. Record the change openly rather than allowing an informal arrangement to become permanent by default.

Interview for the actual transition or delegation

An interim candidate should demonstrate judgment in unfamiliar situations, while a deputy candidate should demonstrate effective leadership within a defined relationship to the CTO. Both need relevant experience, but the evidence questions differ. Use the actual work in your brief to decide which examples matter most.

Criterion	Question	Evidence that helps the decision
Diagnosis	How did you separate urgent facts from competing opinions?	A clear investigation method and acknowledged uncertainty
Delegation	Describe a decision you could recommend but not approve	Respect for authority and an effective escalation route
Continuity	What did you preserve during a leadership change?	Attention to existing strengths, commitments and relationships
Capacity	What work stopped when your mandate expanded?	Realistic tradeoffs rather than unlimited availability
Collaboration	How did you resolve disagreement with another senior leader?	A decision process and the candidate's own contribution
Handover	What remained with the company after you left or changed roles?	Usable records, ownership and disclosed unresolved issues

Use a consistent rating scale with written reasons. Ask follow-up questions where the candidate's contribution is unclear. A claim about improved delivery needs a baseline, a period and an explanation of what changed around the team. Treat percentages without that context as incomplete evidence rather than automatically accepting or dismissing them.

Discuss the relationship the candidate expects with the incumbent or departing leader. An interim appointment should not depend on unrestricted access to a person who may be unavailable after departure. A deputy appointment should not require the CTO to approve every small action if the purpose is to distribute responsibility. Test whether the proposed working arrangement solves the problem described in the brief.

Handle the internal communication carefully

Explain the appointment to the team in terms of responsibilities and continuity. Name what changes, who remains responsible for delivery and how decisions will reach the new leader. Employees should not need to infer a leadership change from calendar invitations or a different person approving work. A concise shared explanation prevents conflicting interpretations from becoming part of the transition.

If an internal deputy is not appointed acting CTO, discuss the relationship directly and respectfully. The decision may reflect the temporary mandate, availability or a need for experience the company does not currently have. Avoid making the deputy responsible for supporting the transition while leaving their own authority uncertain. Their knowledge and established relationships can be essential to a successful arrangement.

Give customers and suppliers the information they need for their actual relationship with the company. Some require a new escalation contact or confirmation of decision ownership; others do not need detailed internal personnel information. Coordinate communication through the appropriate company owner. The new executive should not make commitments to demonstrate responsiveness before understanding the existing obligations.

Review what happens if the planned successor arrives earlier or later than expected. A useful transition arrangement identifies how responsibilities transfer, how overlapping time is used and who approves an extension. It should also make clear which work can finish independently of the permanent hire. Otherwise a delayed recruitment process can turn a temporary appointment into an open-ended mandate without deliberate review.

Finally, preserve a route for the team to raise concerns about the arrangement. A leadership transition changes relationships as well as formal responsibilities. The sponsor should distinguish ordinary adjustment from conflicting instructions or unmanageable workload. Addressing those issues early gives both the interim leader and the deputy a better chance of contributing effectively.

Copyable mandate for either appointment

Download the editable interim or deputy CTO mandate. No email address is required.

Use this outline as an internal discussion document before converting it into recruitment or engagement terms. It is not a contract, a vacancy announcement or a substitute for the organization's own approval process. Replace the prompts with accurate information and remove responsibilities that are not part of the actual role.

Reason for the appointment: State the departure, absence, capacity constraint or organizational change. Describe its effect on decisions and commitments rather than relying on a broad request for senior leadership.

Role relationship: Identify whether the person holds the CTO mandate temporarily or acts as deputy to a named CTO. If a deputy also covers an acting appointment, state when that additional authority applies.

Owned responsibilities: List the functions, technical decisions, management responsibilities and executive communications included. Identify existing leaders whose responsibilities remain in place.

Authority and limits: State what the appointee can decide, recommend and escalate. Record reserved matters, approval limits and the process for disagreements.

Capacity and support: Describe expected availability, necessary time-zone overlap, internal assistance and specialist support. Identify work that will be reassigned if an existing employee takes additional responsibility.

First-phase outputs: Request a decision inventory, continuity review, responsibility map or other concrete outputs that address the reason for the appointment. Name the person who accepts each output.

Review and transition: Define review dates, extension decisions, handover conditions and the information the next leader needs. Do not make completion dependent only on the passage of time.

Prepare a handover that another leader can use

A handover should explain the operating reality, not just list systems. Include current commitments, critical relationships, important decisions, known constraints and unresolved questions. Link each item to a named owner and supporting evidence. A list of tools without context will not tell the next leader why a difficult decision was made or what still needs attention.

Keep credentials and sensitive access details in the company's approved systems. The handover document should reference ownership and access procedures without exposing secrets. Have the appropriate internal team verify that essential accounts, repositories and supplier relationships remain accessible to the company. Documentation cannot compensate for access that still depends on a departed individual.

Use a working review with the incoming owner. Ask them to explain the immediate priorities, identify the next decisions and locate the information needed to act. Their questions reveal gaps that a document-only sign-off can miss. Record what remains uncertain and who will resolve it rather than presenting an artificially clean transition report.

A successful temporary or deputy arrangement leaves clearer responsibility and stronger continuity. It does not need to create a new strategy merely to prove that senior work occurred. If the appointment preserves a functioning team, resolves the important decisions and prepares the next owner, those are meaningful outcomes to evaluate against the original mandate.

Compare fractional and interim CTO arrangements if the remaining decision concerns reserved capacity versus a temporary transition. Fractional CTO Experts is an executive network and matching platform; request a shortlist with your mandate and verify each candidate's relevant experience and availability. The scenario is hypothetical and the images are generated illustrations. No independent expert review or guaranteed delivery outcome is claimed.