Pros: Good pay, nice benefits, a nice, beautiful office, interesting problems to work on, and a successful company. If you manage to keep your head down, you can probably coast pretty easily here.

Cons: Code quality is quite low. Many, if not most, systems at Datadog were built by one-man "teams" of engineers, often as hack-day side-projects, rapidly launched to production well before they were ready. Applications are almost never built in a "normal" way, and there are whole applications without a single test. As a consequence, systems break frequently, and no one even knows how they're supposed to work. As a competent developer, you'll probably notice this in your first two weeks, but you'll also soon discover that there are many sacred cows at Datadog. Despite their obvious deficiencies, the design of these systems is largely non-negotiable. Most of your work will consist of a constant barrage of surprisingly crude DevOps changes just to keep the thing running. For many teams, most work is unplanned and very stressful because it's done in response to outages (we have 3 or 4 outages every day, so half your day will be spent working on "urgent" problems). Backend engineers also participate in the on-call rotation, which ends up being once every 4-6 weeks and lasts for a week at a time. You will be responsible for 90% of the systems, even though you know nothing about them. Because everything is mostly broken, you will be paged every hour. Also, you will get to experience the joys of working with an international team, where because almost every change at Datadog results in an outage, the developers in France will consistently wake you up at 4 AM every morning. The company has grown rapidly, but management has not kept pace. Team leads have no experience in leadership, do no planning, and make irrational, heavy-handed decisions. Concerns are not taken seriously, and you'll be treated like a junior engineer regardless of your prior experience.

Pros: I get to work with smart, conscientious people. The compensation is very good, and I think the core product is quite good (there's a reason people pay for it). I enjoy most days at work, despite my complaints below.

Cons: Virtually every developer at Datadog shudders when they hear the word "Bazel". Our approach to developer experience is so, so, broken. There's an expectation that people should build new products in (one of the several) large monorepos, but actually getting things done in those repos is brutally slow. Just launching or testing your backend service involves waiting ages for Bazel to compile a ton of unrelated code. On top of that, we have to use a lot of bad, underdocumented, proprietary developer tooling. If you want to spin up a new REST service/Postgres instance/whatever, expect everything to take 5-10x more effort and time than it would elsewhere. You will spend more of your time learning how to do things the some-internal-team way than actually solving business problems. Edit-compile-run loops are often an order of magnitude slower than they would be at other companies. This mess is sometimes kind of *interesting*, but it is definitely not a good way to spend software developers' time.

Pros: They take care of employees and are empathetic to needs.

Cons: A "hacker first" culture leads to a lot of bloat.