founding CTO

CTO / Technical Co-Founder —CoreIDLocation:Flexible (Kenya / Africa / Remote)Stage:Pre-seed, zero-to-oneCompensation:Equity (founder-level) + salary post-fundingCommitment:Full ownership mindset requiredAbout CoreID:CoreID is aconsent-driven Health Information Exchange (HIE)that enables patients and healthcare providers to securely identify, access, and share essential health information across facilities —without replacing existing medical record systems.We are buildinghealth infrastructure, not a startup app.This is a long-term, national-scale system with regulatory, clinical, and ecosystem complexity.The RoleWe are looking for aCTO / Technical Co-Founderto architect, build, and lead the technical foundation of CoreID from the ground up.This is not a "just write code" role.You will:Own system architectureMake irreversible technical decisionsTranslate health ecosystem constraints into scalable systemsBuild something that governments and hospitals must trustIf you are not comfortable building under uncertainty, resource constraints, and pressure —do not apply.What You Will Own (Non-Negotiable Responsibilities)1. Core ArchitectureDesign and implement a Health Information Exchange (HIE) architectureBuild a consent-first access control modelImplement minimal record vs extended record logicDesign for interoperability , not data centralizationBuild a federated or hybrid exchange model (not a monolithic EHR)2. Security & TrustImplement strong authentication & authorizationDesign audit trails , access logs, and consent historyApply privacy-by-design principlesUnderstand healthcare data sensitivity and compliance realitiesMake security decisions that survive regulatory scrutiny3. Interoperability & StandardsUnderstand (or quickly learn) health data standards:HL7 / FHIR (at least conceptually)APIs for labs, pharmacies, clinics, insurersBuild systems that integrate , not replaceDesign for facilities with very different levels of tech maturity4. MVP Execution (Extreme Speed, Extreme Focus)Build an MVP in < 8 weeksRuthlessly cut scopeNo overengineeringNo vanity featuresEvery line of code must serve pilot success5. Technical LeadershipSet engineering culture from day oneMake trade-offs consciously and document themEventually hire and lead engineersSpeak confidently to:HospitalsGovernment stakeholdersInvestorsTechnical auditorsWho You Must Be (Non-Negotiables)Youmust:Think in systems , not featuresBe comfortable with healthcare complexityUnderstand that this is not an EHRBe able to explain technical decisions in simple languageBe willing to build before you're paid cashHave founder-level ownership mentalityBe resilient, disciplined, and calm under pressureThis role is NOT for:FreelancersPart-time buildersPeople chasing quick exits"Idea people"People who need hand-holdingPeople uncomfortable with ambiguityCompensation & Equity (Read Carefully)This is a CTO / Technical Co-Founder roleEquity will be offered and negotiated privatelySalary will be introduced post-fundingNo fixed salary at this stageIf you are not comfortable with this — do not applyWe are looking for someone who wants tobuild something that matters, not just collect a paycheck.Why This Is Worth ItYou will help build national health infrastructureYour work will impact millions of livesYou will be a true co-founder , not an employeeIf successful, CoreID becomes foundational to healthcare systems.Technical Requirements (Non-Negotiable)The ideal CTO / Technical Co-Founder must havehands-on experiencein most of the following areas:Core EngineeringStrong backend engineering experience , Python, Go, or similar)API-first system design (REST / GraphQL)Experience designing multi-tenant systemsSolid database design (PostgreSQL, MySQL, or equivalent)Identity, Access & SecurityAuthentication & authorization (RBAC, OAuth, JWT, or equivalent)Consent-based access control modelsSecure handling of sensitive dataAudit logs and access traceabilityBasic threat modeling mindset(You don't need a PhD in cryptography — you need judgment.)System ArchitectureDesigning scalable, modular architecturesUnderstanding of federated or hybrid systemsExperience integrating with third-party systems via APIsAbility to design for low-tech environments and unreliable connectivityInfrastructure & DeploymentExperience deploying production systems (AWS, GCP, Azure, or equivalent)Containerization (Docker-level competence)CI/CD basics (GitHub Actions, etc.)Monitoring, logging, and error handlingHealth Tech (Bonus, Not Mandatory)Familiarity with:HL7 / FHIR (conceptual understanding is enough)Health data workflows (labs, pharmacies, clinics)Prior health-tech experience is a plus, not a requirementWe valuelearning speed over domain history.