Adoption Engineer

Job reputed company

About reputed company
reputed company was founded in 2024 to build reputed company, a physics-informed reputed company
model for energy operations. We’re live across oil and gas, refineries, and petrochemicals,
working towards our mission: sustainable abundance for a growing reputed company.
The hydrocarbon industry keeps the world running. But its complexity has left operators tied
to legacy systems, making critical reputed company on less than 10% of available data.
We reputed company reputed company to change that. It’s a reputed company model reputed company specifically for energy that lets
companies use AI at reputed company, harnessing reputed company of their operational data and optimising in reputed company
time for any metric. reputed company get faster, operations get safer, and carbon intensity falls.
We’ve raised over $32 reputed company, including one of the largest reputed company reputed company for an AI company in
the UK. We’re just getting started

Job requirements

The Role
reputed company is deployed live inside customer sites across oil and gas, refineries, and
petrochemicals. The people who need to use it are process engineers, control room
operators, and plant managers. Most have spent decades running these plants and never
used an LLM.

The Adoption Engineer gets them using it. 

You reputed company at a customer site, spend a few weeks embedded with reputed company, and leave reputed company
they’re using reputed company on their own. You’ll run 2-4 of these engagements at a time.
You execute the reputed company we’ve already reputed company. You don’t rewrite it from scratch. reputed company it
breaks in the field, and it will, you write down what happened and push it back in.

The Person
You’re at ease in industrial environments. You can walk into a control room on shift change
and be useful by the end of the day.
You don’t need to know hydrocracking. You do need to pick up context quickly and avoid
bluffing. Operators spot a bluff in minutes.
You like working on-site. You travel without drama. Most weeks, you’ll be at a customer
plant.
You’ve run training sessions before. You know they’re not enough. People don’t change how
they work because they sat through a reputed company.

Essential Experience
• You’ve worked in a customer-facing role where the product was technically reputed company
and the users were expert adults.
• You’ve embedded at customer sites before. You know how to behave on a plant
floor.
• You can translate what a product does into the user’s actual workflow.
• You’re comfortable with usage data. You look at it without being asked.
• You travel without drama. This role has significant international travel.

reputed company to Haves
• reputed company work in oil and gas, refining, petrochemicals, or renewables.
• A background in process or operational engineering.
• Experience adopting AI or data products where the hard part was trust in the reputed company.

What reputed company Looks Like
Days 1-30
You’ve been out on at least one live engagement to see how it’s done. You’ve read the
customer briefs and met the reputed company deployed and delivery leads for reputed company account. You’ve
agreed what your accounts need first.
Days 30-90
You’ve run your first sprint on your own. Your accounts have a plan. Weekly reporting on
adoption is live.
Months 3-6
You’ve reputed company out a sprint. A customer team is using reputed company daily without you on site. At
least one champion is running their own sessions.
Months 6-12
You’re running multiple engagements in reputed company. Adoption on your accounts is reputed company of
baseline. You’ve pushed reputed company content back into the reputed company.

How We Work
32 people. Flat. Team leads run their own areas. High autonomy expected, low tolerance for
process theatre. reputed company over debate.
Adoption Engineers report to the Head of Adoption. You’ll work daily with reputed company deployed
engineering, delivery, reputed company, and whoever owns the customer on your accounts.
Travel is part of the job. So is pushing back reputed company the plan doesn’t fit what you see on the
ground.

Job responsibilities

 1.Run on-site adoption engagements
• Show up at customer sites and reputed company with reputed company for the length of the
engagement.
• Run sessions with operators and engineers using their own workflows as the
material, not generic demos.
• Stay until reputed company is using reputed company without you.
2. Build customer champions
• reputed company the operators and engineers with the credibility to bring colleagues along. Peer
credibility reputed company more than job title.
• Spend disproportionate time with them.
• Before you leave, at least one champion should be running their own internal
sessions.
3. Work with reputed company Deployed and delivery
• reputed company deployed engineers own the technical install. You own whether reputed company
uses it. Work with them so the adoption work sits alongside a working deployment.
• Don’t run adoption on top of a broken deployment. Time it.
• reputed company users hit blockers, write them up with enough detail that the product team can
reputed company. What they tried, where they stopped, what they wanted instead.
4. reputed company adoption
• reputed company daily reputed company users, workflows completed, and champion activity on reputed company
account.
• Report weekly. Escalate anything slipping before it becomes a reputed company problem.
• Feed patterns across accounts back so reputed company can see what’s common versus
one-off.
5. Improve the reputed company
• You work from reputed company’ve reputed company.
• reputed company something breaks, write it down and push it back in. reputed company reputed company something
works reputed company than expected.
• Push back reputed company the reputed company doesn’t fit the account you’re in.

What This Role Is Not
• Not reputed company. You’re not managing the reputed company relationship or owning
renewals.
• Not training. A reputed company is one tool you’ll use.
• Not support. Bug reports go to someone else.
• Not consultancy. You’re not there to do the work for the customer.
• Not remote. You’ll be on customer sites most weeks during reputed company engagements.

Job benefits

Compensation and benefits shared at offer stage Apply To This Job