Software Engineer
BelozFi, Remote (MX)
What you will do
- Own product / features end to end with the Tech Lead and functional heads: scope, design, build, ship, measure
- Work across a set of microservices platforms composed of: TypeScript/Node services, Go edge services, Python data and underwriting services, React Native mobile, Next.js web
- Diagnose production issues across service boundaries using evidence from logs, traces and data
- Collaborate closely with the data team on pipelines, experiments and underwriting logic
- Explain technical trade-offs plainly to non-technical stakeholders
Tech stack
- Backend: TypeScript on Node.js (Express 5, Sequelize, tsyringe DI, zod). Go (chi, Gin, GORM) for the gateway, auth, bill pay and remittances. Python (Django/DRF, FastAPI, SQLAlchemy) for contracts, underwriting and ETL
- Frontend: React Native with Expo for mobile. Next.js and React for web
- Infrastructure: AWS, postgres, sql, bedrock, datadog, github, linear
What you need
- Strong production experience with TypeScript/Node and at least one of Go or Python, and genuine comfort picking up the other.
- Solid SQL and relational modeling. You can read a slow query plan and fix it
- Experience building and operating microservices: queues, idempotency, retries, failure modes between services
- Hands-on AWS experience (ECS, SQS, Lambda or equivalents). We run everything there
- Proper use of AI. This role is not for AI skeptics, and it's not for people who outsource their thinking either
Overview / About us
Beloz is a Y Combinator and Latitud backed financial health platform in Mexico, led by people from Capital One, Bain & Company, Konfio and DiDi. We exist to measurably improve our customers' financial lives, and in a short time we've reached strong traction with exceptional consumer outcomes and unit economics. We build AI-native: every person here works with AI tools daily, and we only hire people who are substantially AI literate.
What matters most
We hire for problem solving first, and we mean it broadly. It's the ability to take an ambiguous feature request or a cross-system issue, understand how things actually work today, reason about trade-offs, and arrive at a design that is correct, simple and holds up in production. It not only covers debugging, but also deciding what to build, what not to build, and how a change fits into a platform with many moving parts. We expect the caliber of someone who can be handed a goal rather than a spec and own the path to it. Technical depth is the second filter. It amplifies good judgment, it doesn't replace it.