Small senior teams. Fortune 500 problems. No twelve-layer hierarchy between you and the client. At DataOps, the people who scope the work are the people who deliver it, and you'll be one of them.
We stay small on purpose. That means real ownership, direct client relationships, and work that ships. The bench we've built comes from ex-Big 4, big tech, and enterprise consulting backgrounds, people who've delivered for firms like PwC, EY, Microsoft, Honeywell Aerospace, and ExxonMobil, and chose sharper work over bigger org charts. That's the talent you'll work beside, and the bar we hire to.
You'll work alongside ex-Big 4 and big tech practitioners with decades of enterprise experience. No pyramids, no leverage model, no busywork rolled downhill.
Our engagements run from growth-stage firms to $40B global enterprises: governance platforms, AI architectures, and systems thousands of people rely on.
DQE™ and DG-OS™ were built by people doing client work. What you learn in the field becomes product, and you help shape it.
Every role below is a W2 position, and every role requires U.S. citizenship because our engagements include work subject to U.S. export control regulations. We hire enterprise practitioners: consultants and engineers who have delivered inside large, complicated organizations and want to keep doing it without the org chart. Select any role to read the full posting.
Forward deployed means what it sounds like. You work from inside the client's operation for the length of an engagement, close enough to the people doing the work that you can see where the process actually breaks, then you build the fix in their environment against their real data, their identity model, and their security boundary. Nothing you ship is a demo. This is the role with the shortest distance between a decision and its consequences, and it is the hardest one we hire for.
You build the agent systems that go into production and stay there. Orchestration, tool design, context strategy, memory, and the evaluation discipline that separates a demo which impresses a steering committee from a system a business actually depends on. Our agents run inside enterprises where a wrong answer has a cost, so the engineering standard is high and the guardrails are part of the build, not an afterthought.
Everything else we build sits on the foundation you lay. You move data out of ERPs, MES systems, CRMs, and whatever else a global manufacturer has accumulated over thirty years, land it somewhere durable, model it so people can reason about it, and put quality checks in front of it so problems get caught before anyone downstream inherits them.
An agent with no interface is a science project. You build the products people actually open: the review queues, the consoles, the dashboards, and the workflow applications where a person and a model meet. You own it from the browser to the database, and you build it to enterprise standards for authentication, auditability, and accessibility.
You are the reason a deployment on a Friday is uneventful. You build the environments, pipelines, and observability that let small teams ship into large, regulated enterprises without drama, and you make the security and compliance posture something we can demonstrate rather than assert.
Enterprises do not buy AI they cannot measure. You make quality a number: the datasets, the graders, the regression suites, and the thresholds a release has to clear before it moves. When a client asks how accurate the system is, you are the reason we have an answer with a methodology behind it.
Voice is the least forgiving surface we build on. A hundred milliseconds too slow and the conversation feels wrong; one bad interruption handler and the caller gives up. You own the real-time pipeline end to end, from the carrier to the model and back, and the engineering that makes it feel like talking to someone competent.
Part of our work sits inside the defense industrial base, where the rules about who may see which byte are not negotiable. You define the boundaries, design to them, and make sure the architecture we deliver survives an auditor rather than merely an internal review.
Most transformation programs fail on adoption, not architecture. You own the part that decides it. You build the curricula, run the enablement, and stand in front of the people whose jobs are changing, and you keep going until the new way of working is simply the way they work.
You are the person who finds out how the work actually gets done, which is rarely what the process document says. You map it, quantify it, write the requirements, and stay close enough to the build that what ships is what the business meant.
You decide what gets built next and you defend the decision. Across client engagements and our own products, you hold the line between what a stakeholder asked for and what will actually move the outcome, and you keep the backlog honest enough that the team always knows what matters most this week.
Enterprise software has a low bar and our clients know it. You design past it. Your surfaces carry dense information, uncertain model output, and real consequences, and they still have to feel calm and obvious to someone who has thirty seconds and a decision to make.
We are hiring a Technical Project Manager to own the delivery of enterprise data strategy, implementation, and AI engagements. This is not an administrative PM seat. Our programs are highly technical and highly organized, and you will be the person who keeps them that way: every workstream coordinated, every plan current, every meeting purposeful, and every commitment tracked to done. You will know the data well enough to challenge the team and to represent the work credibly in front of the client.
Forward Deployed Engineer, Agentic AI Engineer (2 openings), Data Engineer, Full Stack Application Developer, Platform / DevOps Engineer, QA / Eval Engineer, Voice / Telephony Engineer, Cybersecurity / ITAR Advisor, Change Management Training Lead, Business Analyst, Product Owner, UI/UX Designer, and Technical Project Manager. Select any role on this page to read the full posting.
Yes to both. Every open role is a W2 position, and every role requires U.S. citizenship because our engagements include work subject to U.S. export control regulations.
A Forward Deployed Engineer works from inside the client's operation for the length of an engagement, maps how the work actually gets done, and builds the fix in the client's own environment against their real data. The role requires delivery experience inside large global enterprises, technical fluency across data, engineering, and AI, and the people skills to be credible with a CIO and with the operators on the same day.
Use the application form on this page, pick the role that fits, and tell us what you build best. There is no twelve-layer hierarchy here: the people who scope the work are the people who deliver it.
The work model is finalized per role during the hiring process. We work from Detroit, New York, and Chicago, and client-facing roles include travel to client sites.
No cover letter theater. Send us who you are, what you've shipped, and which role fits.
