Ten tracks, from AI to business analysis. Every one ends the same way: you have shipped real work, in a real team, and you can explain it to anyone who asks.
Live sessions, always recorded · Interest-free instalments · Verified credential
Why we exist
There has never been more material available, and it has never been easier to finish a course and still be unemployable. Four reasons — all four fixable.
Courses end and nothing follows them. You finish with a folder of exercises that look exactly like everyone else’s exercises, and an employer has no way to tell you apart. Here, real project work starts in week three — while you are still learning the tools, because that is the only way the tools stick.
This is the most common complaint we hear from employers in Egypt and the Gulf, and almost no programme in this market addresses it. Twenty-four graded hours of this sit inside every single track we run.
The market is flooded with PDFs nobody can check, so recruiters discount all of them — including the ones that were genuinely earned. Every credential we issue carries a unique number and a public verification page, and we can revoke it.
Most graduates have only ever written code alone, at their own pace, with nobody depending on them. Every project here runs in a team of three to five with rotating leadership, in a shared repository, with real merge conflicts and a real deadline.
“We interview graduates who can build the thing and cannot tell us what they built. That is the gap.” — the feedback that started this company
The method
Whether you take AI, mobile development or business analysis, you pass through the same four stages — which is exactly why the credential means one consistent thing.
A real brief, real constraints and a fixed deadline, starting week three. Not a tutorial with the answers at the bottom.
Twenty-four hours of communication and team management, running alongside the technical work and graded.
Teams of three to five, rotating leadership. Everyone leads a sprint and is reviewed by teammates, not just an instructor.
Issued only on a passed assessment, with a public verification page and the right to revoke.
How you attend
Every session is live.
Every session is recorded.
No pre-recorded courses. No watching someone talk at a slide from two years ago. You are in the room with your instructor and your team — and if you miss one, you catch up the same day.
Two live sessions a week with your instructor and your cohort. You can ask a question the moment you are stuck — the entire reason live teaching still beats video.
Every session is recorded and stays available to your cohort for a full year. Miss one for work or family and nothing is lost — and you can rewatch the hard parts as often as you need.
If your cohort turns out to be concentrated in one city, we add in-person lab days — full days of pair work and hands-on exercises. We confirm that once the group is formed rather than promising it in advance.
From week three you work in a fixed team on the Live Build — standups, a shared repository, a deadline. That continues whether your cohort meets in person or not.
Professional Core
Twelve sessions, twenty-four hours, in every track. Taught against your own live project rather than a case study, so you are practising on work that actually matters to you.
Emails, tickets, pull request descriptions, status updates. The most-used professional skill and the one nobody is ever taught.
A README that lets a stranger run your project. Writing for whoever joins in six months — usually you, having forgotten everything.
Translating what you built for a manager, a client or a finance director. The skill that decides who gets promoted.
Presenting working software under time pressure. Recorded, watched back, done again. Uncomfortable, and the highest-return two hours here.
Clarifying a vague brief before you build the wrong thing. Saying “I don’t know” without losing authority. Raising a blocker early.
The specific registers of standups, code review, client calls and interviews. Aimed at Gulf and remote work.
Branching, pull requests, review etiquette, and resolving a conflict without losing work or a teammate.
Standups, planning, estimation — and why every estimate is wrong, what to do about it, and how to flag a slipping deadline before it slips.
Agenda, timebox, written outcome, an owner for every action. You will run at least two real project meetings and be graded on them.
Breaking work down, delegating, unblocking others, and resisting the urge to do it all yourself at 2am.
Reviewing code so it improves without damaging the person. Taking criticism without defending. Disagreeing with a senior and staying employed.
Written-first collaboration across time zones — the working mode for every Gulf, European or freelance client you will ever have.
It is graded, and the grade is printed on your credential. A student who writes brilliant code and cannot work with anyone does not graduate with distinction here. We say that to every applicant on day one, because it is the whole point.
Tracks
Each track is led by a working practitioner in that field — not a career trainer. The Professional Core, the Live Build and the assessment standard are identical across all of them.
Prices shown are the Cohort tier. Every track runs live with recordings, and adds in-person lab days when the cohort is concentrated in one city. See full pricing.
Not sure which one?
We would rather point you at the right track than sell you the popular one. Answer these and you will get a match, two alternatives, and the reasoning behind all three.
How a cohort runs
Shown for an 18-week track. Shorter and longer tracks compress or extend the technical blocks — the Live Build and the Professional Core keep the same shape.
A written application, a short call, and a prerequisite check. If you are not ready, we tell you what to close first rather than take your money and watch you struggle.
Tooling, the stack, and getting every student to a working setup. Nobody starts the Live Build fighting their laptop.
Runs every week from here to the end, alongside the technical content. It never gets cut for time — that is a rule, not an aspiration.
Teams of three to five, a real brief, a fixed deadline. You start building before you feel ready, which is the point.
Two live sessions a week plus roughly six hours of your own project work between them. Leadership rotates each sprint. In-person lab days here if the cohort is in one city.
Each team presents to the group — your first recorded five-minute demo. Also where we catch anyone drifting: week 9 is recoverable, week 15 is not.
Harder material, and the Live Build moves from working to finished. Peer review, documentation, and the parts of a project everyone avoids.
An individual assessment on unseen work, written to professional standard. This is what the credential certifies, and it can be failed.
Public demo day. Credentials issued the same day so you can post them immediately. Top performers move on to a supervised engagement.
Proof
Every claim on this page is checkable. Below is what Batch 01 shipped, what happened to them afterwards, and what they said about it — in their own words, unedited.
[ Two sentences on what it does and what was hard about it. Be specific — “detection ruleset for credential dumping, tuned to zero false positives over 72 hours” beats “a security project”. ]
[ What it does, and the measurable result. Numbers are what make this section work. ]
[ Pick the three strongest capstones, not the three prettiest. Employers can tell the difference. ]
“[ A real quote from a graduate, collected at graduation while it is fresh. Keep the unflattering parts — ‘week 6 nearly broke me’ is more convincing than ‘amazing course’. ]”
“[ Second quote. Ideally from someone who got a job, naming what actually helped in the interview. ]”
“[ Third quote — from an employer who hired a graduate, if you can get one. An employer quote outweighs three student quotes. ]”
Everything marked in brown is a placeholder. Replace it with real Batch 01 content before launch — invented testimonials are the fastest way to lose the credibility this whole page is built on.
Pricing
Both include live sessions, recordings, the Live Build, the Professional Core, the capstone assessment and — on passing — a verified credential. Interest-free instalments on both, and most students use them.
| Track | Weeks | Cohort | Career Track |
|---|
Three or four interest-free payments. No third-party lender, and the total does not change if you use the plan. Pay in full and take 10% off.
15% off the first ten seats in every cohort. It is not extended and not negotiated afterwards — which is what makes it worth taking.
Two needs-based seats per cohort, by written application. Assessed on ability and circumstance, not on who applies fastest.
The credential
Pass the capstone and you receive a Certificate of Professional Competency carrying a unique number and a QR code. Anyone can confirm it here — no account, no email, no waiting.
Signed by the Chief Executive and by the instructor who actually taught you — so a hiring manager knows who to ask. The reverse carries your full transcript: every module, its hours, and the project you shipped.
Delivered as a PDF and a share image on graduation day.
Technical and Professional Core, shown separately. Employers see how you work, not only what you know.
Every module, its hours, and the project you shipped — so nobody has to guess what your diploma contained.
We can withdraw a credential, and this page says so permanently. That is what makes a valid result worth trusting.
Issued after a passed capstone. Finishing without passing earns a Certificate of Attendance, which says exactly that.
Who teaches
Career trainers teach the version of the stack that was current when they stopped working — and you find out in your first interview. Every track here is led by someone shipping in that field this year.
Founder · Professional Core · Security tracks
Teaching Assistant at the Faculty of Computers and Information Sciences, Mansoura University, and cybersecurity instructor at the National Telecommunications Institute. Background as a SOC analyst and blue team engineer.
Teaches the Professional Core on every track, and leads the security tracks personally.
Track leads are named on every cohort page. You will always know exactly who is teaching you before you pay.
For companies
We are building a talent pipeline, not a course catalogue. If you hire technical people in Egypt or the Gulf, there are three ways to work with us.
Tell us what you need and we introduce candidates whose capstone work we can show you before the interview — with both grades, so you know how someone works as well as what they know. You are reading evidence, not a CV.
Private cohorts on any track, scheduled around your team’s shifts, live online or on site if your team is in one place. The Professional Core is usually the reason companies call — senior engineers who cannot present are a common and expensive problem.
Give a cohort a real brief from your business. You get a working prototype and a close look at a dozen candidates under real conditions; they get work that genuinely matters. The most effective recruiting our partners do.
To start any of these, email hello@technologywarehouse.org or use the application form and mark it as corporate.
Apply
This is not a checkout page. Fill this in, send it, and you will hear back within three working days with a place, a prerequisite plan, or an honest no.
Questions
Live. Two sessions a week with your instructor and your cohort, where you can ask a question the moment you are stuck. Every session is also recorded and stays available to your cohort for a full year, so missing one for work or family costs you nothing.
We do not sell pre-recorded courses. The recordings exist so you can catch up and rewatch, not so you can take the programme alone.
Online by default, so you can join from anywhere in Egypt or the region. When a cohort turns out to be concentrated in one city, we add in-person lab days — full days of pair work and hands-on exercises. Whether that happens depends on where your particular group is, and we confirm it once the cohort is formed rather than promising it in advance.
It depends on the track, and the application asks. Broadly: for the engineering and data tracks you need programming fundamentals and comfort with a command line. For Business Analysis, UI/UX and QA you can start from close to zero if you are willing to work hard. For AI you need Python and a real grasp of the mathematics — we will not pretend otherwise.
If you are short on prerequisites, say so on the application. We will tell you exactly what to close first rather than take your money and watch you struggle.
About twelve. Four hours of live sessions and six to eight hours of your own project work. People who treat it as four hours a week do not finish, and we say so in advance because our completion rate matters more to us than our enrollment number.
A brief from an actual organisation, or an internal build with genuine requirements and constraints, with a fixed deadline and a demo to people who were not your instructor. You work on it in a team from week three until the end of the programme.
It is not a tutorial project with the solution published. Some teams do not finish everything they planned, which is also what happens in industry, and learning to handle that is part of the point.
Yes, on every track, and it is graded. A student who writes excellent code but cannot work with anyone does not graduate with distinction. Some applicants think this is filler taken from "real" content — if that is your view, this is probably not the right programme for you, and we would rather you knew now.
No, and be suspicious of anyone who does. The Career Track gives you priority placement on a supervised engagement as real project work becomes available, so you finish with referenceable work rather than only a certificate. We are a new company and we will not pretend to a placement network we have not built yet — what we can promise is that your capstone goes in front of every employer we talk to.
Technical instruction is in English, because that is the working language of the field, of documentation, and of the Gulf employers many graduates go on to work for. Support, discussion and explanation happen in Arabic whenever it helps. Nobody is left behind for language reasons — but expect to read documentation in English.
Yes, three or four interest-free payments on either tier, and most students use them. Pay in full and there is a 10% discount. There is no third-party lender and no interest, so the total does not change if you use the plan.
It is not accredited by an international body, and we will not pretend otherwise. What it is: verifiable, specific about what you did, and backed by a project and a transcript you can show. In practice, a hiring manager reading your capstone and watching your demo learns more about you than any certificate name would tell them.
Track-dependent. Engineering, data and design tracks need a reasonable laptop — 8 GB of RAM is workable, 16 GB is comfortable. The security and cloud tracks need 16 GB and around 250 GB free for virtual machines. AI work runs on cloud GPUs we provide. If hardware is a problem, raise it on your application; we would rather solve it before week one than during it.
You receive a Certificate of Attendance, which states plainly that you completed the course without passing the assessment, and you may resit with the next cohort at no additional cost. We do not issue the credential to people who have not passed — if we did, it would stop meaning anything for everyone who has.
The small print
Written in plain language, because small print that nobody can read protects nobody. If anything here is unclear, ask before you pay.
What we collect. When you apply we collect your name, email address, phone number, city, and what you tell us about your background and goals. If you enrol we also keep a record of your attendance, submitted work and assessment results. That is all.
Why. To assess your application, to run the programme, and to issue and verify your credential. Nothing else.
What we publish. Your name, programme, cohort, issue date and credential status appear on the public verification page once you are awarded a credential. That is the entire point of the credential and you can ask us to withdraw it from public verification at any time. We never publish your email address, phone number or application.
Who else sees it. Nobody, unless you ask us to introduce you to an employer. We do not sell, rent or share applicant data, and we do not send marketing to people who did not ask for it.
How long we keep it. Applications that do not lead to enrolment are deleted within 12 months. Student records and credential records are kept indefinitely, because a credential you cannot verify in five years is worthless.
Your rights. Write to us and we will tell you exactly what we hold about you, correct anything wrong, or delete it. Deleting your student record means we can no longer verify your credential, so we will say so before we act.
A place is confirmed when the first payment clears, not when you apply. Applications are assessed individually and we may decline one; if we do, we will tell you why.
What we commit to. To deliver the published number of instruction hours, live, with recordings; to provide the project brief and supervise the work; to assess your capstone fairly against a written standard; and to issue a verifiable credential if you pass.
What we do not promise. A job. Any specific salary. That any particular employer will hire you. Career Track gives priority placement on supervised engagements as they become available — it is not a guarantee of paid work.
What you commit to. Roughly twelve hours a week, your own work rather than someone else's, and treating classmates and instructors decently. Submitting work that is not yours is the one thing that ends a place immediately and without refund.
Cohort changes. If too few students enrol we may postpone a cohort. If we do, you choose a full refund or a place in the next one.
Credentials can be revoked if they were obtained through plagiarism or misrepresentation. This is rare and we would contact you first.
Before the programme starts — full refund, no questions, no fee.
In the first two weeks — full refund minus any instalment already used, no questions asked. Two weeks is enough to know whether this suits you, and we would rather you left early than struggled through.
Between weeks three and six — 50% refund of the remaining balance.
After week six — no refund, because the teaching has been delivered. If something serious has happened in your life, tell us: we will move you to a later cohort at no cost rather than take your money for a programme you cannot attend.
If we cancel or postpone — full refund, always, regardless of timing.
How long it takes. Refunds are processed within 14 working days to the account that paid. Instalment plans are stopped immediately on request.
Technology Warehouse is a technical training company operating in Cairo and Mansoura, Egypt, founded and run by Saher Waleed.
Company registration. Technology Warehouse is not yet formally registered as a company; registration is in progress. We state that plainly because corporate buyers ask, and because you deserve to know who you are paying. This page will carry the commercial registration number and tax ID as soon as they exist.
Questions about any of the above: hello@technologywarehouse.org.
Purple Team and Business Analysis are running now. Everything else starts 1 July 2027 — register interest and you get first refusal on a seat.