Full-Time

Technical Account Manager 2

Updated on 8/1/2026

Datadog

Datadog

10,001+ employees

Cloud monitoring, analytics, and observability platform

No salary listed

London, UK + 1 more

More locations: Dublin, Ireland

Hybrid

Hybrid workplace with travel to and from client sites; travel may be required up to 30% of the time.

Category
Sales & Account Management (1)
Required Skills
Chef
PHP
Kubernetes
Microsoft Azure
Python
JavaScript
Puppet
Ruby
Docker
AWS
Perl
Go
Jenkins
DevOps
Google Cloud Platform

Get referred to Datadog

See people who can refer or advise you

Requirements
  • The candidate must have a solid technical grounding and hands-on experience with IT Operations.
  • The candidate must have hands-on experience with AWS, Azure, or Google Cloud Platform.
  • The candidate must be comfortable with scripting languages such as Python, JavaScript, Ruby, Perl, Go, PHP, Chef, or Puppet.
  • The candidate must be skilled in using continuous integration and continuous delivery tools such as Jenkins or GitLab.
  • The candidate must be knowledgeable about containerization tools such as Docker, Kubernetes, or Rancher.
  • The candidate must be able to sit for up to four hours while traveling to and from client sites.
  • The candidate must be able to travel by automobile, train, or air up to 30% of the time.
  • The candidate must have previous experience working as a Technical Account Manager supporting mid-market or enterprise customers in the cloud space.
  • The candidate must have experience using Datadog or other cloud monitoring tools.
Responsibilities
  • Advise customers on technical support and product adoption in line with pre-sales, post-sales, and renewal processes.
  • Analyze each customer’s IT Operations environment regularly and provide recommendations to maximize Datadog’s value.
  • Advocate for customers by understanding their goals and use cases, then suggest process changes, product adoption, configuration changes, and additional features to meet their requirements.
  • Participate in and prepare for monthly and quarterly business reviews with customers.
  • Collaborate with Datadog’s product management, engineering, and technical services teams to help identify new features and products.
  • Continuously evolve best practices for technical product adoption and customer success.

Datadog provides a platform for monitoring and analyzing IT infrastructure, including servers, databases, and applications. The product works by collecting data from a user's cloud environment and displaying it in a single dashboard where teams can track performance, manage logs, and detect security threats. Unlike many competitors that offer fragmented tools, Datadog integrates monitoring, security, and analytics into one unified interface with a flexible pricing model based on data usage. The company's goal is to provide organizations with real-time visibility into their digital operations to ensure their systems remain reliable and secure.

Company Size

10,001+

Company Stage

IPO

Headquarters

New York City, New York

Founded

2010

Get referred to Datadog

See people who can refer or advise you

Simplify Jobs

Simplify's Take

What believers are saying

  • AI and LLM observability expands demand for production monitoring and cost control.
  • Cross-selling cloud cost, synthetics, and incident workflows deepens enterprise account expansion.
  • Global operations across North America, Europe, and Asia-Pacific support continued international growth.

What critics are saying

  • Jefferies cut Datadog to Hold after a 94% year-to-date rally.
  • At about 18x EV/2027 revenue, valuation leaves little room for execution mistakes.
  • Hyperscalers and adjacent platforms like AWS, Microsoft, Snowflake, and Atlassian pressure budgets.

What makes Datadog unique

  • Unified observability and security platform spans infrastructure, applications, logs, and cloud security.
  • Founded in 2010, Datadog is headquartered in New York City and publicly listed.
  • Its SaaS platform monitors cloud applications across servers, databases, tools, and services.

Help us improve and share your feedback! Did you find this helpful?

Benefits

Health Insurance

Dental Insurance

Mental Health Support

401(k) Retirement Plan

401(k) Company Match

Company Equity

Employee Stock Purchase Plan

Professional Development Budget

Hybrid Work Options

Flexible Work Hours

Paid Vacation

Growth & Insights and Company News

Headcount

6 month growth

-4%

1 year growth

0%

2 year growth

0%
OSMU
Jul 24th, 2026
How two French engineers built Datadog in NYC.

How two French engineers built Datadog in NYC. Key insights. * Rejection as motivation: Datadog was rejected by Y Combinator twice, which became a driving force to prove doubters wrong and build a successful company. * DevOps unification: The core idea was bringing developers and operations teams together on one platform to solve cloud monitoring challenges. * Cloud underestimation: The founders initially underestimated the cloud's explosion, thinking AWS was just a toy companies would never use. * Culture over documentation: Rather than writing down company values, Datadog's culture flows from the top through hiring, promotion, and leadership example. * AI-driven transformation: With AI accelerating product development, experienced developers now accomplish in days what once took teams of six months. From IBM to a cloud monitoring vision. Olivier and Alexey met at IBM Research in upstate New York during the late 1990s. Olivier arrived for an internship on internet protocols and planned to stay six months, but remained in New York for over 26 years. Both worked through the dot-com boom and bust - experiences that taught critical lessons about startup execution. Later, they built tech teams at an educational software startup that grew to 800 people, exposing them to significant DevOps and operational challenges. This experience revealed a gap: developers were essentially blind to production issues, while operations teams used separate, specialized tools. The bet: unifying dev and ops. Datadog was founded in 2010 with a bold premise - bringing developers and operations into one unified platform. At the time, "monitoring" was job-specific and reactive, with ops-only tools that developers never touched. The founders targeted this fragmented market from the bottom up. While they didn't fully grasp it then, their platform bet aligned perfectly with the cloud explosion. However, they massively underestimated cloud adoption, viewing AWS as an interesting experiment. Companies they talked to said cloud was a toy they'd never use - and then everyone adopted it. Building culture without a manifesto. Rather than posting company values on walls, Datadog's leadership deliberately avoided written culture statements, believing that if people need "don't be evil" written down, they shouldn't work there. Instead, the culture flows from leadership through hiring, promotion, and firing decisions. After 26 years with co-founder Alexey, Olivier remains deeply involved in product decisions - reading customer support requests, sales transcripts, and employee survey comments. This hands-on approach prevents sanitized information from hiding real problems. When he spots issues in raw feedback, he replies with simple questions that push the entire management chain to understand actual conditions rather than upward-facing summaries. Scaling product strategy with 20+ offerings. Datadog now operates approximately 20-25 products. Product expansion decisions come primarily from observing how customers use the platform - they build workflows and extensions that signal unmet needs. Beyond customer-driven features, leadership also makes strategic bets on emerging trends without waiting for explicit demand. AI presents a new challenge: the market moves too fast to wait for customer requests, so Datadog must get ahead of shifts and accept being wrong more often. Public company reality and AI's impact. Since going public in 2019, Datadog weathered a 65% stock crash when lockup expired during COVID, followed by multiple market cycles. Being public changes the rhythm of investor engagement - a few quarterly calls and a week of preparation replace the constant fundraising demands of private companies. The main concern shifts from survival to employee compensation through RSUs tied to stock performance. AI has fundamentally altered the company's approach. In December, Olivier stood before the engineering team and declared that within two quarters, they wouldn't write code by hand anymore. Experienced developers accomplished in days what previously took teams of six months. This inversion - from mostly writing to mostly automating - signals a structural reorganization. Smaller teams can now tackle problems that once required larger groups, though the exact future state remains unclear. European founders and the US market. Olivier emphasizes that while Europe now offers adequate funding, founders must pursue the US market as soon as product-market fit emerges. He doesn't believe the entire company needs to relocate - if there are two founders, typically one moves to the US. Datadog created its Paris office later for talent acquisition, hiring people unable to renew US visas or seeking to return to France. Conclusion. Two French engineers rejected by Y Combinator transformed that setback into fuel for building Datadog, the cloud monitoring platform that unified fractured developer and operations teams. Their journey reveals that culture, deep product involvement, and willingness to move fast on hiring and firing matter more than perfect planning. As AI reshapes how code is written, Datadog's strategy of leading rather than following demand shows the company is positioned to evolve with its customers.

OpenObserve
Jul 7th, 2026
Compare the top 10 Datadog competitors in 2026: OpenObserve, Grafana, New Relic, Dynatrace, and Splunk. Pricing breakdowns, feature tables, and migration guidance for DevOps and SRE teams.

Compare the top 10 Datadog competitors in 2026: OpenObserve, Grafana, New Relic, Dynatrace, and Splunk. Pricing breakdowns, feature tables, and migration guidance for DevOps and SRE teams. Latest From Its Blogs

NoBS.tech
Jun 11th, 2026
Datadog Bits AI pricing changed. Don't roll it out blind.

Datadog Bits AI pricing changed. Don't roll it out blind. Nick Vecellio Co-Founder and Principal Engineer, NoBS Yesterday at DASH, Datadog moved Bits onto the new AI Credits model, and the math changed dramatically. Under the old pricing, a Bits SRE investigation cost $25 at the committed rate, based on $500 per 20 investigations, or $36 on demand. Under AI Credits, Datadog's own telemetry across all accounts shows an average of 6.5 credits per investigation. At the committed rate of $500 for 500 credits, that puts the average investigation at about $6.50 per run. That is a 74-82% cut depending on how you were buying before. That's not just a discount; it's a signal. Datadog wants agentic operations to be something every engineer reaches for, not something teams save for sev-1s. And it's not just Bits SRE. The same AI Credits model powers Bits Chat, Bits Security, and Bits Dev, which means your organization now has a single consumption pool feeding four different agents. When a capability goes from rationed to routine, and from one front door to four, the question changes. It is no longer, "Can we afford to use it?" It is, "Are we using it well, and can we see who's using it?" Teams that have been through this curve before know how it ends. Log ingestion. Synthetics. Custom metrics. Every one of them started cheap and accessible. Every one of them punished organizations that skipped governance. The answer is governance, not hesitation. Get the access model and the visibility right up front, and the new pricing is pure upside. Start with access: Datadog's default roles need a closer look. The natural place to start is access, and this is where Datadog's default roles deserve scrutiny. The stock Standard role is much closer to Admin than it is to Read Only. That's fine when you're handing out trust, but it is overly permissive for anything with a meter on it. Datadog enables all AI Credits products by default for the Standard role. So if you've done nothing, most of your org can already spend from the credit pool. In its engagements, Nobs replace the three stock roles with a tiered framework purpose-built for cost-sensitive capabilities. With the Bits agent family now sharing a credit pool, Nobs has added a new piece to it. The tiered base roles. Read Only. Full visibility, zero write access, and zero cost exposure. This is the right default for most of the org. Limited Standard. Can create dashboards, monitors, and similar resources. Very low risk of incurring cost, but enough capability for day-to-day platform work. This is where most builders should live. SRE. Effectively Standard-level access plus additional controls, for the operators who need real reach into the platform. Admin. Full administrative access, granted sparingly. Very sparingly. Base tiers handle the broad strokes. Additive roles handle the exceptions. Datadog allows multiple role assignments where assigned permissions win, so an additive role grants a specific capability without promoting someone's entire access level. Its framework includes additive roles for User Management and Cost Management. As of this week, it also includes Bits Access. The Bits Access role is the cleanest example of why additive beats monolithic. A Read Only user granted Bits Access can run Bits agents and draw from the shared credit pool while remaining unable to edit any other resource in the account. You get adoption where you want it, scoped exactly as wide as you intend, with no collateral permissions dragged along for the ride. For what it's worth, granting Bits access to a Read Only user probably is not the right move. It is just a clean example of how additive roles work. What IS a good idea though - giving Datadog users with Incident Management seats access to Bits. Let's be realistic here, a real live incident is exactly where you want Bits in the picture. Watch the meter: AI Credits need cost visibility. Roles decide who can spend; cost monitoring tells you what is actually being spent before the invoice does. One honest caveat up front: as of launch, there are no real-time estimated usage metrics for AI Credits that you can alert on directly. That gap will probably close, but you should not wait for it. What you can do today is track AI Credit spend through your Plan & Usage page. The data isn't instant, but it is a world apart from the alternative, where the alternative is finding out about a runaway agent the same way teams find out about runaway log ingestion: Thirty days late. On an invoice. With no way to claw it back. Close the loop: measure adoption, not just spend. Here's where the governance story pays off twice. Bits activity is visible directly in the agent console, broken down by individual user. So alongside the cost data, you can answer the questions leadership will actually ask: Who is adopting these agents? Which teams are getting value? Is that new Bits Access role you granted last month being used, or sitting idle? Paired with cost visibility, you get both halves of the picture. Cost monitoring catches out-of-bounds spend before the invoice arrives. The console shows whether the spend you did incur maps to real adoption. That is the difference between a cost center you tolerate and a capability you can defend in a budget review. The point is not to slow Bits adoption down. The pricing change makes Bits agents accessible to everyone in your org. The framework above makes sure that access is deliberate: the right roles, granted additively; cost monitoring watching the meter; and per-user visibility closing the loop. None of it slows adoption down. It's what lets you say yes to adoption with confidence. If you want help mapping this framework onto your own Datadog account, that's exactly the kind of thing Nobs do. Reach out. FAQ: Datadog Bits AI, AI Credits & governance. Last updated: 2026-06-10 What are Datadog AI Credits? Which Datadog Bits products use AI Credits? Should every Datadog user get Bits access? Why use additive roles for Bits Access? Who should get Bits access first? How should teams monitor AI Credit usage?

Yahoo Finance
Apr 9th, 2026
Guggenheim upgrades Datadog to buy with $175 target after 14% YTD pullback

Guggenheim has upgraded Datadog to Buy with a $175 price target, viewing the stock's 14.33% year-to-date decline as an attractive entry point. The upgrade centres on Datadog's positioning at the intersection of cloud migration and AI deployment. Datadog reported strong fourth-quarter fiscal 2025 results, with revenue of $953.19 million beating estimates by 3.76%. Full-year revenue reached $3.43 billion, up 28% year-over-year. The company now has 603 customers generating over $1 million in annual recurring revenue, up 31% year-over-year. The cloud monitoring platform provider's shares currently trade near $114, well below the 52-week high of $201.69. Management has guided fiscal 2026 revenue to between $4.06 billion and $4.10 billion. Forty-three analysts rate the stock a Buy.

Yahoo Finance
Apr 9th, 2026
Datadog launches Experiments platform as shares trade 36% below analyst target of $181

Datadog has launched Datadog Experiments, an integrated platform for product testing and analytics that lets teams design, launch and measure experiments alongside real-time observability and business metrics. The offering targets enterprises previously relying on separate tools for experimentation, analytics and monitoring. The launch comes as Datadog shares trade around $116.50, down 12.9% year-to-date despite a 19.6% return over the past year. Shares currently trade approximately 36% below the consensus analyst price target of $181.52. By tying experimentation directly to observability and business metrics, Datadog aims to deepen its platform's role in customer workflows. However, profit margins have declined to 3.1% from 6.8% last year, and recent insider selling has been significant. Adoption rates among large customers will be key to watch.