BIM Manager

Before judging candidates, define the problem the hire needs to solve. A Part II assistant, project architect, senior architect and BIM coordinator may all need Revit, but the responsibilities differ. Clarify project stage, responsibility level, sector, communication demands, and pace or structure of the studio. Hiring is rarely only technical ability — project stage, communication style and team environment matter alongside software and sector.

A BIM portfolio should prove how you use information, not just that you can open Revit. Practices want technical judgement, modelling habits, coordination experience and clear communication of project information. Strong evidence combines project context, model examples, drawing outputs, coordination evidence and a clear explanation of your role — including stage, software and responsibility.

For BIM coordinator roles, show standards, coordination and process. For architectural assistant roles, show how BIM supports design and delivery. For technical roles, show details, packages and accuracy. The portfolio should match the job — a design-heavy practice may not need the same evidence as a technical delivery team.

Software screenshots without project context are hard to assess. Add captions that explain the problem, the task and the outcome. A stronger example: Revit model and drawing package for a residential planning submission. Role: updated model geometry, coordinated drawing revisions and produced GA sheets under the project architect's direction.

For BIM coordinator and technical roles, practices want coordination evidence — clash awareness, consultant information and process — not only that you can open a model. A BIM portfolio should combine project context, model examples, drawing outputs and a clear explanation of your role. Match the evidence to the job: coordination-heavy roles need standards and communication, not screenshots alone.