CAD Drafter interview questions and how to answer them
A CAD drafter interview is mostly a software interview wearing a nice shirt. Expect questions about how you set up and clean up files, and expect to sit at a workstation and draw something while someone watches. The questions below are the ones that separate a drafter who knows the program from one who has just used it.
What happens in each round
- 1
Phone screen with a recruiter or office manager
What happens
Which programs you've used on real projects, what kind of drawings you've made, whether you can start soon and whether your pay expectations fit. Name your software plainly and don't inflate it, because the next round tests it.
- 2
Technical interview with the CAD manager or a lead drafter
What happens
Whether you understand how files are built: xrefs, layers, blocks, layouts, annotation scale and plot styles. They're listening for habits that keep a shared project clean, not just commands you know.
- 3
Drafting test at a workstation
What happens
They hand you a marked-up print or a sketch and a template, then watch how you work. They look at speed, whether you use the office layers, how you place dimensions and text, and whether the finished sheet plots correctly.
- 4
Portfolio walkthrough with an engineer or architect
What happens
Whether you understand what your drawings show and why each detail is there. Engineers want to know you'll catch a mismatch between sheets and ask about it, rather than drawing whatever the markup says.
Questions you're likely to get
1.How do you use external references, and what do you do when one comes in broken?
Why they ask
Most multi-sheet projects are built on xrefs, and broken paths waste hours. They want to know you can fix one without breaking the rest of the set.
How to answer
- Explain that you keep base files like the survey or floor plan as xrefs so every sheet updates from one source
- Say you prefer relative paths so the project survives being moved or copied to another folder
- Walk through fixing a missing reference in the External References palette by repathing it, not by binding it
- Mention checking with whoever owns that base file before you change anything inside it
2.What goes in model space and what goes in paper space?
Why they ask
It's a basic question that a surprising number of people get fuzzy on. Mixing the two causes wrong scales and messy plots.
How to answer
- Model space holds the geometry drawn at full size, real units
- Paper space layouts hold the title block, viewports and sheet notes at plotted size
- Viewports show the model at a set scale, and you lock them once they're right
- Give a quick example, like a site plan and an enlarged detail on one sheet through two viewports
3.A consultant sends you a file that ignores our layer standards. What do you do with it?
Why they ask
Outside files arrive all the time, and dropping them straight into a project pollutes it. They want to see a cleanup routine.
How to answer
- Open it separately first, never straight into the project
- Purge and audit it, then map their layers to yours with a layer translator or by hand
- Strip out anything you don't need, like their title block or unused blocks
- Attach it as an xref on its own layer group so it stays easy to update when they send a new version
4.How do you build and manage blocks?
Why they ask
Blocks decide how fast a drafter works and how easy a file is to edit later. Good ones also carry data into schedules.
How to answer
- Draw blocks on layer zero so they take the layer they're inserted on
- Use attributes for text that changes, like a tag number or an equipment name
- Mention dynamic blocks for parts that come in several sizes or orientations
- Keep them in a shared library or tool palette so everyone inserts the same version
5.A sheet plots with every line the same heavy weight. How do you track it down?
Why they ask
Plot problems show up late, right before a deadline. They want someone who knows where to look instead of guessing.
How to answer
- Check which plot style table the layout is using and whether it's the office one
- Confirm the display setting for plot styles and lineweights is on in the layout
- Look at whether objects have their properties set by layer or overridden one by one
- Plot a test PDF before sending the whole set again
6.How do you keep text and dimensions readable across viewports at different scales?
Why they ask
Annotation that's too big in one detail and unreadable in another is a classic sign of someone who hasn't worked on a real set.
How to answer
- Explain annotative text and dimensions and how they size themselves to the viewport scale
- Or describe dimensioning in paper space when the office prefers that
- Mention using the office text and dimension styles rather than making your own
- Say you check the printed sheet, not the screen, before calling it done
7.Tell me about a shortcut or customization that saved you real time.
Why they ask
This shows whether you've gone past the basics. Drafters who tune their setup are usually the fast ones.
How to answer
- Name one specific thing: a custom alias, a tool palette, a template, a sheet set, a small AutoLISP routine
- Say what chore it replaced and how often you did that chore
- Mention sharing it with the team if it fit the office standards
- Keep it brief and concrete
8.Walk me through updating a set after a late design change.
Why they ask
Changes ripple through several sheets. They want to know you trace the ripple instead of fixing only the sheet the engineer clouded.
How to answer
- Start by listing every sheet the change touches, including sections, details and schedules
- Tell the engineer about any sheet they didn't mark that also needs to move
- Add revision clouds and deltas and update the revision block and sheet index
- Check the changed sheets against each other, not just against the markup
9.How do you work on a shared project so you don't overwrite someone else's changes?
Why they ask
Several drafters often touch one project on a shared server or in a document system. Version mix-ups are expensive.
How to answer
- Follow the office's check-out or file-locking method, whatever it is
- Work in your own files and reference others instead of editing them
- Keep file names and folders to the office convention
- Mention a time you caught or avoided a conflict by asking first
10.How do you turn a scanned or PDF drawing into a clean CAD file?
Why they ask
Plenty of projects start from an old paper set. They want to know you won't trust a scan's scale blindly.
How to answer
- Attach the PDF or image as an underlay and scale it using a known dimension on the drawing
- Check the scale in a second place, because old scans stretch
- Redraw on proper layers rather than converting the PDF linework straight into objects
- Flag anything unreadable to the engineer instead of guessing
11.How do you learn a program or feature you haven't used before?
Why they ask
Firms switch software and versions, and they'd rather hire someone who picks things up than someone who knows only one setup.
How to answer
- Give a real example of picking up a program or a feature, like sheet sets or Revit families
- Say how you learned it: a short course, a practice project, a coworker who knew it
- Show you tried it on low-risk work before using it on a deadline set
- Be honest about what you're still slow at
Mistakes that sink good candidates
Listing software on your résumé that you can't use when they sit you down for the test
Complaining about engineers who change their minds, since that's the job
Bringing portfolio sheets you can't explain line by line
Saying the checker will catch your mistakes, which tells them you won't check your own work
Need more CAD Drafter interviews to prep for?
HeroApply applies to CAD Drafter jobs that match you, every day. 53 jobs are open today.