2026 edition – updated for the current INCOSE certification process.
Applying for Certified Systems Engineering Professional (CSEP) certification is an opportunity to demonstrate that your systems engineering experience meets the requirements established by INCOSE.
For an experienced systems engineering practitioner, the difficult part is not necessarily having the required experience. It is describing that experience clearly enough for someone who was not there to recognise it.
A useful principle to keep in mind throughout your application is this:
INCOSE wants candidates who meet the requirements to achieve CSEP certification. Make it easy for the reviewers to see that you qualify.
This article focuses primarily on CSEP, where documenting and substantiating systems engineering experience forms a significant part of the application. ASEP has no experience requirement and is primarily concerned with satisfying the INCOSE Knowledge Requirement.
Here are ten practical suggestions that can help.
TIP #1 – Start with the current INCOSE requirements
Before completing anything, read the current instructions on the INCOSE Certification website.
Certification processes change over time, so avoid relying on an old application form, an article written several years ago, or even advice from someone who obtained CSEP under an earlier process.
Start by understanding:
- the current certification requirements;
- the experience requirement that applies to you;
- the systems engineering experience areas;
- what information INCOSE expects you to provide;
- what your references will be asked to confirm; and
- the current application and Knowledge Exam process.
You may also have access to a specific certification pathway through an organization, university, INCOSE chapter or other arrangement. Check whether one applies to you before beginning.
A little time spent understanding the process at the start can save considerable rework later.
TIP #2 – Choose the right SEP level
INCOSE offers three levels of Systems Engineering Professional (SEP) certification, recognising different stages of a systems engineering career:
- ASEP – Associate Systems Engineering Professional: aimed at individuals seeking formal recognition of their systems engineering knowledge. No systems engineering experience is required.
- CSEP – Certified Systems Engineering Professional: aimed at practising systems engineering practitioners with at least five years of proven systems engineering experience.ESEP – Expert Systems
- Engineering Professional: aimed at accomplished senior systems engineering practitioners, technical leaders and chief engineers. It normally requires at least 25 years of systems engineering experience, or 20 years if you are already a CSEP, together with the applicable professional-development and technical-leadership requirements.
You can find INCOSE’s current comparison of the three certification levels here: Start Your Certification – INCOSE.
ASEP is not a prerequisite for CSEP. If you already meet the CSEP experience requirements, there is no need to obtain ASEP first. If you do obtain ASEP and later progress to CSEP, you do not need to repeat the Knowledge Exam.
Do not automatically assume that you lack the necessary experience simply because your job title has never included “systems engineering”. Many engineers perform substantial systems engineering work under titles such as technical lead, project engineer, design authority, engineering manager or solution architect. What matters is whether the work you actually performed can be demonstrated as qualifying systems engineering experience.
If you are early in your career and do not yet have the necessary experience, ASEP provides recognition of your systems engineering knowledge while you build the experience required for CSEP.
If you already have five or more years of substantial systems engineering experience, assess yourself against the CSEP requirements rather than applying for ASEP simply because it feels like the safer option.
ESEP is rather different. It is intended not merely for someone who has been working for a long time, but for an accomplished and recognised systems engineering leader.
Choose the highest SEP level that your actual, demonstrable experience supports.
TIP #3 – Describe what you actually did
This is probably the most important advice in this article.
Reviewers are assessing your systems engineering experience, not the systems engineering performed by your team, project or employer.
Compare:
“I was a member of the team responsible for defining the system architecture.”
with:
“I developed and evaluated alternative system architecture concepts, applied agreed decision criteria to support selection of the preferred architecture, defined the resulting system elements and their relationships and interfaces, and documented the selected architecture as part of the system architecture definition.”
The second description gives the reviewer something they can assess.
Where possible, describe your work using recognised INCOSE terminology and the language of the Systems Engineering Handbook and its processes. If your organization uses different internal terms, translate them into the closest accurate systems engineering concepts rather than assuming that the reviewer will make the connection for you.
Do this naturally and accurately. The objective is not to repeat Handbook terminology for its own sake, but to make clear how the work you performed relates to recognised systems engineering activities and processes.
Where appropriate, describe:
- decisions you made or supported;
- analyses you performed;
- requirements you developed;
- models you created;
- reviews you conducted;
- trade studies you performed;
- interfaces you defined or managed;
- risks you identified or treated;
- verification or validation activities you planned or performed; and
- engineering artefacts or work products you produced.
Be specific without turning the application into a project history.
The question to keep asking is:
“What evidence have I given the reviewer that I personally performed systems engineering?”
TIP #4 – Use specific evidence and work products
Statements about responsibilities are useful. Evidence of applying those responsibilities is stronger.
Where appropriate, refer to specific systems engineering outputs or work products that demonstrate what you actually did. These might include requirements, architecture descriptions, trade studies, risk analyses, verification or validation material, interface definitions, plans, models, or technical review outputs.
You do not need to provide the artefacts themselves. The purpose is simply to make your experience concrete and credible rather than relying on a generic job description.
For example, saying that you “performed requirements engineering” is much less useful than explaining that you elicited stakeholder needs, developed and analysed system requirements, resolved issues with stakeholders, and contributed to the approved requirements baseline.
Not every valid systems engineering activity will result in a named document or artefact. Activities, analyses, engineering decisions and responsibilities can also provide strong evidence of experience.
If aspects of your work are commercially sensitive or classified, describe the system and your contribution at a level that allows the nature of the systems engineering work to be understood without disclosing restricted information.
TIP #5 – Map your experience before completing the application
The current INCOSE application process allows you to enter your experience through the online process, but it can still be very useful to work through your career separately before entering everything into the application.
Consider creating a simple spreadsheet or table and mapping your career against the INCOSE systems engineering experience areas.
For each relevant position or period, capture:
- the start and end dates;
- your role and organization;
- the systems or projects involved;
- the INCOSE experience areas to which your work relates;
- what you personally did in each area;
- significant examples or work products that support the experience; and
- the references who could credibly verify that period of work.
This allows you to look at your experience as a whole rather than reconstructing your career one application field at a time.
It can help identify:
- gaps in the experience you intend to claim;
- overlapping periods that need to be treated carefully;
- areas in which you have more relevant experience than you initially realised;
- places where your organization’s terminology needs to be translated into INCOSE terms; and
- whether you have suitable reference coverage for the experience you intend to claim.
That last point is particularly useful. As you map each period of experience, ask who could credibly confirm that work? It is much better to identify a reference gap while planning your application than after you have completed it.
For CSEP, the current application guidance requires candidates to document at least three systems engineering experience areas in which they have worked for at least 12 months, and to list enough references to cover the minimum required experience.
A simple preparation table can therefore help you answer three important questions before you start:
Do I have enough qualifying systems engineering experience?
Do I have the required breadth of experience?
Can appropriate references substantiate it?
Think first, map the experience, then complete the application.
TIP #6 – Demonstrate breadth as well as depth
CSEP is not intended simply to demonstrate that you have spent several years performing one narrow systems engineering activity.
INCOSE looks for both depth and breadth of systems engineering experience.
Current CSEP guidance requires at least one year of experience in at least three systems engineering experience areas.
That means you should pay attention not only to your total qualifying experience, but also to the range of systems engineering activities in which that experience was gained.
Do not artificially distribute time between areas merely to make the numbers work. Your application must accurately reflect what you did.
However, people often overlook legitimate systems engineering experience because their organization used different terminology.
For example, work described internally as “technical planning”, “solution definition”, “design authority”, “technical assurance” or “customer analysis” may contain activities that correspond directly to recognised INCOSE systems engineering experience areas.
Look at what you actually did, rather than relying only on the title of the role or the terminology used by your employer.
TIP #7 – Describe your experience in INCOSE terms
Your company does not need to use INCOSE terminology for your experience to qualify.
But you should help the reviewer make the connection.
Translate the language of your organization into recognised systems engineering language where that translation is accurate.
If your organization called an activity “solution definition”, explain the requirements, architecture, analysis or design work that you actually performed.
If you were called a “technical lead”, do not assume that the title demonstrates systems engineering experience. Describe the relevant planning, decision-making, risk management, architecture, integration, verification or other systems engineering work that formed part of the role.
Using appropriate INCOSE terminology has two advantages:
- it demonstrates that you understand how your practical experience relates to the systems engineering discipline; and
- it makes the reviewer’s job considerably easier.
Do not force your experience into terminology that does not genuinely fit. The objective is not to decorate your application with systems engineering vocabulary. It is to describe real experience in terms that make its systems engineering relevance clear.
Remember: the reviewer was not on your project. Do not make them reverse-engineer your organization’s terminology to determine whether your experience qualifies.
TIP #8 – Make the numbers and the narrative agree
Once you have mapped your experience, check the complete picture.
Your dates, experience claims, descriptions and reference coverage should tell the same story.
Pay particular attention to overlapping positions and concurrent activities. You cannot create additional months of experience simply because you performed several systems engineering activities during the same calendar period.
Check that:
- dates are consistent;
- experience is not inadvertently double-counted;
- the required total qualifying experience is demonstrated;
- the required breadth across systems engineering experience areas is evident;
- descriptions support the experience being claimed; and
- your references can collectively substantiate the necessary periods of experience.
A reviewer should be able to move from your summary information into the detailed descriptions and find a consistent, credible account of your career.
TIP #9 – Choose your references carefully – and help them help you
References are an important part of the CSEP application because they help substantiate the systems engineering experience you have described.
Your references do not need to be INCOSE SEPs themselves. What matters is that they knew your work during the period concerned and understand systems engineering well enough to credibly confirm the experience you are claiming. Where possible, having a reference who is an experienced systems engineering practitioner — and particularly someone familiar with INCOSE — can make this easier.
It is useful to identify potential references while mapping your experience in Tip #5. Think about who worked closely enough with you during each relevant period to confirm what you actually did.
Before sending the formal reference request, contact the person and give them some context. It can be helpful to provide a short factual summary of:
- the projects or systems you worked on together;
- your role at the time;
- the systems engineering activities you remember performing; and
- the period of experience you intend to claim.
Ask them whether they agree with your recollection and let them know how that experience has been described in your application. This helps your application and their reference tell a consistent story without asking them to simply repeat your wording.
The aim is alignment, not coaching. Your reference should still provide their own independent assessment of your experience.
It is also worth starting this process early. In practice, two things can significantly extend the certification timeline: preparing for and completing the Knowledge Exam, and, often even more so, getting all of the required reference material submitted.
The exam is largely within your control. References depend on other busy people.
A little preparation and a friendly follow-up can save a surprising amount of time.
TIP #10 – Give it a final check
Once you are happy with your application, read through it one last time for clarity and consistency.
Check that the dates make sense, that your descriptions clearly explain what you did, and that someone unfamiliar with your projects can understand how your experience relates to systems engineering.
If you are unsure, ask a CSEP or someone familiar with the INCOSE certification process to review it before you submit.
Most importantly, do not overcomplicate the process.
If you meet the requirements, your job is simply to describe your experience clearly enough for the reviewers to recognise that.
Make it easy for them to say yes.
