When Priya first walked into our Balewadi center, she'd already spent three years as a site engineer, earning ₹3.8 LPA, and was honest about why she was there: "I'm good at my job, but I don't see how this turns into a better job in five years if I keep doing exactly what I'm doing now." That conversation is one I've had with dozens of site and design engineers, and Priya's path through it is worth laying out in full, because it's repeatable.
The starting point
Priya had a civil engineering diploma and three years of real site experience — reading structural drawings, coordinating with contractors, resolving on-site issues. She had never opened Revit. What she did have, which mattered more than people expect, was a sharp instinct for spotting where designs and site reality didn't match — which is, in essence, the core judgment clash detection is built around.
Month 1-2: Foundation
She started with our Foundation plan, focused on Revit fundamentals. Her site background meant she understood why a beam couldn't simply move, or why a duct needed clearance — concepts some fresher students take longer to internalize. Her challenge was purely software fluency, which came faster than usual specifically because she already had the technical judgment underneath it.
Month 3-4: Structure
This is where things shifted. Moving into Navisworks clash detection and BIM 360 workflow, Priya realized she'd effectively been doing manual, slower versions of this work on-site for years — chasing contractors about clashes that should have been caught on a drawing. Learning to do it systematically, inside a federated model, before construction even started, was — in her words — "the same job I already knew how to do, just three steps earlier and a lot less stressful."
"I used to be the person on-site finding out a duct and a beam were in the same place after the concrete was already poured. Now I find that out on a screen, three months before anyone pours anything."
Month 5 onward: Applying for roles
With a federated model project and a documented clash-resolution log to show — not just a certificate — Priya started interviewing for BIM Coordinator roles. Her site experience turned out to be a genuine advantage in interviews: most candidates with strong Revit/Navisworks skills had never actually been on a construction site, and hiring managers noticed the difference in how she talked about why a clash mattered, not just how to find one.
The outcome
Within roughly 18 months of starting her training, Priya moved from a ₹3.8 LPA Site Engineer role into a ₹7.5 LPA BIM Coordinator position at a mid-sized consultancy working on metro infrastructure coordination. That's roughly a 97% increase in package — not from a job title change alone, but from a genuinely different, higher-value skill set layered on top of experience she already had.
What made this path work
- She didn't try to skip from zero Revit experience straight to "BIM Manager" — she built the coordination layer first.
- She used her existing site judgment as an asset instead of starting completely from scratch.
- She had a real project — not just a certificate — to discuss in interviews.
If you're a working site or design engineer wondering whether a similar switch makes sense for you, our Structure plan is built specifically for this transition. See full details on the Programs page, or read our broader step-by-step career switch guide.
Editorial note: this story reflects a real AECCORE Learn student outcome, with the name and some identifying details changed at the student's request to protect their privacy.
