PO3 Private RallyPoint Member 3136587 <div class="images-v2-count-0"></div>I&#39;m aware that while serving there will be things that simply cannot be mentioned, or places/activities that are less than easy to verify or may be OpSec issues to really discuss. I&#39;m looking for tips to keep my resume up-to-date as I progress in my career with out saying too much or potentially violating OpSec measurements. This was not something college prepared me for! 2017-12-01T15:33:32-05:00 PO3 Private RallyPoint Member 3136587

<div class="images-v2-count-0"></div>I&#39;m aware that while serving there will be things that simply cannot be mentioned, or places/activities that are less than easy to verify or may be OpSec issues to really discuss. I&#39;m looking for tips to keep my resume up-to-date as I progress in my career with out saying too much or potentially violating OpSec measurements. This was not something college prepared me for!

2017-12-01T15:33:32-05:00 2017-12-01T15:33:32-05:00 SPC David Willis 3136626

<div class="images-v2-count-0"></div>Unless you spent a career in JSOC most of what we have done is unclassified, at least from an infantry point of view. Best rule of thumb is to keep things simple. Instead of &quot;deployed on presence patrol/checkpoint security mission in Nasiriyah, IRAQ&quot; Just say &quot;deployed to Iraq&quot; In fact employers appreciate simplicity when it comes to military applications as a majority have no clue what we would be talking about if we laid our entire ERB out on paper. Speak to what leadership positions you held and how much responsibility you had, and not so much what you did.

2017-12-01T15:45:37-05:00 2017-12-01T15:45:37-05:00 CPT Private RallyPoint Member 3140855

<div class="images-v2-count-0"></div>I am a bit curious about this. As an E3 how much could you have been exposed too that is classified and what of this classified material would you put into a resume. Have you signed a Non-Disclosure Statement? If you did then you are limited as to what you could say. I have worked in the intel world a bit. Even with that in my background I would now talk abou it. It was years ago and it really wasn&#39;t anything special. Where I was in Iraq 14 years ago isn&#39;t going to compromise anything. What I have seen is some people overact when it comes to this. Plus, you would really have to question if telling anything from operations to a future employer would mean anything. Would a civilian really know what any of these means. If in doubt I would seek out a military resume writing assistant.

2017-12-03T13:36:27-05:00 2017-12-03T13:36:27-05:00 1SG Private RallyPoint Member 3144138

<div class="images-v2-count-0"></div>You need to think in terms of how a future civilian employer will think. Outside some obscure government job that you might apply for that has specific need to know about your missions, most don&#39;t really care. They don&#39;t care that you were responsible for maintaining the electronic tracking of ninjas during operation &quot;Aquaman&#39;s Spear&quot; at xxx deg lat, yyy deg long.<br /><br />They want to know that you have experience maintaining data links, or communications equipment, or general troubleshooting of electronic systems. I suggest you go to the internet and look up the general open source description of your job (rating?) and use that to guide your resume. Also talk about more general skills and accomplishments that you may have. <br /><br />I don&#39;t know the specifics with the Navy, but the Army has transition resources that can help and often provide specialists in taking your military career and pulling out stuff that is useful in a civilian resume.

2017-12-04T16:53:49-05:00 2017-12-04T16:53:49-05:00 2017-12-01T15:33:32-05:00