Five years at LinkedIn
Senior Software Engineer on search and recommendations for LinkedIn News and Sales Navigator.
Fractional CTO for non-technical founders
I'm Ibraheem. I spent five years as an engineer at LinkedIn, hold a US patent in AI, and took a healthcare platform to production through SOC 2 and HIPAA as its founding engineer.
Now I work with founders who have a product to build and nobody senior on the technical side. I make the architecture, hiring, vendor and AI decisions with you, explain them in plain language, and build the hard parts myself when that is faster.
Track record
Senior Software Engineer on search and recommendations for LinkedIn News and Sales Navigator.
Inventor on a US patent for AI-driven recommendations.
As a founding engineer, took a healthcare platform to production through both audits.
Where I help
Most founders I talk to are in one of these spots. Each one is cheaper to get right now than to unwind in a year.
I read the code, the infrastructure and the contract, and tell you in plain terms what is solid, what is risky and what it will cost to fix.
I write the role, run the technical interviews and tell you who can actually do the work, so your first hire is not a guess.
I find the places AI pays for itself and build those. If a rule, a report or a change to the process would solve it better, I will say so.
Architecture, security, data handling, the roadmap. I prepare the answers and sit in the room for diligence.
Ways to work together
Start here
About two weeks. I review your code, infrastructure, vendors and team, then walk you through a written report: what works, what is at risk, and the next three things to do, in order.
Good for: a v1 built by someone else, a pending raise, or a decision you cannot make without a second opinion.
Ongoing
A fixed number of days each month as your technical lead. I own the roadmap and architecture, work with your developers or agency every week, hire, and represent the technology to investors and customers.
Good for: founders who need senior judgment every week but not a full-time executive salary yet.
Hands on
I build the thing myself: an MVP, an AI agent connected to your systems, or the piece your team is stuck on. You click through a prototype and approve it before I build it.
You keep the code, the tests and written instructions your team can follow after I leave.
How I work
The writing on this site is how I think about building software that people trust. It is a fair preview of how I will think about yours.
More about meYou should never need to be technical to understand what I recommend, what it costs and what happens if you do nothing.
I talk with the people who do the work and we agree on the result that matters before anyone writes code.
Every release is checked before your users see it. AI features are tested against real questions, and a person approves anything that sends, pays or deletes.
Your accounts, your code, your documentation. The goal is a company that runs well without me.
Latest notes
When AI is central to the product, model access, data boundaries, routing, cost, and reliability become important infrastructure decisions.
Prompts help, but reliable AI products need operating rules, review loops, permissions, and failure handling.
As agents take on more execution, the work shifts toward clearer goals, careful review, and accountable decisions.
Next step
A few sentences is enough: what the product does, who built it so far, and the decision in front of you. I will tell you whether I can help and what I would look at first.