Finding Your Equipment Engineering Role at FLSmidth: What Works Depends on Where You Are

There Is No One-Size-Fits-All Path Into a Global OEM

I've been involved in recruiting for my team at FLSmidth on and off for the last four years. Not as an HR person—I'm an applications engineer who got roped into helping screen candidates for our minerals processing division. In that time, I've reviewed about 250 resumes, conducted maybe 60 interviews, and made some spectacularly bad judgments about who would fit.

Take my word for it? Don't. The first time I picked a candidate, I went purely on the strength of their academic pedigree. PhD from a top school, three publications on froth flotation dynamics. Sounded perfect. He quit after eight weeks. Said the job was 'too operational.' I'd missed the most basic question: does this person actually want to work with equipment, or just model it?

That $3,200 mistake (recruiter fees, lost time, re-advertising) taught me a lesson I've since formalized into a checklist. The thing is, the answer to 'how do I get a role at FLSmidth' or any similar OEM depends almost entirely on where you are in your career. The advice for a junior process engineer is nearly the opposite of what works for a seasoned plant manager making a pivot.

Let me break it into three common scenarios I've seen work—and fail.

Scenario A: The Early-Career Specialist (2–5 Years Experience)

You've got a couple of years under your belt, probably in an operating mine or a consulting firm. You understand the theory of how a SAG mill works, but you've never had to spec one for a greenfield project. Your resume lists 'participated in' and 'assisted with' more than 'led' or 'designed.'

This is the group I've seen struggle most, because they often aim too high. They apply for 'Senior Process Engineer' roles at FLSmidth thinking their two years of plant optimization experience translates. It doesn't. The senior roles require demonstrated ownership of a full equipment selection process, including the political fight to justify the capex.

What actually works for this group?

Target the 'Associate' or 'Graduate' roles explicitly. I know it feels like a step back, especially if you're coming from a site where you had real responsibility. But inside a global OEM, the learning curve for the commercial side—how we structure a proposal, how we manage warranty risk, how we navigate international logistics—is steep. You will be more productive and more valued in 18 months if you start in a role designed to teach you that.

"It took me about 150 applications across different OEMs to realize the 'Senior' title was a trap. The one I finally accepted was an 'Applications Engineer I' slot at FLSmidth. I'm now a III, and I make more than the guy who hired me. Starting a rung lower let me learn the game before I had to win it."

I'd argue that the single most important thing you can do at this stage is be relentlessly specific about what you worked on. Don't say 'I optimized a grinding circuit.' Say 'I conducted a power draw audit on a 26-foot SAG mill and recommended a 12% ball charge increase, which improved throughput by 4%.' The hiring manager (often me or someone like me) needs to see that you understand cause and effect in an equipment context, not just that you were present.

Scenario B: The Mid-Career Operator Turned Engineer (6–12 Years)

This is the sweet spot, and honestly, where most of my team's best hires have come from. You've run the plant. You've dealt with a crusher that seized up on a Sunday afternoon. You know what happens when a flotation cell froth overflows into the walkway (it's slippery, it's messy, and the maintenance team will hate you).

Your risk here is different: you're prone to underestimating the value of your operational knowledge. I've interviewed candidates who could troubleshoot a cyclone cluster in their sleep but couldn't articulate how that experience would help them design a better hydrocyclone manifold. To be fair, I made this mistake myself when I first moved from site to OEM.

What works: frame your operational experience as design intelligence. You don't just 'know how pumps fail'—you know the specific failure modes (cavitation, seal wear, bearing overheating) that should drive the material selection and maintenance access design in a new pumping system. You have a mental database of 'things that broke' that a purely academic engineer doesn't.

I'm not saying you should disregard technical certifications. But when I look at a resume from a mid-career candidate, I'm scanning for evidence of pattern recognition, not just credentials. A PMP is fine. A story about how you redesigned a chute to prevent blockages based on observing three different ore types is gold.

One practical tip: In your interview, don't wait to be asked about your plant experience. Lead with a specific failure or improvement. Say something like, 'In 2022, we had a recurring issue with apron feeder chain breakage. After analyzing the wear patterns, I realized the issue was misalignment in the head sprocket, not the chain quality. That experience directly informs how I think about preventive maintenance schedules now.' That's the language that gets you hired.

Scenario C: The Senior Decision Maker or Pivot Candidate (12+ Years)

This is the trickiest group. You might be a plant manager looking to move into a vendor role, or a senior consultant wanting to go in-house. You have deep credibility in one domain—say, process design for gold recovery—but limited exposure to the commercial realities of selling capital equipment.

I've seen two distinct paths here, and only one works consistently.

The path that fails: Trying to enter at a Director or VP level immediately. You have the gravitas, but you don't have the internal network or the specific knowledge of FLSmidth's product portfolio and pricing strategies. You'll be fighting fires without knowing where the extinguishers are. I've seen three senior hires fail this way in the past five years, each costing the company roughly $25,000 in lost productivity and severance.

The path that works: Coming in as a 'Principal Engineer' or 'Senior Technical Advisor'—a role that leverages your expertise without requiring you to manage a P&L on day one. This gives you 12–18 months to learn the machinery of the business (literally and figuratively) before you're expected to lead a team or drive a sales strategy. It's a smaller title but a faster trajectory.

I've seen this work exceptionally well for someone who had spent 15 years managing bulk material handling systems at a major copper mine. He joined FLSmidth as a Senior Advisor for conveyor systems. Within two years, he'd reshaped our entire approach to overland conveyor quotations—not because he was a great salesperson, but because he knew exactly which design parameters actually mattered to the end user. He's now a Director.

If you're in this scenario, I'll be blunt: your resume needs to be less about your responsibilities and more about the commercial judgment you developed. Did you choose one vendor over another? Why? What was the cost-benefit trade-off you made on a major equipment purchase? If you can't answer those questions in an interview, you're not ready for the move.

How to Figure Out Which Scenario You're In

I've given you three frameworks. Now, how do you know which one applies to you?

Ask yourself honestly: What am I afraid of in this transition?

• If you're afraid of being 'bored' by the slower pace of an OEM office versus a mine site: You're probably Scenario B or C. Focus on roles that emphasize field support or commissioning travel, not just desk-based proposal work.
• If you're afraid you don't have the 'technical depth' to compete with PhDs and design engineers: You're likely Scenario A. Target the associate-level pipeline and accept that your first year will be heavy on learning, not leading.
• If you're afraid of taking a step down in title or salary to make the move: You're probably in Scenario C. You need to decide if the long-term career arc in a global OEM justifies the short-term compromise. For most people I've seen, it does—but not overnight.

I can't tell you the 'right' answer because I don't know your risk tolerance or your financial situation. But I can tell you the common blind spot: engineers overestimate the importance of technical knowledge and underestimate the importance of commercial and operational context. A PhD in flotation chemistry is valuable. Knowing that a plant manager will never buy a $500,000 cell if the maintenance team can't access the impeller with their existing crane is more valuable.

In my experience, the candidates who succeed at FLSmidth—whether they come from site, consulting, or university—are the ones who view equipment not as isolated machines, but as parts of a system that someone has to pay for, install, operate, and fix. If you can show you understand that system, there's a place for you.