Skip to main content
Loading
loadingbar
Loading, Please wait..!!

Director of Technology Operations & Assurance

  • Director of Technology Operations & Assurance job type Posted on: Oct 19, 2026
  • Director of Technology Operations & Assurance experience level DiversyFund, Inc
  • Director of Technology Operations & Assurance employment type San Diego, Texas
  • Director of Technology Operations & Assurance employment type Onsite
  • Director of Technology Operations & Assurance salary Full-time

Point Apply Here APPLY LATER

Curious about compensation?

Explore the historical salary trends, average pay, and estimated compensation for Director of Technology Operations & Assurance roles in Texas.

View Salary Guide →

Job Title :

Director of Technology Operations & Assurance

Job Type :

Full-Time

Job Location :

San Diego Texas United States

Remote :

No

Jobcon Logo Job Description :

Director of Technology Operations & AssuranceLocation: San Diego, CA — In OfficeEmployment: Full-TimeReports to: CEOWorks closely with: Chief Architect/CTO and Director of Engineering & AI Product DevelopmentThe MissionCreate the operating discipline and independent verification system around the technology organization.Engineering builds the technology.You make sure leadership knows what was promised, whether it was delivered, whether it works, whether it is documented, and where risk exists.Your operating model is:Commitment → Owner → Date → Verification → QA → Documentation → Risk → CEO VisibilityYou are not responsible for building the company's software or managing engineers.You are responsible for making technology execution visible, accountable, testable and resilient.What You OwnTechnology Program GovernanceMaintain the company's single source of truth for technology execution.Every meaningful initiative should have:Defined objectiveAccountable ownerDeliverablesDependenciesCommitted datesCurrent statusRisksBlockersAcceptance criteriaDefinition of doneYou do not decide how engineering builds something.You make sure commitments are explicit and measurable.Problems should surface before deadlines are missed.Independent QA & Release AssuranceOwn the verification layer between:"Engineering says it's finished"and"The company has verified that it works."Establish processes for:QAAcceptance testingRegression testingRelease verificationProduction validationDefect trackingPost-release verificationEngineering owns building and fixing the software.Technology Operations owns independently determining whether it meets the agreed requirements.A project is not complete because code exists.It is complete when it meets its acceptance criteria and works in production.Documentation & Key-Person RiskMake sure critical company technology does not exist only inside someone's head.Establish documentation requirements covering:System architectureInfrastructureDatabasesData flowsAPIsAI agentsRepositoriesDeployment proceduresEnvironmentsIntegrationsVendorsAccess requirementsTechnical decisionsRunbooksRecovery proceduresEngineering creates and maintains technical documentation.You verify that required documentation exists, is current and can actually be used by another qualified person.Security Governance & Operational ResilienceEstablish visibility and accountability around:Infrastructure accessCredentials and permissionsSource-code repositoriesProduction environmentsData securityVendorsBackup and recoveryBusiness continuityIncident responseSecurity policiesTechnical riskYou are not expected to personally operate every security system.You ensure appropriate controls exist, ownership is clear and material risks are surfaced.Technology RiskMaintain a technology risk register covering areas such as:Key-person dependencySecurity exposureInfrastructure concentrationUndocumented systemsVendor dependencyData risksProduction instabilityRecovery capabilityTechnical operational riskEscalate material risks directly to leadership.CEO Technology VisibilityCreate a simple executive technology dashboard that answers:What are we building?Who owns it?When was it promised?What's at risk?What's blocked?What shipped?Did it pass QA?Does it work in production?Is it documented?The CEO should not have to chase engineers for answers.What You Do NOT OwnYou do not own:Writing production softwareEngineering architectureEngineering implementationManaging software engineersAssigning engineering resourcesCode reviewsChoosing frameworksBuilding AI agentsTechnical product developmentResolving engineering problems yourselfThose responsibilities belong to the Director of Engineering and Chief Architect/CTO.Your role is to measure, verify, challenge, document and escalate—not become a shadow engineering department.First 90 DaysFirst 30 Days: Map projects, commitments, systems, ownership, access, documentation, security exposure and key-person risks. Establish the technology source of truth.By Day 60: Implement delivery reporting, QA standards, acceptance criteria, documentation requirements, risk tracking and CEO reporting.By Day 90: Establish a repeatable Technology Assurance operating system providing independent visibility into whether engineering is delivering working, documented and resilient technology.How Success Is MeasuredCan leadership see exactly what engineering is working on?Are commitments and dates explicit?Are missed commitments identified early?Does released technology pass independent verification?Are defects being identified systematically?Is critical technology documented?Is key-person dependency decreasing?Are security risks visible?Are operational risks being addressed?Can leadership understand technology status without chasing engineers?Your job is to create accountability and assurance without creating bureaucracy.

Jobcon Logo Position Details

Posted:

Oct 19, 2026

Reference Number:

10440_4475469833

Employment:

Full-time

City:

San Diego

Job Origin:

APPCAST_CPC

Share this job:

  • linkedin

Jobcon Logo
A job sourcing event
In Dallas Fort Worth
Aug 19, 2017 9am-6pm
All job seekers welcome!

Director of Technology Operations & Assurance    Apply

Click on the below icons to share this job to Linkedin, Twitter!

Director of Technology Operations & AssuranceLocation: San Diego, CA — In OfficeEmployment: Full-TimeReports to: CEOWorks closely with: Chief Architect/CTO and Director of Engineering & AI Product DevelopmentThe MissionCreate the operating discipline and independent verification system around the technology organization.Engineering builds the technology.You make sure leadership knows what was promised, whether it was delivered, whether it works, whether it is documented, and where risk exists.Your operating model is:Commitment → Owner → Date → Verification → QA → Documentation → Risk → CEO VisibilityYou are not responsible for building the company's software or managing engineers.You are responsible for making technology execution visible, accountable, testable and resilient.What You OwnTechnology Program GovernanceMaintain the company's single source of truth for technology execution.Every meaningful initiative should have:Defined objectiveAccountable ownerDeliverablesDependenciesCommitted datesCurrent statusRisksBlockersAcceptance criteriaDefinition of doneYou do not decide how engineering builds something.You make sure commitments are explicit and measurable.Problems should surface before deadlines are missed.Independent QA & Release AssuranceOwn the verification layer between:"Engineering says it's finished"and"The company has verified that it works."Establish processes for:QAAcceptance testingRegression testingRelease verificationProduction validationDefect trackingPost-release verificationEngineering owns building and fixing the software.Technology Operations owns independently determining whether it meets the agreed requirements.A project is not complete because code exists.It is complete when it meets its acceptance criteria and works in production.Documentation & Key-Person RiskMake sure critical company technology does not exist only inside someone's head.Establish documentation requirements covering:System architectureInfrastructureDatabasesData flowsAPIsAI agentsRepositoriesDeployment proceduresEnvironmentsIntegrationsVendorsAccess requirementsTechnical decisionsRunbooksRecovery proceduresEngineering creates and maintains technical documentation.You verify that required documentation exists, is current and can actually be used by another qualified person.Security Governance & Operational ResilienceEstablish visibility and accountability around:Infrastructure accessCredentials and permissionsSource-code repositoriesProduction environmentsData securityVendorsBackup and recoveryBusiness continuityIncident responseSecurity policiesTechnical riskYou are not expected to personally operate every security system.You ensure appropriate controls exist, ownership is clear and material risks are surfaced.Technology RiskMaintain a technology risk register covering areas such as:Key-person dependencySecurity exposureInfrastructure concentrationUndocumented systemsVendor dependencyData risksProduction instabilityRecovery capabilityTechnical operational riskEscalate material risks directly to leadership.CEO Technology VisibilityCreate a simple executive technology dashboard that answers:What are we building?Who owns it?When was it promised?What's at risk?What's blocked?What shipped?Did it pass QA?Does it work in production?Is it documented?The CEO should not have to chase engineers for answers.What You Do NOT OwnYou do not own:Writing production softwareEngineering architectureEngineering implementationManaging software engineersAssigning engineering resourcesCode reviewsChoosing frameworksBuilding AI agentsTechnical product developmentResolving engineering problems yourselfThose responsibilities belong to the Director of Engineering and Chief Architect/CTO.Your role is to measure, verify, challenge, document and escalate—not become a shadow engineering department.First 90 DaysFirst 30 Days: Map projects, commitments, systems, ownership, access, documentation, security exposure and key-person risks. Establish the technology source of truth.By Day 60: Implement delivery reporting, QA standards, acceptance criteria, documentation requirements, risk tracking and CEO reporting.By Day 90: Establish a repeatable Technology Assurance operating system providing independent visibility into whether engineering is delivering working, documented and resilient technology.How Success Is MeasuredCan leadership see exactly what engineering is working on?Are commitments and dates explicit?Are missed commitments identified early?Does released technology pass independent verification?Are defects being identified systematically?Is critical technology documented?Is key-person dependency decreasing?Are security risks visible?Are operational risks being addressed?Can leadership understand technology status without chasing engineers?Your job is to create accountability and assurance without creating bureaucracy.

Loading
Please wait..!!