01
Clarity before cleverness.
Corrective action on bugs, explicit threats and risks, and strategies that make the next release safer beat one-off hacks that nobody can maintain.
I work where backend contracts, mobile UX, and regulatory context meet -- especially in Saudi Arabia, where payments, ZATCA, and transport platforms each bring their own constraints.
How I got here
Tawfik Ahmmed
Full-stack and mobile engineer at Masar Soft in Riyadh -- Laravel, Flutter, SaaS integrations, and delivery from API design to app store.
I graduated from Dhamar University with a Bachelor's in Computer Science (94%) and have spent the last several years at Masar Soft in Riyadh as both a full-stack developer and a mobile application developer.
Day to day I administer development phases, debug issues, optimize performance, and collaborate with product and design -- from API design and backend web apps to databases, servers, and Flutter clients.
I have hands-on experience linking Flutter applications with multiple payment gateways in the Kingdom, working with third-party libraries, cloud platforms, and requirements that span technical teams and end customers.
I stay current with web and mobile stacks and enjoy seeing a project through from first specification to store release and operations.
01
Corrective action on bugs, explicit threats and risks, and strategies that make the next release safer beat one-off hacks that nobody can maintain.
02
Payments, government platforms, and partner APIs are first-class: they need the same rigor as the user interface.
03
Mobile and web responsiveness, cross-platform behavior, and backend efficiency all affect trust -- especially under real traffic.
04
Working with graphic designers on web design, with product on roadmaps, and with stakeholders on compliance keeps the build aligned with reality.
Map phases of delivery early so scope, dependencies, and risks are visible to the whole team.
Design APIs and data models with evolution in mind -- particularly when external regulators or partners change their interfaces.
Test and debug systematically; treat customer-reported issues as signals about gaps in observability or documentation.
Recommend new product directions when research supports them, while keeping ongoing systems stable.