Senior Software Engineer in Amman, Jordan, with 9+ years across mobile and backend engineering. Primary focus on Flutter and Node.js — mobile architecture, RESTful APIs, authentication, payments, Firebase and real-time features — while guiding cross-functional delivery and staying hands-on in the codebase.
Three selected case studies — what the product does, the part I owned, and the engineering problems that had to be solved to ship it.
A Flutter mobile platform delivering one product experience on iOS and Android, built on independently testable feature modules with shared state, offline-tolerant data flow and a single design language.
A mobile backup application that moves user data to cloud storage with resumable transfers, scoped permissions and a restore flow that stays verifiable when it is interrupted.
A smart clinic management system used privately by clinic employees — appointments and scheduling, doctor and patient records, lab results, imaging and medical reports, behind role-based access. Bilingual Arabic and English, on web and mobile.
Each step added a layer rather than replacing one. Select a stage to see what it contributed.
Started server-side: REST APIs, relational schemas, background jobs and the deployment plumbing around them.
This is where the habits came from — modelling data before writing screens, treating failure as a normal path, and reading logs instead of guessing.
Shipping production apps on Flutter and native, from architecture through store release.
Designing the services and data models the clients depend on, and keeping them observable.
Modular systems, versioned SDKs and pipelines that make releases uneventful.
Setting technical direction, growing engineers, and being present when production breaks.
I'm Bashar Al-Najjar, a Senior Software Engineer based in Amman, working across mobile and backend. I began on the backend, moved into native Android and then iOS, consolidated onto Flutter, and now lead the teams that deliver across all of it. What carried through every step is a preference for systems that are simple to reason about: clear boundaries, small interfaces, and code a new engineer can read on their first week.
I still write code every week. Leadership without hands-on context turns into guesswork, and guesswork is expensive once something is in production.
Architecture choices get a short written rationale, so the team inherits the reasoning and not only the result.
Code review is the highest-leverage teaching moment there is — I use it that way rather than as a checkpoint.
Most delivery risk lives between mobile, backend, QA and DevOps. I keep those handoffs explicit and unglamorous.
When production breaks, I'm in the logs with the team — then we fix the class of problem, not just the instance.
Leading a cross-functional group of 10+ engineers spanning mobile, backend, QA, databases and DevOps: technical direction, delivery planning and production ownership.
Flutter applications published to both stores, built on modular feature architecture with shared design systems and automated release pipelines.
Android and iOS applications and a distributed native SDK — background execution, mapping, offline data and versioned public APIs.
REST services, data modelling across SQL and NoSQL stores, and the integration layer that keeps mobile clients honest about failure.
Happy to talk through mobile platform work, SDK design, or leading a delivery team. Based in Amman, working with distributed teams.
Full engineering history, technologies and leadership scope, as a PDF.
Download CV ↓