Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en Dlocal en feb 2026
Entrevista
The interview was only 2 steps: a Q&A tech assessment, and a product/behavioural assessment.
I got a very good impression overall of the people who interviewed me, but the outcome has been delivered without any feedback.
I believe that not giving feedback to a candidate is something that gives a negative impression of the company, because this leaves a scar in candidates' memories, and this burns the bridges with this candidates should dLocal being interested in hiring them later.
Very unprofessional behaviour.
Preguntas de entrevista [1]
Pregunta 1
Tech assessment was mostly about databases, basic and advanced concepts, performances tradeoffs, etc.
Product assessment: relationship AI, past experiences, and regular behavioural questions.
Solicité el puesto a través de un captador. Acudí a una entrevista en Dlocal (Madrid) en feb 2026
Entrevista
The interview process at dLocal was impressively dynamic and fast. It consisted of four clear stages:
1. HR Interview: Initial screening and culture fit.
2. Technical Interview: Deep dive into specific skills and problem-solving.
3. Team Interview: Great opportunity to meet potential colleagues and see the team chemistry.
4. VP Interview: High-level discussion regarding strategy and vision.
The entire team was very friendly and well-prepared. It was clear that the interviewers had reviewed my background beforehand, as they asked insightful and relevant questions. Highly professional experience overall.
Preguntas de entrevista [1]
Pregunta 1
Golang Technical Questions
General Concepts & System Design:
what is a software pattern you have used recently?
Explain Connection Pooling, Circuit Breaker, Timeouts, and Retries with Backoff.
Databases: Experience with SQL vs. NoSQL. Define a Primary Key. Explain Master-Slave architecture
AWS/DynamoDB: What types of keys does DynamoDB use? What is a partition key?
Architecture & Patterns: How do you implement Idempotency and Rate Limiters?
Team & VP Rounds:
Deep dive into past experiences.
Specifics on Observability, Rollout/Deployment strategies, and Incident Management.
Discussion on team processes, ways of working, and personal motivation for joining dLocal.
Envié una solicitud electrónica. Acudí a una entrevista en Dlocal en oct 2025
Entrevista
The first interview is a standard screening with HR. The recruiter was kind but many questions were responded with "it depends on the team, in next steps you can ask the technical team to provide more details".
After that, I had a technical interview with an "Architect". It was a 1 hour interview where the architect would ask you general questions about Golang, system designs, technologies you have used. Honestly the interview went great and I answered almost all questions correctly, but I received a rejection email (written with an LLM but anyway) telling me that they won't move forward because "I dont have professional experience with Kafka nor CQRS". Even if I don't have professional experience, I know about those technologies and I could respond fine to the questions..
Advice for the company: if you have a hard requirement about some technology, PUT IT IN THE JOB OFFER. Don't make candidates waste their time.
Preguntas de entrevista [1]
Pregunta 1
Golang:
- what is a pointer, operations on pointer (* and &)
- what is a goroutine.
- how to communicate between goroutines.
- what is a channel. when is blocked, buffered vs non buffered.
- what is an array. what is a slice, differences.
- new() vs make()
- what is an struct. can you add a method to a struct? difference method vs function
- what is an error. how you handle errors in golang.
General concepts:
- Apart from Singleton, tell me a recent sofware pattern you have used.
- connection pooling.
- Circuit breaker. The states of the circuit. How to implement it?
- Timeout, Retry with backoff.
- CAP Theorem.
- What SQL databases you know? and about NoSQL?
- what is a primary key.
- Idempotency, how would you implement it.
- Rate limiter, how could you implement it.
- Load balancer.
- CQRS.
- Messaging, Kafka.
- DynamoDB. What types of keys. What is a partition key?
- Strong consistency, eventual consistency.
- Database master-slave. Can you use a slave/readonly replica for everything (no, because it has a replication lag).
