Three months ago, a Dubai fintech founder came to me after their technical co-founder quit—taking the entire codebase with them. The company had raised $400K, spent six months building, but owned none of the code. The "CTO" had written everything on personal GitHub repos and refused to transfer it.
This disaster was 100% preventable.
Choosing a technical co-founder is one of the most important decisions you'll make as a startup founder. Get it right, and you have a partner who can build anything. Get it wrong, and you're looking at six months of wasted time, burned capital, and potentially starting over from scratch.
After 25 years in tech and working with dozens of startups in Dubai and Europe, I've seen this pattern repeat too many times. Here's what you need to know before bringing on a technical co-founder.
The Wrong Questions Most Founders Ask
When evaluating technical co-founders, most non-technical founders focus on the wrong things:
- "Do they know React/Node/Python?" (Wrong question)
- "Have they built an app before?" (Too vague)
- "Are they smart?" (Everyone thinks their co-founder is smart)
- "Do they work hard?" (Hard work on the wrong things wastes time)
These questions miss the point entirely. Technical skill is necessary but not sufficient. You're not hiring a developer—you're choosing a co-founder who will make or break your company.
Here's what actually matters.
The 7 Critical Evaluation Criteria
1. Can They Ship? (Not Just Build)
The Difference:
Building is writing code. Shipping is delivering working software to actual users.
I've met dozens of "technical co-founders" in Dubai who can write beautiful code but have never shipped a product that real users depend on. They get stuck in endless refactoring, perfectionism, or "we need to rebuild this properly first."
How to Evaluate:
- Ask: "What's the fastest you've ever shipped a working product to real users?"
- Good answer: "2-3 weeks for an MVP, then iterated based on feedback"
- Red flag: "Well, I spent six months building a proper architecture first..."
The Right Mindset:
You need someone who understands that week one's goal is learning, not perfection. Someone who can build an MVP in 2-3 weeks, get it in front of users, and iterate based on real feedback.
Real Example:
A Dubai e-commerce founder interviewed two technical co-founders:
- Candidate A: "I need 4 months to build a proper scalable platform"
- Candidate B: "I can have a working Shopify + custom checkout in 10 days. We'll know if people will pay before building anything custom."
Candidate B shipped in 12 days. They made their first $5,000 in sales within the first month. Six months later, they raised seed funding and hired a team to build custom infrastructure—but they already had proof of concept and paying customers.
2. Do They Understand Business, Not Just Technology?
The Problem:
Many technical people optimize for interesting problems, not business value. They want to use the latest framework, the coolest architecture, the most impressive tech stack—regardless of whether it helps the business.
How to Evaluate:
Present a scenario: "We need to launch in 6 weeks for a major trade show in Dubai. We can either build custom or use Bubble/Webflow with integrations. What do you recommend?"
Good Answer:
"Depends on the product. If it's primarily content/frontend, I'd use a low-code tool and ship in 2 weeks. That gives us 4 weeks to iterate based on early feedback. We can always rebuild properly once we've validated the market."
Red Flag Answer:
"We should never use low-code tools. We need to build everything custom from day one with proper architecture."
The Distinction:
Great technical co-founders think like product people. They ask "What's the fastest way to validate this?" before asking "What's the most elegant solution?"
3. Do They Know What They Don't Know?
Dunning-Kruger in Tech:
The worst technical co-founders are the ones who think they know everything. They've built one or two apps and now believe they're experts in everything from security to scaling to DevOps.
How to Evaluate:
Ask about areas outside their expertise:
- "How would you approach building a GDPR-compliant system for UAE/EU customers?"
- "What's your strategy for handling 100,000 concurrent users?"
- "How would you structure our cloud infrastructure for regulatory compliance in the UAE?"
Good Answer:
"I haven't built for that scale before. Here's what I'd research, and I'd probably bring in a consultant who specializes in compliance/infrastructure for the setup."
Red Flag:
"Oh yeah, I've done that. It's easy—you just..." [proceeds to describe something that's actually quite complex]
Why This Matters:
A co-founder who knows their limits will seek help when needed. One who doesn't will waste months building the wrong solution before admitting they need help.
4. Can They Explain Technical Decisions to Non-Technical People?
The Test:
Ask them to explain a technical decision to you like you're a smart 15-year-old.
"Why should we use PostgreSQL instead of MongoDB?" or "What's the difference between serverless and traditional hosting?"
Good Answer:
Clear, jargon-free explanation using analogies. "PostgreSQL is like a filing cabinet with strict rules—everything has its place and relationships are clear. MongoDB is like a box of documents—more flexible but easier to get messy."
Red Flag:
Either way too technical (jargon-heavy, assumes you understand) or way too simplistic (condescending, no substance).
Why This Matters in Dubai:
You'll need to pitch to investors, explain technical risks to board members, and make strategic decisions together. If your technical co-founder can't explain technology in business terms, you're going to struggle with every major decision.
5. How Do They Handle Being Wrong?
The Scenario:
Tell them about a technical decision you think should be made differently (even if you're not sure). How do they respond?
Good Response:
- Listens carefully
- Asks clarifying questions
- Explains their perspective
- Either explains why your idea wouldn't work (with specifics) or says "That's actually a good point, let me think about that"
Red Flag Response:
- Immediately defensive
- Dismisses your input without consideration
- "You don't understand, this is a technical decision"
- Can't admit when they might be wrong
Real Story:
A Dubai SaaS founder suggested using WhatsApp Business API for their customer communication instead of building custom chat. The technical co-founder insisted they needed to build everything custom. Four months and $80,000 later, they had buggy custom chat that worked worse than WhatsApp would have.
A good technical co-founder would have evaluated both options honestly and chosen based on business needs, not ego.
6. What's Their Code Like? (If They Have Public Projects)
Important Check:
If they have public GitHub repos, look at them. You don't need to understand the code—you're looking for patterns:
Good Signs:
- README files explaining what the project does
- Consistent commit history (regular work, not massive dumps)
- Comments in the code explaining complex logic
- Tests (shows they care about quality)
- Recent activity (they're actively coding)
Red Flags:
- No public code at all (and they claim to be experienced)
- Massive, sporadic commits (suggests disorganized work)
- Zero documentation
- Abandoned projects everywhere
- Code is all copied from tutorials with minimal changes
The Dubai Context:
Many technical people in Dubai's market have impressive resumes but limited hands-on experience. Public code (even hobby projects) shows they actually build things, not just talk about building things.
7. Do They Understand the Local Market?
UAE-Specific Considerations:
- Local payment gateways (Network International, Telr, etc.)
- Arabic language support (right-to-left UI challenges)
- Regional cloud hosting (AWS Bahrain vs US/EU)
- Local regulations (data residency, e-commerce licensing)
- Mobile-first reality (UAE has 99%+ smartphone penetration)
How to Evaluate:
Don't expect expertise, but do expect awareness. A good technical co-founder in Dubai should at least know these are considerations, even if they need to research specifics.
Red Flag:
"We'll just build it like a US product and localize later." Localization isn't a feature you add at the end—it affects architecture from day one.
The Deal Structure Questions You Must Ask
Before committing to a technical co-founder, get these details in writing:
Intellectual Property
- Question: "Who will own the code, and where will it be hosted?"
- Right Answer: "Company-owned repos from day one. All work is work-for-hire assigned to the company."
- Red Flag: "I prefer to work on my personal accounts and transfer later."
Time Commitment
- Question: "Are you full-time on this, or do you have other commitments?"
- Right Answer: "Full-time once we raise/launch" or "Part-time now with a specific transition plan to full-time."
- Red Flag: Vague commitments or "I'll balance multiple projects."
Vesting
- Question: "What vesting schedule makes sense?"
- Right Answer: "Standard 4-year vest with 1-year cliff."
- Red Flag: "I want all my equity up front" or resistance to vesting.
Exit Scenarios
- Question: "What happens if one of us wants to leave?"
- Discussion Needed: What happens to unvested equity? Can the company buy back shares? What are the terms?
This is uncomfortable but essential. The time to discuss breakup is before the relationship starts.
Red Flags That Should End the Conversation
Some warning signs mean you should walk away immediately:
Won't sign an NDA or IP assignment - If they're not willing to protect your IP before you've even started, what happens once they have access to everything?
Promises unrealistic timelines - "I can build Instagram in 6 weeks" is either lying or delusional.
Dismissive of non-technical input - Your role is business/product. If they don't respect that, the partnership won't work.
No references - Every experienced technical person has worked with others who can vouch for them.
Only talks about technology, never about users or business - You're building a business, not a technology demonstration.
The Danish Standard
In Denmark's tech ecosystem, there's a strong culture of pragmatism. Danish developers are known for building things that work reliably rather than things that are architecturally impressive.
This is the mindset you want in a technical co-founder:
- Ship first, optimize later
- Boring technology that works beats exciting technology that doesn't
- User needs trump technical preferences
- Measure everything, assume nothing
If your technical co-founder embodies these principles, you're in good shape.
What If You Can't Find the Right Co-Founder?
If you're struggling to find a technical co-founder who meets these criteria, you have options:
Option 1: Fractional CTO
Bring on an experienced CTO part-time to guide technical strategy while hiring developers to execute. You get senior technical leadership without giving up significant equity.
Option 2: Technical Advisor + Lead Developer
Instead of a co-founder, bring on a technical advisor (1-2% equity) and hire a strong lead developer. This costs more short-term but might be safer than the wrong co-founder.
Option 3: Agency/Consultant to MVP, Then Hire
Build your MVP with a development partner, prove market fit, then hire a technical co-founder or CTO when you can afford to pay for the right person.
Each has tradeoffs, but all are better than choosing the wrong co-founder out of desperation.
The Bottom Line
Choosing a technical co-founder is not about finding the best developer. It's about finding someone who can:
- Ship products quickly and iterate
- Think in terms of business value, not just technology
- Communicate clearly with non-technical people
- Admit what they don't know and seek help
- Handle disagreement constructively
- Understand your market and users
Technical skills matter, but they're the baseline. The difference between success and failure is usually in these softer factors.
Take your time. Meet multiple candidates. Do reference checks. Have the uncomfortable conversations about equity, IP, and exit scenarios before you commit.
Your technical co-founder will influence your startup's trajectory for years. Choose carefully.
Need help evaluating technical talent or looking for fractional CTO services? We help Dubai startups build the right technical foundation. Schedule a free 30-minute consultation to discuss your needs.