“Learn Revit” is common career advice. It can be useful and still be wrong for the job you actually want. In a discussion among architects working in the US, some described Revit-heavy commercial teams, while others still used AutoCAD and SketchUp for residential work, alterations or specialist inputs. A software choice is therefore a question about target roles and deliverables, not about winning an argument between programs.
This guide helps you read job advertisements, identify the skill behind a software requirement and build proof that an employer can assess. It does not claim a percentage of all firms using any tool: a reliable count would need a defined sample of current vacancies, deduplication and a published method.
Start with the work, then the tool
Imagine three vacancies. A healthcare team asks for Revit and consultant coordination. A small residential studio asks for AutoCAD, SketchUp and construction details. A design-led studio asks for Rhino and visual communication. All three are architecture jobs. The first priority for each candidate is different.
Write down four things for every advert: project type, stage of work, named deliverables and software. “Revit” beside “issue coordinated construction documents” means more than drawing walls in a tutorial. “Rhino” beside “complex facade studies” means more than making a sculptural form. The employer needs a result within its workflow.
Check the same firm’s portfolio and current openings. A listing may copy a long software wish list even when the hiring team uses only two tools daily. Ask at interview which tool is central to the role, what model or drawing standards the team follows and what a new hire would produce in the first month.
What each common tool tends to signal
Revit and other BIM platforms. The important skill is managing a consistent information model: views, sheets, families or objects, schedules, links and changes across disciplines. A candidate who can explain how they found and resolved a coordination issue shows more than someone who only names the application. Archicad or another BIM system can be relevant in a different practice; transferring concepts may be easier than transferring shortcuts.
AutoCAD and other 2D CAD tools. They remain useful where teams, consultants, client archives or project types depend on DWG workflows. Show clear layering, references, annotation, plotting and a controlled revision. Do not describe 2D work as obsolete simply because you prefer BIM. The architects’ discussion of CAD use illustrates how project type and legacy material affect the choice.
Rhino, Grasshopper and computational workflows. These often point toward form finding, rationalisation, repeated geometry or specialised analysis. Employers may expect you to turn an exploration into a buildable, documented system. A script that only makes a striking image is weaker evidence than one with stated inputs, limits and a way to update the model.
SketchUp, Adobe tools and visualisation software. These can support quick iteration and communication. Hiring teams still need to know whether the output is a concept, a measured model or a final presentation. State which part you produced, what you checked and how it connected to the technical set.
Project information tools. Issue trackers, common data environments, markup tools and spreadsheets may matter as much as modelling software in coordination roles. They show how work moves between people and versions, even when they are absent from a flashy “top ten” list.
How to read a crowded software requirement
Divide every item in a vacancy into four groups:
- Core production: software used daily to make the deliverable.
- Collaboration: platforms used to coordinate files, comments and consultants.
- Presentation: tools used to explain a proposal.
- Optional or aspirational: tools the team would like but may not require.
Look for words such as “required,” “preferred,” “working knowledge” and “experience with.” Then read the responsibilities. If the role is for documentation but the advert lists six rendering tools, documentation quality probably remains the stronger application evidence. Do not assume that “proficient” means expert in every feature. Prepare to describe a task you can complete independently, a task needing review and a task you have never done.
For international applications, translate job titles and project stages carefully. “Architectural assistant,” “designer,” “job captain” and “project architect” are not identical across countries or firms. Software requirements are a clue, not a substitute for checking legal title restrictions and actual responsibilities.
The two-project portfolio test
Choose no more than two projects for each targeted role. On each page, add a small “workflow and contribution” box:
- Brief: What did the team need to produce?
- Your responsibility: Which model, drawing, analysis or presentation did you own?
- Tool: What did you use it for, specifically?
- Check: How did you verify dimensions, consistency or coordination?
- Outcome: What changed in the design or delivery?
Example: “Modelled the ceiling zone in Revit, compared it with the consultant model, recorded three clashes for team review and revised the section after the architect’s decision.” Use that only if it describes your real work. It shows a workflow, not a badge. For a student project, label it as academic and explain the check you performed yourself.
If you are switching from CAD to BIM, include a short comparison: existing 2D drawing, reconstructed model, a schedule or sheet generated from it, and one discrepancy caught during checking. If moving from Revit to a CAD-based studio, show that you can maintain drawing clarity and revision discipline without relying on the model to do it for you.
A focused 30-day learning plan
Week 1: choose a target. Save ten current vacancies for one role and location. Record the core tool, deliverable and stage from each. This is a private decision sample, not a claim about the entire industry. If the results conflict, narrow by firm type.
Week 2: reproduce a small task. Use a permitted project or clearly fictional exercise. Create one sheet, model view, detail or parametric study that matches the target work. Keep it small enough to finish and review.
Week 3: introduce change. Revise a dimension, consultant input or material. Show what breaks, how you detect it and how you update dependent outputs. Real practice is full of revisions; a tutorial completed once does not prove production readiness.
Week 4: document and get feedback. Ask a practitioner or instructor to inspect the deliverable. Record what you fixed. Put a concise process page in your portfolio and practise explaining it in two minutes.
Do not pay for an expensive course merely because a forum says a tool is “the standard.” Use a small trial first, check the target vacancies and compare the course output with the work employers request.
What to say when you lack the exact program
Be honest and specific. “I used Archicad to coordinate model views, schedules and issued sheets; I have not yet produced a live Revit set. Here is a short Revit exercise, and here are the BIM concepts I can transfer” is credible. “I am proficient in all BIM tools” is difficult to defend.
Ask whether the firm trains new hires in its templates and standards. No software certificate can teach an office’s file naming, review process, consultant agreements and project history by itself. A firm that expects immediate flawless production should state that clearly, especially for an entry-level role.
At interview, ask what version and template the team uses, whether consultants exchange native models or exports, and who performs quality control before an issue. These questions help you judge how quickly your current skills could become useful. They also expose a vacancy that lists software without a clear production workflow.
You can browse architecture vacancies on jobs.archi to build your own current sample. Our older software overview for young architects lists tools; this guide shows how to decide which one matters for a specific job search.
FAQ: Is AutoCAD still worth learning?
It can be, if your target practice uses it for measured drawings, details, legacy files or consultant exchange. Verify that through current vacancies and conversations. Learning CAD solely because it was once common is a weaker reason.
FAQ: Will one software skill get me hired?
Rarely by itself. The strongest evidence connects a tool to a project stage, an accurate deliverable and a clear contribution. Employers hire people who can use the workflow to solve problems with a team.
The takeaway
Choose a role, read the deliverables, then learn the tool that makes those deliverables possible. Build one small piece of inspectable work and show how you handled a change. That is a more durable signal than a long software list on a CV.
The post Revit, AutoCAD or Rhino? Learn the Software Your Next Architecture Job Uses first appeared on jobs.archi.