DDS hires professional engineers at a special paygrade pegged to their civilian pay stubs for a 2 year tour of duty fixing pressing issues in DoD tech via pretty broad authority to sidestep
A) the usual senior military slow-roll* in the way of these fixes
B) the sh**y govt contractors who made the tech and usually get paid to fix their own bad tech.
DDS Hires a lot of motivated engineers who would be in civil service but for the $180k -> $90k paycuts and fear of bureaucratic hell. It is run by one of the ~founders of opentable who, post opentable riches, was flying on 9/11/01, decided to join the Chicago PD as a result, did west Chicago homicide until the PD discovered his past, he then stood up Chicago’s data-based policing technical approaches, and eventually the Obama admin heads about him asked him to take over DDS (iirc, +/- details there).
Cool stuff and I’d work for them in a second, probably need another few years in private sector though.
> DDS hires professional engineers at a special paygrade pegged to their civilian pay stubs
I wish USDS would do this as well; I feel like they'd attract a lot more talent. Although perhaps they want to attract exactly the kind of talent who would take a big pay cut out of a sense of service/duty.
> Cool stuff and I’d work for them in a second
For myself, while I recognize that military is a necessary evil in the world we live in, and I have a ton of respect for the people who put themselves in harm's way, working for an org with a .mil address would be against my values. I'm so torn, though, since (e.g.) the Internet itself came out of the DoD. It's a hard pill to swallow for me sometimes that a lot of essential civilian tech was originally developed by or for the military.
I think it’s ok to have that self awareness about where your values line is, when it’s paired with understanding that you’re able to abstract away that public service to someone else who does it for you.
A ton of folks want to have a free lunch in that respect, especially in tech. God help them if Amazon wins the JEDI contract while they work there, but other nefarious work FAANGs get up to while employed at one is ok as long as it’s ~out of sight. Like the Dragonfly project at GOOG...
Similarly, there’s this issue of so much fundamental tech came out of huge DARPA grants, NIST work, and so on. It’s ok if you don’t want to be the one working with DARPA/DDS, but tech’s roots are so tied to them that it has to be ack’d.
The line of folks who “would be in the DoD but for X” is long, and it’s a comically reoccurring conversation for people who do DoD work. That conversation is much different if that awareness exists, though.
The org has done really interesting things under a few different political climates. To the extent it’s safe/neutral to say we’re entering a more pro-govt can-do env, I think they’ll have a cool next 4 years as an org.
Some of the projects they talk about doing have huge value-adds to technically underserved groups like military families during mandatory base moves every few years. Those groups are totally dependent on following the system as designed (get your travel voucher here, your goods shipped here, etc) and much of it depends on single option, very janky govt, almost intranet-like, porfals. Iirc, one of their projects was fixing a portal was leaking SSNs like gangbusters. Normal times, that’s a 6 month -> 10 year process to work with the contractor. DDS did it fairly quickly.
I don't know Brett super well so I can't speak to the rest of his background, but it's not correct that the Obama admin asked him to take over DDS.
DDS's founding head was Chris Lynch, who served in that role until the middle of the Trump administration, when he left government service and that's when Brett got the job.
The first paragraph a job description gives some context to their culture:
> How do you feel about the cloud? Specifically, what are your thoughts on the cumulus clouds of Bespin? Do you believe Cloud City is composed of only cumulus clouds? Do you have any idea about what we are asking? If your answer is yes, definitely read on. If no, still read on, but we might find your lack of faith disturbing!
More money, I assume. The government does not want to raise all programmers’ pay, so instead of adjusting the pay schedules that apply to everyone, they make a special group that the normal pay schedules don’t apply to.
I wonder if it came about because how much of a dumpster fire the first version of healthcare.gov was for the premier of the Affordable Care Act. That probably embarrassed a lot of people.
healthcare.gov's problem led to a rescue team, whose members helped to start USDS, whose members helped to start DDS!
To your first point, it'd be more accurate to say that many government offices often don't hire any programmers, which can (among other issues) make it challenging for those offices to select strong contractors.
> Created in 2015, the DDS operates a Silicon Valley-like office within the Pentagon.