Responsibilities:

- Self-Operation Product
- Build and run the driver booking platform end to end — onboarding flows, reservations, payment integrations, releases, bug fixes, and uptime.

- Partner with the EV Workshop Project Leader, who owns selecting and implementing the workshop management system; you own integrating it with the booking platform, telematics, billing, and the dashboard.

- Spend time with drivers and the operations team on the ground, turn what you see into requirements, and ship improvements in short cycles.

- Keep the platform deliberately simple, and flag early when a feature needs specialist help rather than a workaround.

- Systems Integration

- Map how data moves today between operations, fleet and telematics, ride-hailing platform data, accounting, and Google Workspace — and find where it breaks.

- Replace manual handoffs with APIs, webhooks, and automations.

- Migrate operational data off spreadsheets into our internal operations portal, one prioritized module at a time, so the portal becomes the system of record.

- Performance Dashboard & Data

- Take ownership of the existing performance dashboard covering financial, driver, and platform performance and the P&L.;

- Own the data pipelines behind it: sources, refresh, data-quality checks, and documented metric definitions.

- Build new views as the business asks new questions. Finance owns the accuracy and sign-off of the financial figures; you own making sure the dashboard shows them correctly.

- Cross-Team Product Ownership

- Work day to day with operations, finance and accounting, and commercial; translate their problems into clear, scoped requests.

- Maintain a single prioritized roadmap of internal and self-operation product work, agreed with the CEO.

- Train users, write the documentation,



and make sure every system you build can survive without you in the room.

- Tools, AI & Automation

- Evaluate new tools and AI capabilities and bring in the ones that remove real work — document processing, driver onboarding checks, reporting.

- Keep the tool stack tidy: who has access to what, what each tool costs, and what can be retired.

Requirements:

- 0–3 years of experience. A degree in computer science, engineering, or a related field is welcome, but not required — proof matters more than credentials.

- A portfolio of things you have built and shipped: side projects, hackathon builds, internal tools, open-source contributions. We will ask you to walk us through one, including what broke.

- A clear understanding of how software systems fit together — REST APIs, webhooks, authentication, relational databases, and SQL.

- Hands-on with a modern builder stack: AI app builders such as Lovable, Supabase/Postgres, GitHub, and AI coding assistants. Comfortable reading and writing TypeScript/JavaScript or Python.

- You use AI tools every day, and you can tell quickly whether a new one is useful or hype.

- You can explain a system to a workshop supervisor or an accountant in plain language, and you are comfortable pushing back when a request doesn't make sense.

- Working comfort with basic financial concepts — revenue, cost, margin, the structure of a P&L; — or the willingness to learn them fast.

- Ownership: when something breaks in production, you are the one who fixes it and tells people what happened.

- Bilingual Spanish/English required. Our internal teams work in Spanish; shareholder counterparts and much of our technical documentation are in English.

- Based in Monterrey, working on-site alongside the operations team; occasional travel to Mexico City.

📌 Product & Systems Builder (Monterrey)
🏢 Nir-yu
📍 Monterrey