- CLD means Certified LabVIEW Developer, a National Instruments credential earned by building a working application, not by answering multiple-choice questions.
- The initial exam is a four-hour practical: build a LabVIEW application from a specification, software only, no hardware.
- Grading uses a 40-point rubric: Programming style 15, Functionality 15, Documentation 10. You need 28/40 (70%).
- NI recommends 12-18 months of LabVIEW development experience; there is no mandatory prerequisite certification listed.
What CLD Means in This Context
CLD stands for Certified LabVIEW Developer, a professional credential issued by National Instruments Corporation (NI). It certifies that you can design, build, document, and test a LabVIEW application that is modular, readable, and maintainable. If you have seen the same three letters attached to other credentials, set those aside: everything on this page concerns the NI LabVIEW credential only. For other phrasings of the same question, see our explainers on what CLD stands for and the meaning of CLD.
The CLD sits at the developer level of NI's LabVIEW certification path. It is not a trivia test about palette locations or a recall quiz on function names. It is a work sample. NI hands you a specification, you build the application, and graders evaluate what you built against a published rubric. That single fact shapes how you should prepare, and it is the reason this credential has a reputation among LabVIEW engineers as a genuine measure of practical skill.
How the Exam Actually Works
The format is simple to state and demanding to execute: you receive a specification and have four hours to build a working LabVIEW application that satisfies it. The exam covers software development only. You do not wire up instruments or data-acquisition hardware; any hardware behavior is simulated in software, so your score depends on your architecture, your code quality, and your documentation, not on lab equipment.
NI's preparation guide permits the use of built-in LabVIEW Help, shipped examples, and templates. It prohibits externally developed VIs and outside resources. In practice this means you should know the stock templates and example projects well enough to start from the right one quickly, because choosing and adapting an appropriate starting point is a legitimate and valuable skill under this rule.
The delivery model is modern: NI schedules the exam through Pearson VUE, which also offers an NI OnVUE online-testing route. Performance-based NI exams run on a secured virtual machine, so the logistics described in the older guide (USB drives, local proctors, specific software versions) are historical. Always confirm the assigned software image and candidate rules in your current booking instructions rather than relying on the older PDF's delivery section.
For a candid look at how demanding this format feels in practice, read How Hard Is the CLD Exam? and then pressure-test your readiness with timed builds, which our practice test site is designed to support alongside your own coding exercises.
The 40-Point Rubric
Graders score your submission against a 40-point rubric split across three categories. The passing criterion is 28 out of 40 points, or 70%. For a deeper treatment, see CLD Passing Score: Exactly What You Need to Pass.
| Rubric Category | Points | Share of Rubric | What Graders Look For |
|---|---|---|---|
| Programming style | 15 | 37.5% | Block diagram layout, modularity, subVI design, error handling, readable data flow |
| Functionality | 15 | 37.5% | Does the application meet the specification and run without errors or unwanted behavior |
| Documentation | 10 | 25% | Front-panel, block-diagram, and VI-property documentation that explains the code |
| Total | 40 | 100% | Pass at 28/40 (70%) |
Two points deserve emphasis. First, these percentages are calculated shares of the grading rubric, not weights for the ten topic areas described below. NI does not publish percentage weights for the topics. Second, documentation carries a quarter of the available points. Candidates who build a perfectly functional application but leave it undocumented routinely forfeit points they could have secured in minutes.
The Ten Exam Topics
NI's preparation guide lists ten Exam Topics. They define the knowledge a successful submission demonstrates. They are not separately scored sections, but every rubric point traces back to one or more of them. Our complete guide to all 10 CLD content areas goes deeper; here is the working summary.
Domain 1: Design Concepts
The foundation under everything else. You are expected to reason about code quality as an engineer.
- Modularity, scalability, readability, and maintainability
- Cohesion and coupling between components
- Hierarchical and file-level organization of a project
Domain 2: User Interface Design
Front panels are graded for usability and tidiness, not just correctness.
- Color, grouping, and control properties
- Custom objects and clear icons
- Static and dynamic state of controls at initialization and at stop
Domain 3: Block Diagram Layout and Style
A reviewer should be able to read your diagram left to right without effort.
- Clean data flow and readable wiring
- Consistent layout that avoids hidden or overlapping code
Domain 4: Programming Practices
Choosing the right building blocks for each job.
- Data elements, functions, and subVIs
- Structures, references, and property nodes
Domain 5: SubVI Design Practices
Reusable, well-formed modules are central to the style score.
- Modular subVI design with sensible front panels
- Clean connector panes and recognizable icons
Domain 6: Architecture Selection
Matching the specification to a design pattern that is scalable, maintainable, and responsive. See the next section.
Domain 7: Timing
Applications must behave predictably over time without hogging the CPU.
- Timing functions and Express VIs
- Event and synchronization timeouts
- Timed structures
Domain 8: Error Handling
Errors must be detected, propagated, and reported coherently rather than ignored.
Domain 9: Documentation
Front-panel, block-diagram, and VI-property documentation that lets another developer pick up your work.
Domain 10: Testing
Reviewing your own code and documentation, verifying functionality, and catching errors before you submit.
Architectures You Must Be Able to Build
Architecture Selection is where candidates most often separate themselves. The specification will describe behavior, such as acquiring data, responding to user actions, and logging results, and it is your job to choose a structure that handles it without blocking the user interface. NI's guide names the patterns a candidate should know:
- Simple state machine for sequential, mode-based logic
- User interface event handler for responding to front-panel actions without polling
- Queued message handler for command-driven processing
- Data and event producer-consumer for decoupling acquisition from processing or display
- Functional global variable for protected shared data
The goal is a design that is scalable, maintainable, and responsive. A common failure is an application that works for the happy path but freezes the interface during a long operation, or that cannot be extended without rewriting. Practicing each pattern from a blank diagram, and knowing when each fits, matters more than memorizing definitions.
Key Takeaway
Build each of the named patterns from scratch at least a few times before exam day. Fluency means you can read a specification, name the right architecture in under a minute, and spend the remaining time on quality rather than deliberation.
Eligibility, Experience, and Validity
NI lists no mandatory prerequisite for the initial CLD, and the current credential page does not require another certification first. Older versions of the guide described a Certified LabVIEW Associate Developer prerequisite, but that has been superseded by the current credential page. NI recommends 12-18 months of LabVIEW development experience, and it notes that completing Core 1, Core 2, and Core 3 training can substitute for three months of that experience. Our CLD requirements guide unpacks what qualifying realistically looks like.
Once earned, the certification is valid for three years. NI's recertification policy, updated April 30, 2026, allows renewal by examination and offers Recertification by Points to developer-level and architect-level professionals. The recertification examination (CLD-R) is a distinct exam and should not be used as a model for the initial exam's format.
Registration and Test-Day Logistics
Scheduling runs through Pearson VUE, with the NI OnVUE option for online testing. Because delivery details change over time, treat the current booking instructions as authoritative: they tell you which software image you will receive, what the candidate rules are, and how the secured virtual machine behaves. For fees and what to budget, see CLD Certification Cost: Complete Pricing Breakdown, and for scheduling windows see CLD Exam Dates.
Before test day, confirm three things: that your environment meets the online-testing requirements if you choose OnVUE, that you know what resources are allowed (built-in Help, examples, and templates only), and that you have practiced working inside an unfamiliar, locked-down environment so the interface itself is not a distraction.
Who Values the Credential
LabVIEW is used heavily in test and measurement, automated test equipment, research laboratories, industrial monitoring, and system integration. Employers in those spaces, along with the integrators and consultancies that build systems for them, tend to value a credential that demonstrates working code rather than recalled facts. A CLD signals that you can produce an application another engineer can maintain, which matters in teams where LabVIEW code lives for many years.
Whether the investment pays off for you depends on your role and market. For analysis, see Is the CLD Certification Worth It?, the CLD salary guide, and CLD jobs.
A Domain-Ordered Preparation Plan
Because the exam is a build, your plan should be a sequence of builds. This is the one place where scheduling matters, so here is an ordering tied directly to the ten topics. For a fuller version, use the CLD study guide.
Foundations: Design Concepts, UI, and Diagram Style
- Review cohesion, coupling, and hierarchy on an existing project
- Practice front-panel grouping and initialization state
- Rework a messy diagram into a clean left-to-right flow
Building Blocks: Practices, SubVIs, and Error Handling
- Build subVIs with clean connector panes and icons
- Use references and property nodes deliberately
- Wire error propagation through every module
Architecture and Timing
- Build each named pattern from a blank diagram
- Add timing, timeouts, and nonblocking behavior
Full Timed Builds: Documentation and Testing
- Complete four-hour mock builds against self-written specifications
- Score yourself against the 40-point rubric
- Reserve the final stretch of each build for documentation and review
Self-assessment is the key habit: after every mock build, grade yourself honestly on style, functionality, and documentation, then fix the weakest category first. Our one-page CLD cheat sheet is a handy final review, and the CLD Exam Prep practice site can supplement your coding with conceptual review. For context on how candidates fare overall, see what the data shows on CLD pass rates.
Frequently Asked Questions
Here, CLD stands for Certified LabVIEW Developer, a credential from National Instruments that validates the ability to build well-structured, documented LabVIEW applications.
No. The initial CLD is a four-hour practical in which you build a working LabVIEW application from a specification. It is graded on a rubric covering programming style, functionality, and documentation.
You need 28 out of 40 rubric points, or 70%. Programming style and functionality are worth 15 points each, and documentation is worth 10.
NI lists no mandatory prerequisite on the current credential page. It recommends 12-18 months of LabVIEW development experience, and Core 1, Core 2, and Core 3 training can substitute for three months of it.
Three years. You can renew by examination, and NI also offers Recertification by Points to developer-level and architect-level professionals under its policy updated April 30, 2026.