Mercado Libre

• Competitive compensation at the time of hiring, especially for candidates who negotiate their initial offer effectively.
• Opportunity to work on large-scale systems and high-traffic platforms.
• Exposure to modern technologies, distributed architectures, and complex engineering challenges.
• Strong brand recognition that can be valuable on a résumé.
• Collaboration with talented engineers and exposure to a fast-paced environment.

• Salary growth after joining can be limited compared to the increasing workload, responsibilities, and expectations placed on engineers.
• Performance reviews may feel highly dependent on the perception and priorities of the direct manager, leading to inconsistent experiences across teams.
• Career progression, compensation decisions, and performance evaluations are often heavily influenced by project leadership.
• Frequent on-call rotations and an expectation of availability outside regular working hours can significantly impact work-life balance.
• The workload can become difficult to sustain over time, particularly when operational responsibilities are combined with aggressive delivery expectations.
• Organizational priorities and management directives may change frequently, creating uncertainty about expectations and success metrics.
• Teams can receive mixed messages regarding performance indicators, productivity goals, and tool adoption, making it difficult to understand what is truly expected.
• Strong emphasis on KPIs and activity metrics can sometimes encourage optimizing for numbers rather than focusing on sustainable engineering practices and long-term outcomes.
• During my time at the company, there was a growing emphasis on AI-assisted development. While these tools can be valuable, their adoption occasionally felt driven by usage metrics rather than clear engineering or business objectives.
• Cross-functional alignment between management layers can be inconsistent, resulting in conflicting guidance and unnecessary friction.
• A significant portion of the workweek can be consumed by meetings, status updates, and coordination activities. Many of these interactions could be handled asynchronously, allowing engineers to spend more time creating value.
• Finding uninterrupted time for deep technical work can be challenging. The volume of meetings, operational demands, and context switching often limits opportunities for engineering, technical improvement initiatives, and innovation.
• Engineers may spend a substantial amount of their time reacting to operational priorities rather than building, improving, or refining software solutions.
• The culture can feel political at times, and navigating relationships with stakeholders may have a significant impact on one's overall experience.
• Long-standing organizational dynamics can make it difficult to challenge existing approaches or provide dissenting opinions without careful consideration.
• Employees may feel the need to be highly cautious in day-to-day interactions, particularly when dealing with sensitive topics, performance discussions, or cross-team disagreements.
• The combination of frequent meetings, on-call responsibilities, shifting priorities, delivery pressure, and performance metrics can contribute to burnout if not managed carefully.

Improve consistency in leadership communication, make performance evaluations more objective and transparent, reduce the overreliance on activity-based metrics, and create more protected time for engineers to focus on technical work.

Encouraging sustainable workloads, clearer expectations, and stronger alignment between leadership layers would significantly improve both employee satisfaction and engineering effectiveness.