Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Datadog (París) en ene 2024
Entrevista
Il y a 4 étapes et c'est long. Quelles que soient tes compétences, il est essentiel de bien connaître leur plateforme et de bien maîtriser leurs technologies.
alors c'est un peu une perte de beaucoup de temps si tu n'as l'experience avec leurs technologie, ils vont oas te prendre.
Entrevista normal
Solicitud
Envié una solicitud electrónica. El proceso duró 2 meses. Acudí a una entrevista en Datadog (Boston, MA) en jun 2024
Entrevista
The interview process involved:
1.) phone screening with recruiting team/HR
2.) teams call with hiring manager
3.) technical skill assessment
4.) interview with two other managers
5.) onsite interview
I was involved in steps 1-4, then got a rejection notice after step 4. The process up until this point took 2-2.5 months; however, this was primarily due to the HR person taking several weeks to respond for each round.
Preguntas de entrevista [1]
Pregunta 1
Question 1 - Integration Not Working
I’m not seeing the metric system.disk.directory.file.bytes in my Datadog account. I’m trying to monitor our application directory and I have installed a Windows Datadog Agent onto our environment. This is what we have so far for the integration:
init_config: instances:
- directory: "C:\Users\projects\prod-application"
I know I saved the configuration, directly after saving it I then checked the platform, and I’m still not receiving the metric. I tried uninstalling the Agent and setting up the integration again, but it tells me:
2021-07-19 08:06:22 UTC | CORE | INFO | (pkg/metadata/host/host.go:169 in getPublicIPv4) | No public IPv4 address found
2021-07-19 09:12:05 UTC | CORE | ERROR | (pkg/util/azure/diagnosis.go:21 in diagnose) | Azure HostAliases: unable to query metadata endpoint: status code 404 trying to GET http://111.254.167.255/metadata/instance/compute/vmId?api-version=201 7-04-02
2021-07-19 09:12:05 UTC | CORE | ERROR | (pkg/util/azure/diagnosis.go:21 in diagnose) | Azure HostAliases: unable to query metadata endpoint: status code 404 trying to GET http://169.254.169.254/metadata/instance/compute/vmId?api-version=201 7-04-02
2021-07-19 09:12:17 UTC | CORE | WARN | (pkg/autodiscovery/providers/file.go:192 in collectEntry) | C:\ProgramData\Datadog\conf.d\directory.d\conf.yaml is not a valid config file: yaml: line 3: found unknown escape character
2021-07-19 09:12:20 UTC | CORE | INFO | (pkg/serializer/serializer.go:374 in sendMetadata) | Sent metadata payload, size (raw/compressed): 1331/379 bytes.
Can you let me know what I’m doing wrong so I can get this integration up and running?