Skip to content
CoreNexes
Team

The engineersbehind CoreNexes.

A small senior team. Every service line has a named lead: the person who scopes your project is the one who builds it, and the one you speak to when something breaks.

  • Mustafa Tariq

    AI Engineer

    Lahore, PK

    Builds the automation and custom model work: retrieval, evaluation harnesses, and the pipeline that has to keep running after the demo. Decides what ships thin and what waits until it can actually be operated.

    • LLM engineering
    • Retrieval and evals
    • Python
    • System architecture

  • Abdul Rehman

    AI Engineer

    Lahore, PK

    Language pipelines end to end: extraction, engine routing, quality estimation, and the release gate at the end of it. Decides where a human still needs to read the output.

    • Localization systems
    • Machine translation
    • Python
    • Cloud architecture

  • Haider

    UI/UX Designer

    Lahore, PK

    Internal tools and the interfaces people sit in all day. Optimises for throughput and for the tenth hour of use, not for the screenshot.

    • Product design
    • Design systems
    • UX research
    • Figma

  • Anees

    Full Stack Developer

    Lahore, PK

    Ships features from schema to CSS, then owns the test automation around them. Treats flake as a defect rather than weather, and builds suites teams still believe on a bad day.

    • TypeScript
    • Next.js
    • Playwright
    • CI/CD
How weoperate

Four working rules.

They shape who we hire and what we agree to build.

Our process

  1. Say no clearly

    If a request falls outside what we do well, we say so and refer it out rather than learning on a client's budget.

  2. Scope small, finish

    One workflow at a time. Engagements fail by widening, and the widening always looks reasonable while it happens.

  3. Leave nothing locked

    Source, deployment and documentation transfer at handover. A client should be able to fire us without losing anything.

  4. Write it down

    Definitions of done, runbooks, failure modes. If it only exists in someone's head, it does not survive their holiday.

Starthere

Tell us the process,not the solution.

The most useful first message describes what someone on your team does by hand today and how often. That is enough for us to tell you whether it is worth building.

What happens next
  • A named engineer reads it, not a form inbox
  • Reply within 24 hours, even if we're not the right fit
  • A 30-minute call to trace the process end to end
  • A fixed-scope quote, or an honest no
Book a discovery callinfo@corenexes.com