Preferences

Has anyone here ever done any work at DARPA, and if so how was the experience?

Also, I'm assuming you need some kind of background related to the projects you apply to work on right?


I know a fair amount about this and will happily answer additional questions. There are two main ways to work for DARPA. Bid on contracts when they are opened up for public bid. The other way is to work at DARPA to do this you need an incredibly unique idea that solves a particular office director's mandate for their tenure then you apply as a program manager. Most program managers are academics with unique ideas to solve the needs of that particular office head. You can only work as a program manager for a certain amount of time, I believe two years, before you have to rotate out.

If you work as a contractor on a DARPA program, you generally get to keep all IP rights. I've used these programs to fund companies before.

Where find list of said *"needs of.... department head"*?
Assuming that you mean working on cool research. You can interview and come in as a DARPA Program manager where you need to bring in a grand vision and would be in charge of revolutionizing a field(s). But what is it that you would do day to day? A DARPA PM doesn't do actual research but instead has access to the network of the best minds in research and uses them to shape a multi-million 5 yr 'program' and arrange for funding and transition paths to DoD and private industry. A PM's tenure is 5 yrs, so most PMs come in with a vision, start 2-5 programs, inherit other programs and then transition out.

You can always look at the latest programs - https://www.darpa.mil/work-with-us/opportunities

The people doing the actual research are independent research labs, universities, and small business. These are a combination of scientists and engineers publishing papers and taking the technology from papers to the field.

Frankly, that sounds awful. Like a honeypot for the smoothest bullshitters ever.
You're more wrong than almost any poster I've ever seen on Hacker News. At least you got a throw away before you posted this ignorant comment.
Source: I said so.
GP wrote in a different comment that they worked with DARPA in the past, so I would assume that they know more about the processes than other people.

https://www.hackerneue.com/item?id=36637805

I think you are thinking more of defense contracting than darpa.

Also, darpa has real use-cases and those use-cases tend to be hard to solve ones, they aren't VCs looking for the next trend to vampire like a national security version of the TV show shark tank.

Granted, it is 2023, it is the govt, and it is tech/eng/sci holy trinity of profit so I wouldn't be shocked if I am off the mark with my assessment.

Edit: typo

Maybe. Even when a PM is very technical in their field, they are not expected to know the nitty gritty of the broad area they tackle in a program. To come up with realistic programs and execute them successfully, a PM needs to know where are the boundaries of current knowledge, how much $$ is required to push research to transition to real tech... and sniff out bullshit being sold by research labs. Bullshitters or not, they need to be really good at sniffing bullshit!
No, that's crypto. And some parts of AI.
So, government?
I once interviewed for memex project but didn't get the job. It was $160K-$250K for global remote and hardest interview I ever did (how would you build google for the hidden web for 2 hours, interviewed by 3 senior engineers). I ended being best of ~100 people in that but failed on the next step with machine learning exercise($80/hour take home exercise). This was ~7 years ago.
I worked on the DARPA Urban Challenge (before self driving cars were cool) as part of one of the teams competing, does that count?

My experience with them was positive. They ran that challenge really well and created a good environment for teams to compete. It was fun and memorable.

I worked for a few years for a contractor and we did several DARPA projects.

Pros: work on really exciting stuff. I worked on cutting edge squad-embedded robotics platforms and media forensics to fight fake news. Got to travel a bit for demos. It's very rewarding to know your work is making a real impact.

Cons: they don't call it DARPA-hard for nothing. Timelines are tight, the problems are research heavy with no guaranteed results. I did a lot of work bridging grad student quality code to production systems, which is its own kind of hell.

I'm currently finishing up working on the 2nd big DARPA grant in my career, as an engineer in one of the labs that got paid money to do the work. DARPA funds a lot of "pie in the sky" ideas where the work is super exploratory in the beginning, which is cool because we get to conduct a lot of basic research and try out weird ideas.

Like someone else said, timelines are tight, budgeting is a mess, and every phase you have to continue to justify your team's existence to bureaucrats or you get cut. The updates are in presentation form as well, but you have to abandon the "show don't tell" because the presentation is sent out to a bunch of people that don't attend the meetings afterward.

Overall it's a lot of money to work on cool stuff but I'm happy I'm not managing any of it.

> you have to abandon the "show don't tell" because the presentation is sent out to a bunch of people that don't attend the meetings afterward

I think there is a misunderstanding about what "show don't tell" means.

In a presentation like that tell means: "Our underwater robot is very stealthy." while show means "Our robot spent 2 weeks trailing a nuclear submarine of ours without the submarine being aware of our presence. Here is a picture we took of the submarine's sail, and here is the statement of the captain saying he had no idea." (Obviously this is a silly example, please don't spook people with the biggest, meanest sticks.)

Show means showing your results and tell means describing how awesome you think you are without evidence. It has nothing to do with whether or not your audience attends the presentation.

This is similar to fiction writing, where tell means that you describe what someone is like, while show is describing how that behaviour/emotion appears. For example tell would be "George was angry", while show would be "George banged on the door with two fists, his veins bulging with barely contained rage."

I participated in a DARPA brainstorming conference a number of years back. It was not paid, but a fun experience. So in addition to bidding on contract topics they propose, you can get invited onto working committees or symposiums and such (but that usually means you have expertise on the topic and someone involved knows who you are). It's a pretty good gov agency to work for as well from my various friends who have worked there.
uh - is it a legit, say, interview experience - or is participating in such teams, which are unpaid, just a harvesting of free ideas for DARPA?

Or a secret recruiting method to weed-out those who wont pull whatever narrative is rq'd around said *'needs of the department head'*?

What I worked on was more of a community of interest brainstorming conference where all the participants had an interest in seeing a good outcome of a DARPA program. You could call it "free ideas" but everyone knew that going in and it was the point after all. Research and development usually benefit from a free exchange of ideas from stake holders and people with expertise in the field (or adjacent fields).

Recruiting is never secret and DARPA, DoD, and the IC are just like the rest of the tech industry and _always_ looking for scarce talent (except they have to pay less than commercial sector thanks to congressional laws).

You seem to have convinced yourself of only negative interpretations as being options, but there really is a lot of overtly beneficial research done by DARPA and a lot of people who really believe in the good they do involved. Not to say that there isn't also occasional bad actors, bad policy, or mercenary transactions, but those are the exceptions, not the norm.

>>*You seem to have convinced yourself of only negative interpretations as being options, but there really is a lot of overtly beneficial research done by DARPA*

I appreciate your reality check on this - I dont exclusively focus on negative, but I am sensitive to efforts which ultimately result in negative (sociallogically - such as deeper surveillance) outcomes, and while darpa does awesome science, and great leaps in tech - every one of these steps /tend/ to feed surveillance-state paradigms.

Like most government agencies I assume most of the work is done by some form of defence contractor.

That being said, I'd like to hear stories from anyone who has worked there as well.

I've never worked at DARPA, but yeah, they are a funding agency mostly so there's director-types who set research directions and create grant opportunities, admin-types who push money around and track status, and most the work is done by those who submit successful proposals. I've had a couple smallish tasks for DARPA while I was at a gov lab.

They have a nice model. The program managers (those who set research directions) are fixed-term IIRC, so they have very little incentive to politic, and instead can focus on seeing their pet program through to completion in the given time / funding.

One of their main "jobs" (aside from above), is to be an advocate for emerging tech among the military and civilian industrial partners to make sure it actually "becomes something".

To work at DARPA in this capacity usually requires a lot of successful R&D program management experience and some sense of grand vision. To work in a lesser, administrative capacity, including interacting with research partners, requires just a tad less, but on the average they've been exceptional, intelligent, and responsive partners for all the work we've done for them.

Program Managers are fixed term - up to 3 2 year terms (though Director Tompkins generally doesn’t like PMs to be around longer than 4 years - see section 1101 of the Strom Thurmond NDAA for more details about the hiring authority).

I don’t know about the admin vs director types split you’re talking about (at least in the PM ranks). Office directors generally provided top cover and some very sweeping research directions, but as a PM it was your job to come up with research programs that were roughly compatible, convince the office director it was, and then manage the technical execution with the performers and doing dog and pony shows when the pentagon called.

How ironic that Strom Thurmond had anything to do with any limits on tenure for such posts...

This guy was in grifting senate/etc for 48!!!!! YEARS...

https://www.ranker.com/list/facts-about-strom-thurmond/micha... (I do not know if these are true - but its not the first time hearing about some of these allegations)

Yes. Most of the work is not done in the DARPA building. Generally federal contractor sites. The daily work in the building is phone calls, reviewing papers, email, building powerpoint slides, and trying to come up with the next program. In my time, most PMs managed between 3 and 5 programs, some of their own creation, and some inherited from outgoing PMs (term limit + federal contracting timelines means generally the originating PM is not around to see a program through to its conclusion)
Submit.

Hear absofuckingloutely nothing back.

Get paid obscene levels of money.

Repeat.

DARPA programs are typically not known for large sums of money, especially compared to other defense sectors.
They give a lot of money to things that are yet to be proven.

This item has no comments currently.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal