Wednesday, March 20, 2013

"The Foreign Service": What is it?

In my non-work world, one question I get asked semi-frequently is, "What is the foreign service?  I thought you worked for USAID?"  Or, more simply: "What is it you do again?"

In order to put to rest these questions, I thought I'd use the newly-rediscovered blog to provide a bit of an explanation of what I do, and why your taxes go to pay my federal salary (thank you very much, by the way).

So I work for USAID, which stands for the United States Agency for International Development (our fairly lame website is here: www.usaid.gov).  Normally, when people think about U.S. foreign policy (if they do at all), then they normally think of the State Department.  But in reality, our foreign policy is based on the "Three D's" -- diplomacy (which State Department takes care of), defense (the Pentagon), and development (USAID).  In other words, the way our government interacts with other countries is through some combination of those 3 D's.  

The "foreign service" is a reference to a specific type of employee, regardless of which specific government agency you work for.  The formal definition (at least the one I found on the web) is: "Members of the Foreign Service can be sent to any embassy, consulate, or other diplomatic mission anywhere in the world, at any time, to serve the diplomatic needs of the United States."  It's a little bit like being in the military: whether you are in the Navy or Army or Air Force or Marines, you're part of the military, and have ranks, a certain mission, etc..  

In terms of numbers, the vast majority of foreign service officers ("FSO's") are part of the State Department.  They represent the elite of the Department -- about 11,500 out of the Department's 50,000 or so total worldwide staff (the rest are civil servants, contract employees, etc.).  USAID also is authorized to have a relatively small number of FSOs -- about 1,800 the last time I checked (out of a total workforce of around 10,000 worldwide, I'm guessing, including American and local staff).  As with State, the FSOs get certain privileges versus civil servants and other employees (for example, FSOs can retire with a pension after 20 years, rather than 30, and most key leadership positions in the Agency are reserved for FSOs, etc. -- the logic behind that is that USAID is, by definition, a "foreign affairs agency").  So the picture looks something like this:

So what does a USAID "foreign service officer" actually do?

Option #1: This is what we'd love to think our job is like.

Option #2: This is what my job mostly is like.
This is me, sitting in the Kabul embassy in 2003, with the windows blocked out by black "bullet curtains" to prevent grateful Afghans from firing at me.
 The truth of the matter is that my job essentially is to lead a team of people to design and implement projects to make corrupt countries less corrupt, to try and protect free media, to help civic and human rights groups, and to improve the relationship between governments and populations.  The idea is that if this all works out, countries won't melt down into civil war or strife, the U.S. won't get sucked in to more endless (and endlessly expensive) military adventures, and everybody's happy.  So, compared to the war in Iraq, USAID is a pretty good deal for the US taxpayer.

In terms of my day to day routine, my work consists of a mixture of boring office work, and more exciting other stuff which I could tell you about but then I'd have to kill you.  An example of our highly classified work:

I Am A Terrible Blogger

I would assume that the first rule of being a good blogger is to remember that one actually has a blog.  Having failed this first test, I can safely assume that I suck at blogging.  It has now been over a year and a half since my last post, which I can perhaps attribute to the following factors:
  1. I forgot about the blog
  2. I do a fair job of putting pictures and photos up on Facebook (which contributes to #1)
  3. I have a job that keeps me traveling between five Central Asian countries, and thus doesn't leave too much time for things like blogging.
These are all explanations -- hard to read ones, at that -- not excuses, and so, in the spirit of "not letting the perfect be the enemy of the good enough," I will write a brief update here.

Previously, my life in Almaty might have best been characterized as follows:
Almaty's great for outdoor activities -- the mountains are right next door, there's skiing and hiking galore.

This past Fall, though, we had some big news, which has changed everything.  Again, a picture is probably worth a thousand words:
Whoa!  What happened to Amita's belly?!?
 As you probably know by now, Amita and I are expecting a baby sometime around May 20, 2013.  A little girl, to be specific (assuming the ultrasounds are correct).  This is a very exciting time for us, but also incredibly intimidating not only because we've never had a kid before, but because of all of the administrative and logistical tasks that have to be taken care of in order to then successfully relocate back to Kazakhstan, when the Deed is Done.  There is about a 20 page State Department cable outlining all of the tasks we have to take care of, from getting Medical Clearance to a diplomatic passport for the little one, to getting the Kazakh government to give her a visa, etc..  And on the "what to buy?" side, I'm absolutely astounded by the array of "must-have" items that a newborn requires.  It's hard to tell what's really required, and what is simply the product of very (VERY) clever marketing campaigns. 

In any event, Amita will fly from Almaty to NYC on April 6, and I will join her around May 10.  Then we're supposed to fly back to Kazakhstan on July 3rd, to introduce what we hope will be our healthy, happy (or, more likely: confused) little girl to her new home.

love,
D  & A

PS - we're still open to name suggestions!  :-)