Technology & Design Resume Guide
Here, a portfolio link and named software fluency carry more weight than a degree, and a resume without either one is missing what reviewers check first.
What recruiters actually look for
Software fluency named specifically: Revit, Navisworks, AutoCAD Civil 3D, not a generic "CAD/BIM software" line. Real clash detection, coordination, or modeling experience described in concrete terms (how many models federated, how many conflicts resolved, what discipline you coordinated). A portfolio or work sample link, since design-adjacent roles are judged visually more than almost any other category on this site, and a resume without one invites the reviewer to assume there isn't one. Relevant certifications like Autodesk Certified Professional.
How to structure it
Put your portfolio or work-sample link near the top, not buried in a footer. List software fluency by name and by proficiency level rather than a flat list with no distinction between "used it once" and "coordinate models in it daily." One page early career, closer to two once you have multiple real projects and a specific technical specialty to show.
What to leave off
A software list with no indication of actual skill level; naming ten tools you've each opened once reads worse than naming three you're genuinely fluent in. Applying for a design-adjacent role with no portfolio or sample link at all, when one is the standard expectation. And don't describe modeling or data work only in vague terms ("worked with BIM") when you could name the specific software, project type, and outcome instead.
Bullets worth adapting
- Coordinated MEP clash detection in Navisworks across a 40-model federated BIM, resolving 300+ conflicts before construction
- Built and maintained Revit models for a 250,000 sq ft hospital renovation
- Autodesk Certified Professional (Revit)
- Processed drone-captured site survey data into as-built topographic models