Senior Software Engineer Interview Experience - Argentina
Process
- Interview with recruiter
- Offline coding challenge + written questions
- Interview with the manager/tech lead
- Spoken technical interviews
A final offer was extended by the recruiter. I rejected it because they offered an incredibly low salary. I would avoid them at all costs.
Questions
-
What is the difference between a contributor and a maintainer?
-
When do you ask for help?
-
What is a deadlock?
-
What is a hashmap?
-
How does binary search work and what would you test?
-
What happens when you execute a query?
-
What is the hardest and easiest part when executing?
-
How does a database execute a distributed sort?
-
How does a database execute a distributed join?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Elastic Senior Software Engineer role in Argentina.
Success Rate
Elastic's interview process for their Senior Software Engineer roles in Argentina is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Elastic's Senior Software Engineer interview process in Argentina.
Elastic Work Experiences
- 5.0Great company to work for!Senior Software Engineer • Current EmployeeBuenos Aires, Buenos Aires, ArgentinaOctober 3, 2024Pros: - Great work-life balance - Interesting problems to work onCons: - Pay not up to par with FAANG or similar companies
- 3.0Good work-life balance, but management struggles with distributionSenior Software Engineer • Current EmployeeVancouver, BCOctober 1, 2026Pros: Work-life balance. Compensation. Top technologies.Cons: Distributed work is hard to manage.
- 3.0Time to refocus on the productSenior Software Engineer • Former EmployeeJanuary 15, 2023Pros: - Great benefits (2x Fridays off per month for the entire company, 4x months paternity leave, SANS training, etc.) - Lots of smart coworkersCons: - Too many stakeholders to align across a complex organizational structure to get traction with major projects. - Sunk-cost fallacy affecting decisions around product strategy and NIH syndrome. - Too many meetings full of corporate cheerleading. - Layoffs were poorly handled.
