How do you begin in an industry when you do not yet know what all the roles involve? Jacob Hansen described entering BIM work without the background he expected someone in that position would have. The opportunity gave him a place to learn, take responsibility, and eventually build Hansen Consulting Group. Our conversation connected that career story with the questions companies face when they introduce reality capture and other tools.
Look for a place to begin learning
Jacob recalled his first role directly: “I didn't even know BIM existed. I didn't know semiconductor facilities existed.” That describes his own starting point rather than a promise about how any particular company will hire. What he brought was a willingness to figure out the work. The role then gave him something specific to learn.
The career takeaway is to investigate an opportunity before deciding you cannot belong in the field. Learn what the work involves and what the organization actually needs. A class, an internship, or time with someone doing the job can help make that investigation practical. The next step should match the responsibilities of the role and the support available for learning it.
See the wider ecosystem of work
The conversation ranged across BIM, VDC, reality capture, and different project settings. Those subjects connect design information, captured conditions, coordination, and the people making decisions. A person may begin with one task and discover other ways their skills can contribute. Understanding those connections helps make a career path more visible than a list of unfamiliar job titles.
The existing takeaways also point beyond construction to other settings where spatial information can be useful. That does not mean every workflow transfers unchanged. Different uses bring different requirements and people who understand the setting. Curiosity about the wider ecosystem gives someone a reason to ask where the information is going and what the next person needs from it.
Understand the outcome before adopting a tool
Jacob described seeing equipment without the surrounding training or workflow needed to make it useful. That is a different problem from deciding whether a device is interesting. The team still needs to know why it is collecting information and what makes the result suitable for use. A purchase cannot answer those questions on its own.
Our discussion included asking what a point cloud should support and what degree of accuracy the intended work needs. Those are project questions that need appropriate expertise. Defining the outcome helps the team compare approaches and recognize which knowledge is missing. It also makes a demonstration more useful when someone tests the path through to the required deliverable.
Collaborate with the people doing the work
Jacob emphasized being present with the people involved in a project. Site conversations can reveal conditions, questions, and constraints that are difficult to understand from a file alone. That gives a technical team a better chance to learn what the information is for. The right arrangement still depends on the role and the work, rather than one rule about where everyone should sit.
He described the human side plainly: “Organizations are inanimate objects, they're built with people. And how we communicate and how we work together is going to solve these problems.” That brings collaboration into the actual delivery process. Who needs to share information, where is a handoff unclear, and what can each person contribute? Those questions make teamwork more specific than simply telling everyone to cooperate.
Turn experimentation into shared knowledge
The final takeaway describes a field where tools and workflows are still developing. That creates room to test approaches, alongside a responsibility to explain what was tested and what happened. A case study becomes more useful when it includes the conditions and limitations of the work. Other people can then decide what might apply to their own project.
Jacob's early experience also shows why support matters when someone takes on an unfamiliar responsibility. Trust can create room to grow, while feedback helps a learner understand what needs to improve. The goal is a useful result and knowledge the team can build on. Sharing that learning gives the next person a better starting point than asking them to repeat the same uncertainty alone.
Hear the full conversation, Breaking Into the Fastest Growing Space in Construction | BIM, VDC & Reality Capture with Jacob Hansen, on YouTube, Apple Podcasts, or Spotify. We discuss his route into the work, building a business, and the people behind technology adoption.