Join MRE Consulting! We specialize in helping organizations navigate complex business and technology challenges, providing expertise that supports critical operations, strategic initiatives, and end-to-end delivery. Whether overseeing commodity transactions from the trading floor to final delivery or guiding projects from planning through execution, we help clients achieve their goals while managing risk, driving efficiency, and creating lasting business value.
We are different from other big-name consulting firms in that we do not have the typical “up or out” culture. Instead, we empower our employees to explore their own career paths and achieve great things. This also means you will experience merit-based growth driven by your performance and contributions, not politics.
Our team includes market-leading experts with deep experience across industries, technologies, operational processes, and project delivery disciplines. At MRE, we are proud to go the distance with integrity, expertise, and personal commitment.
An engineer who moves fluidly between a product decision, a database schema, and a model’s failure mode, often within the same day. We are not looking for a specialist who dabbles in AI, or a researcher who tolerates the frontend. We need someone who treats the entire stack, model behavior included, as one system they are accountable for end to end.
This role requires comfort with ambiguity that has not yet been broken into tickets. Much of what we build has no established pattern to follow — defining what “correct” looks like is as much a part of the job as implementing it.
-
Building and shipping complete features — UI, API, data layer, and any model or agent logic underneath — without waiting on a handoff
-
Designing and iterating on prompts, evals, and agent workflows, and holding them to the same standard as production code: versioned, tested, and monitored
-
Deciding where logic should live — client, server, or model — and revising those decisions when new evidence warrants it
-
Diagnosing issues that span layers, tracing a UX problem back through the retrieval logic to the schema decision that caused it
-
Working directly with the owner of the product outcome, translating ambiguous goals into working software with minimal handoff
-
Establishing the infrastructure your own work depends on — CI, deployment, observability — rather than waiting on a platform team
-
Production experience across a modern web stack — frontend, backend, and the data layer connecting them — not limited to coursework or personal projects
-
Hands-on experience building with LLMs beyond a single API call: prompt iteration, retrieval, evaluation, or agent orchestration in something that shipped
-
Judgment to distinguish problems that require a model from those that require a well-indexed query
-
Ability to read and debug code you did not architect
-
A record of shipping finished work, not just prototypes that performed well in a demo
-
Clear, precise written communication — you will be explaining technical tradeoffs to people who need the reasoning, not just the conclusion
