Amina Qureshi
Founder & Principal Engineer
Shapes the first architecture decisions and keeps delivery teams honest about production risk.
About MayaLogic
A senior engineering team that ships real software, not slideware.
We started MayaLogic because we wanted to work on real problems with serious teams — and we wanted to do it without the overhead, jargon, and theatre that the consulting industry is famous for.
Founded
Engineers & designers
Products shipped
Continents served
Our story
Built by engineers who got tired of broken software.
MayaLogic was founded by a small group of engineers and product designers who had spent the previous decade inside fast-growing startups, banks, and enterprise IT departments. We had seen the same pattern repeat: ambitious roadmaps, capable people, and software that quietly failed to live up to either.
We started the firm with a simple bet: that a small, senior, opinionated team — paid to care about the outcome rather than the hours — could outperform a much larger one. Six years and more than a hundred products later, that bet has held.
Today we are a team of more than sixty engineers, designers, data scientists, and SREs working with clients on four continents — from seed-stage founders to publicly listed enterprises modernising their software estate.
Meet the technical leads
Founder-minded operators, not anonymous capacity.
Every engagement has visible technical leadership from people who have shipped, operated, and modernised systems under real constraints.
Daniel Mercer
Technical Director, Cloud & Platform
Turns fragile infrastructure into secure, observable platforms that client teams can own.
Nadia Farooq
Head of Product Design
Connects research, accessibility, and design systems so products feel coherent after launch.
Omar Siddiqui
AI & Data Practice Lead
Builds evaluated AI systems where retrieval quality, cost, and user trust are measurable.
Mission
Help ambitious teams ship software that earns trust — software that is fast, accessible, observable, and a pleasure for the next engineer to work on.
Vision
A world where the default outcome of a software engagement is a team that ships, not a deck that explains why they did not.
How we work
Small senior teams. Weekly working demos. Code and infrastructure you own from day one. No surprises in the invoice or the runbook.
How we staff engagements
Small teams with clear ownership.
We do not sell blended squads. We assemble named specialists around the outcome, then make responsibilities explicit from discovery through handover.
Technical Lead
Owns architecture, delivery risk, stakeholder trade-offs, and the final engineering bar for the engagement.
Senior Engineers
Ship production code, write tests, instrument the system, and leave patterns the client team can extend.
Product Designer
Runs lightweight research, maps flows, maintains design-system quality, and validates usability every release.
Platform / SRE
Sets CI/CD, cloud, observability, security controls, and runbooks before launch pressure arrives.
Delivery Partner
Keeps scope, decisions, budget, and weekly demos visible without adding project-management theatre.
Client Counterparts
Join reviews, own domain decisions, and receive the system gradually rather than in a final handover.
Values
The non-negotiables.
We will not bend these to win business. They are how we hire and how we decide.
Engineer the truth
We surface bad news the moment we see it. Optimism does not ship features; engineering does.
Senior or not at all
Every engagement is staffed with people who have seen the failure modes before.
Ship continuously
Working software is the unit of progress. Anything else is a leading indicator.
Boringly reliable
We prefer obvious, well-trodden choices and reserve novelty for where it actually pays.
Make the next team’s job easier
Code, infrastructure, and docs are written for the engineer who has not been hired yet.
Earn the next conversation
We grow because clients ask us back. That keeps us honest more than any sales target could.
Culture proof
The habits clients can inspect.
Our culture is not a poster. It shows up in pull requests, incident reviews, architecture notes, and the way a week of work is demonstrated.
Engineering principles
Prefer simple architecture, typed boundaries, automated tests, accessible UI, and observability before cleverness.
Delivery rituals
Weekly working demos, written decision records, risk reviews, and a visible release plan from the first sprint.
Code review expectations
Every meaningful change gets peer review for behaviour, security, performance, readability, and ownership transfer.
Milestones
A visible path from four people to a global delivery team.
2019
Founded in Lahore
Started with four engineers and one product designer working out of a single room above a bookshop.
2021
First enterprise rebuild
Re-platformed a 12-year-old healthcare claims system; cut release cycles from quarterly to weekly.
2022
AI & data practice
Stood up our applied ML practice; first production RAG systems for regulated industries followed within months.
2024
Crossed 100 products
Shipped our 100th product. Client retention crossed 95% on a trailing-twelve-month basis.
2026
A global team of 60+
Engineers and designers across four continents, working with clients from seed-stage to enterprise.
Why clients stay
Retention comes from trust earned in the details.
Long engagements happen because the client keeps getting clearer systems, better decisions, and fewer surprises.
Named senior people stay close to the work instead of disappearing after sales.
Clients see working software, risks, and budget movement every week.
We document trade-offs and hand over code in repositories and cloud accounts they own.
Teams can expand or taper without losing the technical context of the engagement.
“It felt like hiring an engineering leadership team without the equity dilution.”
“They told us what we did not want to hear in week one, and that is exactly why we trusted them by week ten.”
“Documentation, runbooks, code quality — all the things we asked for in the RFP and never expected to actually get.”
Join the team
Want to work with us?
We hire senior engineers, designers, and SREs who care about how software behaves in production.