Built environment technology can be a serious route for people from architecture, BIM, information management and construction. The work is still about buildings, clients and project information, but the day-to-day environment can feel very different from practice.
This Glider Tech conversation is useful because it shows what a digital built environment company actually needs: people who understand project reality and can help technology solve real industry problems.
Watch: Glider Tech on built environment technology
Glider Tech talks with Stephen Drew about working in a digital built environment company and how architecture experience can translate into technology roles.
What transfers from architecture
- Understanding how project information is created and used.
- Knowing where clients, consultants and contractors struggle.
- Explaining complex technical ideas clearly.
- Spotting the gap between a tool’s promise and a project’s reality.
What may feel different
Technology companies often move faster, measure work differently and rely on cross-functional teams. You may work with product, sales, customer success, data, implementation and support colleagues, not only designers and technicians.
That can be refreshing, but it also means you need to be clear about why your architecture background helps the business, not just why you want a change.
Check your transfer story
Before applying for a tech-side role, make the link between your experience and the company’s problems obvious.
- Name the built environment users you understand.
- Explain the information problems you have seen first-hand.
- Show examples of training, coordination, implementation or client support.
- Translate practice language into product and business language.
Next step
Watch the video, then rewrite your profile summary for a technology audience. If it only says you want to move into tech, it is not specific enough.
Add a comment