AtEZCORPwe are a growing team focused on creating and changing the pawn industry as we know it today. We believe that our platform enabled lending and e-commerce solutions will revolutionize our ability to attract, engage and service our customers across the United States, Mexico and Latin America.

Join us now for an opportunity to be a part of a team that wants to provide access to short-term cash for every person – everywhere!

The Company:

Founded in Austin in 1989, EZCORP has grown into a leading provider of pawn loans in the United States, Mexico and Latin America. We are dedicated to satisfying the short-term cash needs of consumers who are both cash and credit constrained and providing an industry-leading customer experience.

What’s in it for you:

Ground Floor opportunity with EZCORP, a company with a start-up, purpose-driven mentality where innovative and agile problem solving are part of our DNA along with competitive compensation and benefits.

Address:

Guatemala

The Technical Product Owner partners with technical product managers and engineering teams to translate business product strategy into technical execution. Writes user stories independently using Given-When-Then (Gherkin) format and applies AI tools systematically to accelerate delivery. Coaches teammates on effective AI-augmented practices.

ESSENTIAL DUTIES & RESPONSIBILITIES:

AI-Augmented Delivery

• Demonstrate active AI fluency — use AI assistants (GitHub Copilot, Claude, or equivalent) as a daily co-engineer for code generation, test creation, documentation, and learning.
• Apply AI tools systematically to accelerate engineering work — code generation, automated test creation, refactoring, and code review.
• Use AI to accelerate research, requirements analysis, and stakeholder communication.
• Coach teammates on effective AI-augmented practices and contribute to team conventions for AI use.
• Validate AI-generated outputs before accepting them into deliverables.

Requirements & Story Writing

• Partner with technical product managers and business stakeholders on requirements gathering and analysis.
• Write user stories independently using Given-When-Then (Gherkin) format with clear behavioral context (Given = initial state/preconditions, When = actions/triggers, Then = expected outcomes).