Hello, I am Tarek Mohammed
A software engineer who believes
A good site
holds up under load
Any interface looks fine on a quiet day. The difference shows up during the ad campaign, when a thousand people arrive in an hour and every form and every payment has to work.
I build the layer that carries the growth
Ordered databases, readable APIs, and integrations into payment, stock and CRM systems. I write on the assumption that someone else reads this in a year.
What Tarek owns inside a project
The hard part of most projects is not building the feature — it is making it work with everything else without breaking something. That is where Tarek sits.
A data model built once
He designs tables and relationships before the first line of interface code, because restructuring data after launch costs far more than getting it right up front.
Wired into the systems you run
Local payment gateways, stock systems, CRM tools. He handles the cases people forget: the dropped connection, the double charge, the order that only half arrived.
Defined behaviour on failure
No generic error screen. He decides what the user sees, what gets logged for the team, and what should page someone immediately.
How Tarek takes work in and hands it on
How many users? How many orders a day? What must stay true at all times? The answers decide the architecture — preferences do not.
Tables, relationships, indexes. This step determines how fast the site is a year from now more than any later optimisation.
Short, explicit endpoints a front-end developer can use without asking what each field means.
Connect the external systems, then break them on purpose: declined payments, dropped connections, partial data.
Error logging and alerts that reach the team before the client calls. An unmonitored site is one where the customer finds the outage first.
Read the requirements as numbers
1How many users? How many orders a day? What must stay true at all times? The answers decide the architecture — preferences do not.
Design the data
2Tables, relationships, indexes. This step determines how fast the site is a year from now more than any later optimisation.
Build the APIs
3Short, explicit endpoints a front-end developer can use without asking what each field means.
Integrate and test the failures
4Connect the external systems, then break them on purpose: declined payments, dropped connections, partial data.
Ship with monitoring
5Error logging and alerts that reach the team before the client calls. An unmonitored site is one where the customer finds the outage first.
When the logic matters more than the layout
Tarek is the right name on a project with calculations, stock, payments, or an existing system you cannot replace.
Let’s build something precise, useful, and ready to grow.
Want to talk to the person who'd do the work?
Tell us what you are building, where it is stuck, and what the next step needs to achieve. You will get a straight answer about scope and sequence — and it will come from whoever would actually build it.