If a job asks you to train the system, four things worth knowing before you take it

Jobs where part of the work is teaching a machine to do the work are increasingly common, and they are frequently well paid, well trained and interesting. This is not a reason to avoid them. It is a reason to ask better questions at the interview.

Ask what happens to the role when the system is good enough. Not whether it will be, which nobody knows, but what the plan is if it is. An employer who has thought about it will tell you. An employer who has not will change the subject, and that is your answer.

Ask what you are being trained in, and whether it is portable. Advanced driving qualifications, first aid, safety certification: these belong to you and they leave with you. Familiarity with one company's internal system does not.

Look at what the job is called and who else has it. If the role sits in an operations team alongside shift leads and field engineers, it is an operational job with a career ladder in it. If it sits alone, it is a project.

And read the accounts. Any British company files them, free, at Companies House, and we set out how yesterday. A company hiring quickly and paying more each year is telling you something different from a company that is not. Neither tells you your future. Both are better than a press release.

One thing worth holding on to. The person who knows most about where a system still fails is the person watching it fail all day. That knowledge is real, it is scarce, and it is worth naming out loud when you are asked what you bring.