Full disclosure: I still am an AutoCAD developer on a contractual basis. So, this post is going to seem pretty self-serving at first. But I'm really going to try to avoid anything that's self-promotional or seems like an implicit ad for my services.

I've been working with AutoCAD code for over 20 years now, so I'm deeply aware of the platform. I've also run a business for those 20 years and have hired contractors or outsourced some general software projects. As a result, I can put myself in the seat of the hirer or the hiree.


Drafter Or A Developer

When most people think of an AutoCAD developer, they imagine someone who can expertly draft, design, and manipulate digital drawings. While it's great to have a developer who's technically proficient with AutoCAD, it's less essential than that person being a good developer.

Developers need to be experienced enough with AutoCAD to know the core product and to be able to functionally test their own code. Beyond that, it's not all that important.

Would you rather have a developer who can swap ACAD layers in a half second vs. two seconds, or would you rather have a developer who can isolate and fix errors quickly?


They Need To Understand Your Workflow

Any developer trying to develop Autodesk solutions for your business should start by understanding your workflow. They should ask (or you should insist) for you to show them how you currently get the job done.

We once won a huge bid for a power company where we were competing against Autodesk Consulting for a massive 2-year configuration and special programming project of an Autodesk product.

The main reason we won the bid is that we asked questions about how a new solution should behave, step 1 into step 2, etc. Autodesk Consulting really asked no questions; they just threw a random price at the client. They were willing to toss a number out there and not worry about under-bidding - there were internal political considerations where they needed "the win."

Our little 3-person team got the contract instead. Why? Because we asked questions and understood their current workflow and what they wanted their future workflow to look like.


Suggest New Ideas For Your Workflow

Once your developer understands your workflow, they can actually dream up some new ideas.

I've found that sometimes clients ask for things where they're surprised by what a big (and costly) ask that is; and other times they're afraid to ask for something they think is too costly, and it ends up being easy.

Generally speaking, almost every idea IS POSSIBLE. It's just a question of how long and how much money it will take to accomplish.

If anything, as a developer I've been too guilty of coming up with too many ideas that would be helpful but not a great use of time and resources. But it's great when a developer gets to that point of suggesting "Wouldn't it be cool if ..." ideas.

Almost all of the good ideas I've had for AutoCAD clients have been in requirements-gathering processes where I ask real workers, "What could I invent that would help you do your job better?" or "What magic button would you like to have in AutoCAD?"


Strong Communication Skills

Designing in AutoCAD doesn't happen in isolation. A developer may collaborate with architects, engineers, project managers, and clients.

The ability to clearly explain design choices, listen to feedback, and translate complex ideas into understandable visuals is invaluable. Miscommunication can lead to costly errors or delays, which are really expensive and demoralizing to un-do.

Also, don't trust developers who traffic in buzzwords or unknown algorithms.

To paraphrase Albert Einstein, "If you can't explain it to a 6-year-old, you don't know what you're talking about."


Attention to Detail

Obviously, everybody wants developers who are precise. A minor oversight can cascade into larger problems, affecting both functionality and aesthetics.

You can tell who's detail-oriented by their work. If their emails are very detailed, yes, it might be annoying, but it shows a lot of consideration. What in the real world can be dismissed as being "anal" is actually "detail-oriented" at work.

Thorough developers write cleaner code, have error-handling procedures, and put out better documentation.


Understanding of Industry Standards

AutoCAD is used across a variety of industries, from architecture and civil engineering to manufacturing and product design. So, if you're an architect, it's more ideal to have a developer who has previously had architectural clients.

I will tell you that as a repeat developer for utility companies for electric distribution design tools, I've built up a library of code functions for clients. If Client A needed it, it's very possible that it could benefit Client B, as well. Although I'm very mindful of code ownership issues; even so, doing it once makes it VERY easy to do it again.

That said, it’s important but not essential. As long as you can describe it, they can do it.


Adaptability and Continuous Learning

The world of CAD is constantly evolving with software updates, plugins, and industry trends changing regularly. Outstanding AutoCAD developers stay curious and adaptable, continuously learning new techniques, tools, and technologies.

More specifically, developers know their way around helpful APIs. There's no point in spending time (and money) to reinvent the wheel to write code when existing APIs can already get you most of the way there. Developers who are familiar with Autodesk APIs have the potential to shave days off time-sensitive projects.


Conclusion

Being an excellent AutoCAD developer is about more than just technical mastery. Don't be fooled by a demo that they can draw quickly; most demos are fake vaporware anyway.

It's about combining creativity, communication, precision, adaptability, and collaboration to deliver high-quality, practical solutions.

My advice to you when hiring an AutoCAD developer is to pay close attention to your prospective developer's questions and make your judgment based on how well those questions demonstrate an understanding of your industry.