Two engineers.
One focus.
We started Jabbar because we kept seeing the same problem: research teams with genuinely important work, held back by software that wasn't built for the way they think.
Built on academic ground.
We met while working at the University of British Columbia, where we spent time embedded with research teams - watching talented scientists lose weeks to broken workflows, missing tools, and software that generic enterprise vendors couldn't or wouldn't tailor to academic use.
Between us we've worked at Amazon, PPI, and directly within university research environments. That combination - industry-grade engineering discipline applied to the specific constraints of academic work - is what makes Jabbar different from a typical agency.
We stay deliberately small. Two engineers, working closely with each client, is how we maintain the quality and focus that boutique research projects demand.
Meet the founders
Navid Samiei
Navid has worked on large-scale data systems and consumer-facing platforms at PPI, and collaborated with research teams on computational tooling at UBC. His time embedded in the university gave him a clear-eyed view of the gap between what generic software offers and what researchers actually need.
LinkedIn
Partheeban Bharati
Partheeban has built production systems at Amazon and worked closely with academic research groups at UBC. His background spans fullstack development and infrastructure, and his time inside the university gave him a genuine appreciation for the workflows and constraints that make research software uniquely challenging.
LinkedInOur values
Precision over speed
We take the time to understand the problem before writing a line of code. Misunderstood requirements cost far more to fix than they do to get right the first time.
Respect for domain expertise
We are engineers, not researchers. We bring technical knowledge; you bring domain knowledge. The best work happens when we treat both as essential.
Longevity as a design constraint
Software that only works while the original developer is around isn't finished. We write for the next person - the grad student, the post-doc, the IT admin inheriting the project.
Honest scoping
We'd rather scope a project down to what's achievable and deliver it excellently than overpromise and underdeliver. If something isn't feasible in your timeline or budget, we'll tell you upfront.
Ethics by default
Academic research involves human participants, sensitive data, and public trust. We take data handling, consent, and privacy seriously - not as compliance checkboxes but as design principles.
Small by choice
Staying a two-person shop is deliberate. It means every client gets senior-level attention, every decision goes through the people who understand the project, and nothing falls through the cracks.