Loading your next page…
Loading your next page…
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.
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.
Async briefs, recorded demos, and optional Lahore and Dubai hubs keep deep work protected across time zones.
Monday risk notes, Wednesday pairing blocks, Friday demos, and monthly incident-reading circles.
Practice guilds, conference budgets, internal architecture reviews, and room to lead client outcomes.
Humane on-call, parental leave, sabbatical paths, health support, and flexible public-holiday swaps.
We evaluate judgment, written communication, code review behavior, and how you make trade-offs visible.
Every role is close to shipped code, measurable outcomes, accessibility, observability, and security hygiene.
We hire for high autonomy, then support it with clear expectations, written context, and room to keep learning.
Work from where you do your best thinking, with optional hubs in Lahore and Dubai for collaboration weeks.
You are paired with experienced engineers and designers, not junior shadow rotations hidden behind a senior pitch.
Annual training and conference support is expected to be used, then shared back through guild notes.
Time-zone-friendly rotations, written runbooks, and compensating recovery time after difficult incidents.
Equity participation in the MayaLogic alumni program for people who help build the firm over time.
Parental leave, sabbatical paths, and flexible public-holiday swaps for long-tenure builders.
“The best part is the absence of theater. If a design is risky or a sprint is overloaded, we say it while it can still be fixed.”
“I joined for senior peers. Code review here feels like a design discussion about behavior, not a hunt for formatting issues.”
“Remote works because decisions are written down. I can do deep work, read the context, and still feel close to the team.”
The common thread is not a specific framework. It is judgment, ownership, and a willingness to make the work easier for everyone around you.
You surface risk while there is still time to act, especially when the answer is unpopular.
You leave tests, runbooks, decisions, and patterns that make the next engineer faster.
You read pull requests for correctness, accessibility, failure modes, and long-term maintainability.
01 · Intro
We discuss your preferred work, time-zone overlap, compensation expectations, and the kind of client problems you want to own.
02 · Work sample
Bring a repository, design case study, incident write-up, or architecture decision. We talk through trade-offs rather than assign homework by default.
03 · Peer panel
Senior engineers and designers evaluate communication, judgment, code review instincts, and how you handle ambiguity.
04 · Offer
If there is a fit, we share team, engagement type, compensation, benefits, and the first ninety days in writing.
Candidates meet the practices we expect daily: written decisions, production thinking, rigorous review, and care for how systems behave after launch.
Architecture records, release notes, and customer trade-offs are captured where the team can challenge them.
We treat accessibility, observability, security checks, and rollback plans as part of done, not launch-week extras.
Pull requests are expected to improve behavior and transfer context, with senior engineers modeling the standard.
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.
Product Engineering
Ship production software end-to-end on TypeScript stacks. You will lead the technical shape of an engagement, mentor mid-level engineers, and own the system in front of the customer.
Platform & DevOps
Set the platform standard across our engagements: golden paths, IaC modules, observability defaults, and the developer experience our delivery teams depend on.
AI & Data
Build production LLM systems for our customers: RAG, agents, evaluation harnesses, guardrails, and the observability that makes them trustworthy.
Product Engineering
Lead native and cross-platform mobile delivery on customer engagements — from architecture and CI to store submission and crash-free release.
Design
Design products that engineers love to build and users return to. Embedded in client teams alongside the engineers who will build the work.
AI & Data
Build the warehouses, lakehouses, pipelines, and semantic layers our customers run their business on — with the testing, lineage, and governance that make them trustworthy.
Not the right role?
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.