Senior engineers deal with EFT a lot in mid/junior and even some seemingly seniors who just absolutely abdicate responsibility for anything that is not interesting.
A common example - asking for help debugging by basically just saying "it doesn't work", requiring you to interrogate them with 10 questions before you get to the what/where/why/when/how of "it" and "doesn't work" to actually begin helping them. Helping them causes you more work than necessary because they can't be bothered to write up a decent 2 sentence explanation up front.
Another example - always doing half (at best) of the task, arguably leaving things in a worse state. In a data engineering context, things like making a change in some mappings in your data loader, but only fixing it on new data, leaving old data in a broken state. So now downstream users of the dataset need to be aware of the old bad mapping, the new good mapping, and either the date of cutover/handle both cases. They saved themselves some work, but caused everyone else more work.
The last class I would mention would be coworkers who are basically "prototype devs". Guys, (its always guys) who are fairly creative and fast moving, delivering interesting IDEAS that they are incapable of productionising. These guys are incredibly dangerous to the team if not managed well, as they get ahead of their skis offering products to management that they can't get past the toy stage. The rest of the team is left to write the other 90% of the code, or usually do a full rewrite. As it turns out the toy always takes 1/10th the time of the real solution, and so they have plenty of time to run off and build more toys.
I'd also describe EFT as leaving you feeling like you've lost agency and control of your day.