Tamim Abbas Aljuratli
Software engineer, systems architect, founder, and engineering leader.Tamim Abbas Aljuratli is a Syrian-Spanish software engineer, systems architect, engineering leader, and Founder of ReemRose. For more than a decade, Tamim has worked across software engineering, architecture, engineering management, product development, and technical leadership. His career has taken him from hands-on software engineering to leading international engineering teams, designing complex software systems, helping founders make technical decisions, and building products across different industries and markets. Tamim Abbas Aljuratli has worked with companies and organizations including FutureLearn, OVO Energy, Pearson, and Smoll AI, alongside years of independent engineering, consulting, entrepreneurship, and product development through ReemRose. Today, much of Tamim's work sits somewhere between engineering, architecture, product, and business.
About Tamim
Tamim Abbas Aljuratli started his career as a software engineer, but he was always interested in more than the code in front of him.
He wanted to understand how the whole system worked.
Why was something designed a certain way? What would happen when the product grew? Where should responsibilities live? How should engineers work together? Which technical decisions mattered now, and which ones could wait?
That curiosity gradually took Tamim from hands-on software engineering into systems architecture, technical leadership, and engineering management.
He remained an engineer, but the problems became larger.
Instead of only asking how to build a feature, he increasingly found himself asking how the entire product, system, team, and business fit together.
That way of thinking still defines Tamim's work today.
From Engineer to Engineering Leader
Tamim Abbas Aljuratli moved into technical leadership early in his career.
Over the years, he has worked with FutureLearn, OVO Energy, Pearson, and Smoll AI, as well as startups, founders, and independent clients across different industries.
At Pearson, Tamim worked in engineering management and led engineers working across several countries and time zones.
That experience reinforced something he had already begun to understand:
strong engineering is not only about strong developers.
Architecture matters. Ownership matters. Communication matters. Product understanding matters. And engineers make better decisions when they understand why the business needs something rather than simply being told what to build.
As Tamim's career developed, he became increasingly interested in the space between technology and business — the decisions that often determine whether a good idea becomes a good product.
How Tamim Thinks
Good engineering is mostly about making good decisions.
Technology changes constantly.
Programming languages change. Frameworks change. Infrastructure becomes easier. New tools appear. AI is changing how software gets built again.
But the important questions remain surprisingly similar.
What are we actually trying to solve?
What complexity is necessary? What complexity are we creating for ourselves? What needs to exist now? What can wait? And what happens if the product actually succeeds?
Tamim does not believe every startup needs enterprise architecture.
He also does not believe that moving quickly means building something carelessly and hoping somebody fixes it later.
The job is to find the right balance for the business, the product, and the stage the company is in.
Problems Tamim Likes to Solve
Tamim Abbas Aljuratli is at his best when the problem is bigger than a single feature.
Often, that means situations where a company knows something is wrong technically but cannot yet explain exactly what the problem is.
Maybe several teams have worked on the same product. Maybe the architecture grew without a clear direction. Maybe development is getting slower. Maybe engineers disagree about what should happen next.
Maybe a founder has a product but cannot tell whether the technology underneath it is actually good. Or maybe the company has simply outgrown the decisions that made perfect sense when the first version was built.
Those are the problems Tamim naturally gravitates toward.
He enjoys understanding complicated systems, finding the underlying issue, and turning technical uncertainty into a direction people can actually act on.
Sometimes that means architecture. Sometimes leadership. Sometimes restructuring a system. Sometimes simplifying it.
And sometimes the best technical decision is deciding not to build something at all.
Building ReemRose
ReemRose grew naturally out of Tamim Abbas Aljuratli's engineering career.
Before ReemRose became a company, Tamim was already spending years building increasingly complex products for clients and working beyond the boundaries of traditional software development.
Projects that started with development gradually became conversations about architecture, infrastructure, performance, integrations, product decisions, engineering teams, and long-term technical direction.
The work had changed.
Clients were not only asking Tamim to build software anymore.
They were relying on him to help decide what should be built, how it should be designed, and what technical decisions made sense for the business behind it.
ReemRose became the natural home for that kind of work.
Today, Tamim Abbas Aljuratli is the Founder and Systems Architect of ReemRose, a software engineering company operating across the United States and Dubai, United Arab Emirates.
An International Background & Mission
Tamim Abbas Aljuratli has a Syrian-Spanish background, and his personal and professional life has always crossed borders.
He speaks Arabic, English, Spanish, and Catalan and has spent much of his career working with international companies, clients, and engineering teams.
Today, Tamim is based in Dubai, United Arab Emirates, while ReemRose operates across both Dubai and the United States.
That international background has influenced the way he works. Different cultures communicate differently. Different companies make decisions differently. Different markets can look at the same problem in completely different ways.
Tamim's mission is not to build as much software as possible.
It is to help build better technology, better products, and stronger engineering organizations.
He wants founders to understand the technology behind their businesses, engineers to have enough context to make good decisions, and architecture to solve problems rather than become one.
After more than a decade working in technology, the part he values most is being able to look at a difficult technical situation, understand what is actually happening, and help people decide what should happen next.
What Defines Tamim?
Engineering
Understand the whole system, not only the code in front of you.
Judgment
Knowing what not to build can be as important as knowing how to build it.
Leadership
Give people context, ownership, and a reason behind the work.