Technical Lead

Role: Technical Lead – Applied AI Scrum Team

Location: Mexico City (Hybrid – 3 days in office)

Employment Type: Full-Time

Reports to: Applied AI Engineering Leadership

Experience

10+ years in software engineering, incl. 2+ years in a technical leadership role

Role Summary

The Technical Lead owns the tactical technical decisions for the team and is the hands-on anchor for architecture, code quality and delivery. This person sets the technical direction, unblocks the team, and ensures the product is built to scale across markets on a cloud-agnostic platform.

Key Responsibilities

• Make day-to-day tactical technical decisions and drive architecture for the Virtual C-Suite product.
• Lead design and hands-on development of scalable microservices in Java / Spring Boot and AI capabilities in Python.
• Own engineering quality – design reviews, code reviews, coding standards, and technical debt management.
• Guide integration of Azure AI Foundry / LLM models (Claude, GPT-4.1, Mistral) into product workflows.
• Ensure robust CI/CD, observability and Kubernetes-based deployment across Azure (and emerging AWS) environments.
• Mentor senior SDEs and QE, and collaborate with the TPM on roadmap, estimates and exit criteria.
• Champion autonomy – enable the team to independently plan and deliver roadmap priorities.

Must-Have Skills

• Strong hands-on Java / Spring Boot; solid Python for AI/LLM integration.
• Microservices, REST APIs, event-driven design; NoSQL / document databases.
• Cloud-native engineering on Azure (AWS a strong plus); Kubernetes and CI/CD pipelines.
• Proven experience taking products from concept to production at scale.
• Excellent technical judgement, communication and mentoring ability.

Nice to Have

• Experience building agentic / GenAI applications and RAG pipelines.
• Databricks and data-platform experience; fintech / payments domain exposure.
• Comfortable operating in a fully autonomous team that owns delivery end-to-end.
• Strong fundamentals in the relevant discipline and a good culture fit – collaborative, ownership-driven and outcome-focused.
• Able to work in a cloud-agnostic environment (Azure today, expanding to AWS).
• Hybrid working – 3 days per week from the Mexico City office, with emphasis on in-person collaboration during the early build phase.
• Clear communication and the ability to move fast without compromising engineering quality.