You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Posted 5 days ago
Requirements and responsibilities
Why this role exists:
- Today the CTO owns solution design, delivery planning, and technical execution across the platform.
- This role is the person he delegates that to.
- You will be the CTO’s right hand: turning business intent into architecture, architecture into committed scope, and committed scope into delivered software.
- You own the how and the when, with a level of autonomy that only works if you are senior enough to be trusted with it.
- This is not a coordination role.
- You are expected to have opinions on architecture, defend them, and be accountable for what ships.
What you will own:
- Solution architecture: target-state and integration design across our capability areas, including payment processing and acquiring, payment orchestration, core banking, ledger and merchant tooling, risk, compliance, and identity.
- API contracts, integration patterns, technical trade-offs, and the decisions behind them.
- Delivery: the path from roadmap to production, including scope definition, prioritization, committed delivery cycles, dependencies, risks, and milestones.
- You keep delivery predictable and honest.
- Our development partner: most engineering is executed by an outsourced development partner.
- You own that relationship technically: scoping statements of work, reviewing their architecture and process, and holding them to what was committed.
- Translation: commercial, operational, and regulatory needs arrive as problems, not specs.
- You convert them into requirements, user stories, process flows, and acceptance criteria that an engineering team can build against without guessing.
- Hands-on technical work: you review code and build proof-of-concepts.
- On exceptionally complex work, you implement it yourself.
- You stay close enough to the system to know when you are being told something that is not true.
Requirements:
- 8+ years in software, including engineering, architecture, and delivery, with a meaningful part of it spent owning systems, not just coordinating them.
- Deep experience in cross-border payments, acquiring, and/or payment orchestration.
- Strong software engineering background: you read and review code, design distributed systems, and reason about integrations, failure modes, and trade-offs.
- Proven track record owning complex platforms end to end, from problem to architecture to production.
- Program and project delivery discipline: multiple parallel initiatives, real deadlines, and real dependencies.
- Experience working with outsourced, nearshore, or partner engineering teams.
- Excellent written communication: much of your output is written, including specs, decisions, and diagrams.
- Fluent Spanish and English.
- Based in Latin America, working hours compatible with São Paulo.
Bonus:
- Portuguese.
- Card schemes, tokenization, stored credentials, 3DS.
- Core banking, BaaS, ledgers, and reconciliation.
- Crypto and stablecoin flows, including on/off ramps and treasury.
- Multi-market regulatory environments across LatAm.
What we are looking for:
- Ownership: you take the problem, not the ticket.
- Judgment under ambiguity: you decide with incomplete information, and you are explicit about what you do not know.
- Pragmatism: the right architecture is the one that ships and survives.
- Directness: you challenge decisions, including the CTO’s, with reasoning, and you commit once the call is made.
How we work:
- Remote, full-time employees.
- Small senior team with direct access to the CTO and CEO.
- Plans are built jointly and in the open; once a decision is made, we execute.