About me
I'm Sergio Toshio Minei. For 16 years I've been taking other people's hardest problems and turning them into software that works. Here's who's behind the code.
How I work
A spreadsheet with one reader. A client had built their quoting tool in there: carefully done, full of formulas and edge cases, and only its author understood it. For everyone else at the company it was useless. My team and I sat down and worked through it. They sold property and every unit was paid for differently: the size of the down payment moved the discounts, buyers could pay months ahead, and the term depended on what was left. One wrong number could end in a lawsuit. We turned it into software that matched every result and that their sales team could actually use.
I know how to decide what to build and how to implement it. Whether the code comes from my keyboard or from the AI I'm directing, I review all of it, test it, and hold it to a high standard of quality.
Here's where my attention goes while a product takes shape:
- Scope by value. I propose a focused scope from the start: the work that moves the product most, first, without drifting sideways. That's where a team's time pays off best.
- Architecture and data model. Every business and every problem wants a different shape, so I read the context first. The architecture I propose comes out of that, fitted to the product in hand.
- Product judgment. Programming isn't where I stop. I pitch features and I have opinions on the ones I'm handed. Designing from scratch isn't my strength, but building products taught me to read a design well.
- Code the team can read. In a team you spend more time reading code than writing it. So I push on clear names, small functions with one job each, and reusing what's already there.
- Error handling. I narrow the failure down to the exact point where it breaks. Then I diagnose it, dig through AI and the web both, and stay on it until the cause is out.
- Learning on purpose. Tech doesn't sit still, so I give real time to what's new: docs, tools, projects of my own. What I'm working on lately is on my GitHub.
I take responsibility from the problem through to working software.
What I look for
I'm open to a full-time role or a defined project, as a software developer or as a tech lead.
I want us to discuss everything openly, then get behind the decision we make. That includes me.
Here's what I look for in a role or a project:
- Impact you can see. I want what I build to matter to the people using it: real problems, solved, and a visible difference in someone's day.
- More than my job title. It's why startups suit me: a clear job, plus the go-ahead to step outside it. I pitch features, get into design questions, and weigh in on sales or marketing when that helps.
- Freedom with responsibility. I'll keep a schedule, as long as there's slack inside it for the life around the work. Judge me on what I deliver, not on hours logged at a screen.
- Trust from day one. Trust that I'll do good work, and room to do it. I hold to what I commit to, and when something won't make it, you hear that early.
- Leadership with a purpose. The team hits its goals and, along the way, each person hits their own. I like backing my people, and I know I led well when they pass me.
The person
I'm based in Lima, Peru (GMT-5), and I work in Spanish and English. I enjoy being at home. A good day has a quiet stretch of reading in it, time with family, and a meal out for something I've been craving. I read a lot of manga, plus fiction and nonfiction: One Piece is my all-time favorite, and on the book side it's the Cosmere saga. A good series pulls me in without much resistance too.
That quiet side sits next to the rush of putting something live and waiting to see how people take it. The best part comes right after: someone tries what we built and the thing that was blocking them is gone.
Starting things marked me early. I've founded companies, and what stayed with me is a bit of everything: selling, marketing, design, making content. I like learning new things and trying out technologies, and I usually get there by poking at something until it breaks, just to see why it worked.
Learning something new costs you, and being wrong genuinely stings. I'll take it anyway: be wrong fast, fix it, come back a little better. The alternative is standing still in what I already know.
Where I've worked
Startups, agencies and corporations are some of the places I've worked. Here's a short list of the most recent ones.
- JobLeap, senior engineer, then tech lead. Since May 2024.
- AloHome, senior frontend and tech lead. 2021 to 2023.
- Webveloper (now Bizwise), frontend engineer. 2019 to 2021.
- Wozzii, co-founder, CEO and lead programmer. 2019 to 2021.
- Bildin, co-founder. 2016 to 2019.
- Linnso, co-founder and CEO. 2013 to 2018.
- Scotiabank Perú, full-stack developer as a contractor via Stefanini. 2018 to 2019.
For the full detail, see my LinkedIn profile.
Camino Independiente
Before this, I hosted Camino Independiente where I talked about entrepreneurship and going your own way. It's a good window into how I think about building things.
Listen on SpotifyLike how I think? Let's talk.
If this sounds like the kind of person you want on the problem, the next step is easy.
Let's work together