A profileSeattle area, Washington
Karim Mohamed is a young entrepreneur and software builder from the Seattle area who likes turning ideas into working systems.
Most of his work so far has happened in software: building products, experimenting with AI, untangling operational problems and learning by shipping. The deeper pull has always been underneath the interface — how computation works, how software reaches the physical world, and how a machine might perceive, decide and act.
That curiosity is steering him toward computer engineering, hardware, artificial intelligence and robotics.
Karim has always been drawn to building things. The appeal was never a particular language or framework. It is the moment an idea that existed only in his head becomes something that runs, responds, and can be handed to someone else.
Software was the first place that could happen quickly. A problem noticed in the afternoon could be sketched by evening and running, imperfectly, the next day. Some of those experiments became products he still works on. All of them changed the way he approaches a problem.
Karim learns by making. He runs into a problem, gets curious about why it exists, and starts building before every answer is known.
The first version is never right. He tests it, something breaks, and the fix exposes a better question. The product changes, then the architecture underneath it. The idea only becomes clear in the act of implementing it.
That loop is not the cost of the work. For Karim, it is most of the attraction.
Karim founded Daythread to rethink how freelancers and small businesses manage the conversations — and all the operational work — that surround their customers.
For a photographer, a coach or a small studio, the business runs through messages: a question on Instagram, a text about rescheduling, an email asking about a date. Around those messages sit calendars, bookings, follow-ups and a scattering of disconnected tools. Daythread brings them into one workspace.
Take a client who writes, “Are you free Saturday afternoon?” Displaying that message is the easy part. The interesting problem is understanding what is being asked, connecting it to the calendar and the business’s workflows, and helping turn the conversation into an action — while the owner still decides what happens.
AI proposes. The owner decides.
Building Daythread has meant working across the whole system at once. Karim shaped the product architecture and the interface, wrote the frontend and the backend, and connected the integrations and automation that let messages from different channels land in one place.
Much of the work is the part nobody sees: authentication and security, testing, infrastructure and deployment. The product strategy moves with the code; each version clarifies what Daythread should become, and what it should refuse to do.
Developed in public: more than 280 commits and more than 890 automated tests since the first commit on 30 August 2026. Repository (opens in a new tab)
Academic planning for high-school students
Rushd started from a problem close to home. A student’s week is scattered across classes, assignments, exams, deadlines and whatever time is actually free. Rushd gathers those pieces and turns them into a prioritized plan: take something messy, build a system around it, make it easier to act on.
therushd.com (opens in a new tab)Internship management, associated with EdAI
InternOps applies the same instinct to a whole program. It coordinates interns, task assignments, work sessions, proposals, communication, alumni and certificates, with the administrative workflows that hold them together.
GitHub (opens in a new tab)Looked at together, the projects share a shape. Again and again, Karim has ended up building software that coordinates people, information and work — and each time, the valuable part is less the screen than the system behind it.
His time with EdAI also included a hackathon, where his team placed second and received $1,000 in group prize earnings.
A thought, then an interface, then a system, then a product, then something another person can use.
Software was the fastest route from an idea to something real. That immediacy is what drew Karim in.
But building kept exposing the layers underneath: how data moves through a system, why something slows down, what the processor is actually doing, where the software ends and the machine begins. The more he built, the more those layers became the interesting part.
Software was the entry point. Computing became the deeper question: not only what a program does, but how computation happens at all.
From there, hardware became interesting — computer architecture, embedded systems, the physical constraints software usually hides. Artificial intelligence added perception and decision-making. Robotics connects all of it to the physical world.
These are directions of curiosity, not claims of expertise. His long-term direction is computer engineering, with interests reaching into computer vision, autonomous systems and intelligent machines.
The physical world
The intersection of computation, perception, intelligence and physical systems is where Karim ultimately wants to go deeper.
One question runs through everything so far, and through what comes next.
| Work | System | Status |
|---|---|---|
| Daythread | Business systems | Built |
| Rushd | Planning systems | Built |
| InternOps | Operational systems | Built |
| Computer engineering | Computational systems | Next |
| Artificial intelligence | Intelligent systems | Next |
| Robotics | Physical systems | Next |
Karim is at the beginning of this path, and being early is part of the story.
Software remains the medium he builds with today — Daythread first, and whatever problem turns up next. Computer engineering, hardware, artificial intelligence and robotics are the deeper systems he wants to understand, and eventually to build.