MayaLogic
Careers

Senior engineers, paired with senior engineers.

MayaLogic is a small, senior team. We hire builders who would happily be hired onto our clients’ teams — and we treat the bar that way.

A distributed, remote-first MayaLogic team
Engineers in a deep-work session
The MayaLogic studio in Lahore
Life at MayaLogic

Senior work, sustainable pace, visible standards.

The employer promise is simple: fewer ceremonies, stronger peers, clearer writing, and benefits that respect people who want to do this for a long time.

Remote-first, not remote-forgotten

Async briefs, recorded demos, and optional Lahore and Dubai hubs keep deep work protected across time zones.

Rituals that improve the work

Monday risk notes, Wednesday pairing blocks, Friday demos, and monthly incident-reading circles.

Growth with senior peers

Practice guilds, conference budgets, internal architecture reviews, and room to lead client outcomes.

Benefits for long-tenure builders

Humane on-call, parental leave, sabbatical paths, health support, and flexible public-holiday swaps.

A high hiring bar

We evaluate judgement, written communication, code review behaviour, and how you make trade-offs visible.

Engineering proof over theatre

Every role is close to shipped code, measurable outcomes, accessibility, observability, and security hygiene.

Benefits and ways of working

Built for distributed builders.

We hire for high autonomy, then support it with clear expectations, written context, and room to keep learning.

Remote-first

Work from where you do your best thinking, with optional hubs in Lahore and Dubai for collaboration weeks.

Senior peers

You are paired with experienced engineers and designers, not junior shadow rotations hidden behind a senior pitch.

Learning budget

Annual training and conference support is expected to be used, then shared back through guild notes.

Humane on-call

Time-zone-friendly rotations, written runbooks, and compensating recovery time after difficult incidents.

Alumni upside

Equity participation in the MayaLogic alumni programme for people who help build the firm over time.

Life-stage support

Parental leave, sabbatical paths, and flexible public-holiday swaps for long-tenure builders.

From the team

What the work feels like from the inside.

The best part is the absence of theatre. If a design is risky or a sprint is overloaded, we say it while it can still be fixed.
Sara MalikSenior Product Designer · MayaLogic
I joined for senior peers. Code review here feels like a design discussion about behaviour, not a hunt for formatting issues.
Hassan ReedStaff Engineer · MayaLogic
Remote works because decisions are written down. I can do deep work, read the context, and still feel close to the team.
Priya NairPlatform Engineer · MayaLogic
Success here

What makes someone thrive at MayaLogic.

The common thread is not a specific framework. It is judgement, ownership, and a willingness to make the work easier for everyone around you.

You communicate early

You surface risk while there is still time to act, especially when the answer is unpopular.

You optimise for ownership

You leave tests, runbooks, decisions, and patterns that make the next engineer faster.

You review for behaviour

You read pull requests for correctness, accessibility, failure modes, and long-term maintainability.

Interview process

A transparent process with senior peers.

  1. 01 · Intro

    A practical conversation

    We discuss your preferred work, time-zone overlap, compensation expectations, and the kind of client problems you want to own.

  2. 02 · Work sample

    Review something real

    Bring a repository, design case study, incident write-up, or architecture decision. We talk through trade-offs rather than assign homework by default.

  3. 03 · Peer panel

    Meet future collaborators

    Senior engineers and designers evaluate communication, judgement, code review instincts, and how you handle ambiguity.

  4. 04 · Offer

    Clear role shape

    If there is a fit, we share team, engagement type, compensation, benefits, and the first ninety days in writing.

Engineering culture proof

The bar is visible before you join.

Candidates meet the practices we expect daily: written decisions, production thinking, rigorous review, and care for how systems behave after launch.

Written decisions

Architecture records, release notes, and customer trade-offs are captured where the team can challenge them.

Production readiness

We treat accessibility, observability, security checks, and rollback plans as part of done, not launch-week extras.

Review as mentorship

Pull requests are expected to improve behaviour and transfer context, with senior engineers modelling the standard.

Open roles

Currently hiring.

Do not see your role? Send a note via the contact form — we keep an interest list for senior builders we would love to work with.

Not the right role?

Tell us who you are anyway.

We keep an interest list for senior builders we would love to work with. Drop a note via the contact form and we will be in touch when a fit opens up.

Careers at MayaLogic