About
Najeeb Said
I build production React Native mobile apps, Next.js web applications, and Node/PostgreSQL backends.
Now
Based in Swat, Pakistan. Full-stack engineering at Learnsignal (schema design, access control, and billing infrastructure for an LMS) and lead mobile engineering at SwipeTech (Dubai Daily Deals).
The path
COMSATS · 2020 – 2024
A software engineering degree, and the habit of shipping things classmates actually used. The one that mattered: CUI-ATD-Companion, a timetable scraper and offline-first React Native app that served students at my university for eighteen months — my first real users, and six hosting migrations on a student budget. Before that direction settled, I built the same inventory system three times — JavaFX, PHP, then React Native and Firebase — to see how the problem changed shape with the stack.
Sparking Asia · 2024 – 2025
First lead role. I architected DIFM, a multi-tenant CMS and site builder, across three tiers — an AdonisJS API, a React admin portal with a visual page editor, and a Next.js storefront — and refactored its routing from wildcard subdomains to path-based URLs so tenant sites stopped diluting the domain's search authority. The lesson was as much about users as code: the editors were non-technical staff, so every design had to survive someone who will never read documentation.
SwipeTech · 2024 – present
Primary engineer on Dubai Daily Deals, a consumer React Native app, since August 2024. Two years of owning one production codebase end to end — including a React Native 0.73 to 0.84 New Architecture migration executed solo across four revert-friendly sessions. Maintaining one app for years teaches what greenfield work cannot.
Bell Partners · 2025 – 2026
Backend and data work for music-industry platforms: rebuilding ArtistServe from an AWS AppSync/GraphQL stack to a Node/Express REST API over PostgreSQL with a zero-downtime dual-write cutover, and migrating 8.4 million historical records out of DynamoDB into a star-schema warehouse with materialized views. This is where I learned to respect rate limits, memory ceilings, and other people's APIs — the failures all lived at the boundaries.
Learnsignal · 2026 – present
Lead full-stack engineer on an LMS for accounting students. I architected the Supabase/PostgreSQL schema — 60 tables, over 200 row-level-security policies — rebuilt the Stripe billing integration around advisory locks for gapless invoicing, and built an exam-grading pipeline on Claude's batch API with a human-escalation gate. An education platform tolerates no billing errors and no lost coursework; correctness is the product.
What I'm good at
Read the case studies in sequence and one discipline repeats: systems that stay correct when conditions are bad. Offline clinics syncing over intermittent connections, deep links surviving auth walls, invoice numbers staying gapless under concurrent checkout, workers backing off instead of getting banned, storage engines recovering from power loss mid-write. That is the work I am best at, and the work I go looking for.
When I want to understand something properly, I build it from first principles. That is where the Rust storage engine projects came from — understanding page layouts, write-ahead logs, and crash recovery by implementing them directly. Two of them are public: PithKV and Cura.
Common questions
What does Najeeb Said specialise in?
Production React Native mobile apps, Next.js web applications, and Node/PostgreSQL backends — with a particular focus on software that behaves correctly under bad conditions: offline operation, poor networks, concurrent writes, and crash recovery.
What is Najeeb Said working on now?
Full-stack engineering at Learnsignal — schema design, access control, and billing infrastructure for an LMS — and lead mobile engineering at SwipeTech on Dubai Daily Deals. Based in Swat, Pakistan (UTC+5).
Where can I see his code?
PithKV, a crash-safe key-value store in Rust, and Cura, an offline-first clinic desktop app in Tauri, are both public on GitHub — along with git-identity-sync, a small tool that keeps git identity in step with the active GitHub account. Client work stays in private repositories, but every project has a written case study on this site covering the problem, the decisions, and the outcome.
Contact
Reach out for technical inquiries, engineering projects, or technical collaboration.