@allenholub@unclebobmartin And monorepo gives you the best flexibility of the two worlds: a modularized application (where you can have good or bad architecture, depending on the seams you created), while also being able to change deployment according to your need.
@dwlz Instead of coding so much more, you can now spend more time talking to users to know what to build and improve accuracy! I’m totally on your team. Same features, faster and more complete.
It's worse... it's on THE AVERAGE of human code. 😂
But there are softwares... and there are softwares...
I think people who say this (that they don't read the code), work on very simple applications CRUD-like (ecommerce, CRMs, etc).
People who work in high data volume critical systems would never do that... NASA would never do that.. SpaceX would never do that...etc
There’s a lot that happens behind this API call in an acquiring company. They are automating a lot of processes (talking with credit card brands, the bank, etc), have security mandatory infrastructure (it’s regulated), provide infra with a huge SLA, can’t loose data, must process this huge complex process in milliseconds, have to store data for a long time due to regulatory needs, KYC, support, etc.
Also, when I worked at StoneCo and discovered about this industry for the first time I discovered that lots of this price goes to the banks and the brands (visa, Mastercard, etc). The acquiring company keeps a tiny amount of this as real revenue.
If something is fast and easy, doesn’t mean it doesn’t involve a lot of work to get at this state
RWS Integration - Product Builder
B2B SaaS companies lose deals and delay revenue because enterprise integrations take months. Our platform makes them happen in *under an hour*.
Engineers love the technical power. Now we need an exceptional first product hire to turn deep customer problems into intuitive, high-impact experiences that drive real business outcomes — faster onboarding, faster go-live, and faster revenue.
This is a founding role. You’ll work side-by-side with the founders in a small, high-trust team to shape the product from first principles: deeply understanding customer pain, breaking it down to fundamentals, and translating it into clear, buildable solutions with excellent UX taste.
No large org processes. No existing playbook or metrics dashboard. You will define how we discover problems, prototype solutions, and ship what actually moves the needle.
What you’ll own:
- Lead customer discovery and problem framing with Heads of Product, Partnerships, CTOs, and end users
- Decompose complex integration and onboarding challenges into elegant, first-principles solutions
- Rapidly prototype UI/UX flows and product concepts
- Collaborate closely with engineers to ensure solutions are technically sound and feasible
- Shape ambiguous ideas into specific, high-quality blueprints that deliver measurable value
What success looks like:
In the first 6 months, you will have deeply mapped key customer segments, shipped multiple impactful improvements, and helped turn early product strengths into closed lighthouse customers.
In 12 months, you will have established our core product direction and shaping process, setting the foundation for the next hires and scalable growth.
This role is for you if:
- You are a rigorous first-principles thinker who excels at breaking down messy problems
- You have strong taste in interfaces and can move quickly from insight to prototype
- You communicate clearly across technical and business audiences
- You thrive in early-stage ambiguity and want to build something foundational rather than optimize an existing machine
- You’re energized by in-person collaboration in São Paulo and working directly with founders who value depth over process
This role is not for you if:
- You prefer structured roadmaps, heavy project coordination, or big-company PM frameworks
- You mainly enjoy optimization, metrics dashboards, or execution management over invention and shaping
- You need a large team or extensive support systems to make progress
Location
📍São Paulo – full-time, in-office. We build fast and together; this is not a remote role.
Compensation
R$ 30,000 per month base + top-tier healthcare. Meaningful equity is available (performance-based after initial impact or negotiable upfront for exceptional candidates coming from partner-level roles or higher base salaries). Total compensation will be discussed directly with the founders.
How to apply
Email [email protected] with a short note on why this problem and role excite you. Include one example of how you turned a complex customer or user problem into a simple, elegant product solution. We review every application personally.
You can look at a problem and decompose it in its fundamental parts. Its abstract, yes, it will change over time as you understand it better.. but having a mental model of the problem your company is solving (or trying to solve) doesn’t look like a waste to me.
We are currently solving the time to revenue problem of B2B companies. Understanding how the sales cycle and onboarding works and decomposing they further we arrived at the enterprise integrations as the root cause of both the long sales cycle (maybe half of it) and the onboarding (almost all of it). It’s almost impossible to hire some product person who already know this in a deep level already.. but it’s easy to teach the experience to a smart hire who has good problem solving skills.
I think it’s the founder role to be the owner of this model at any given time and communicate it to the team on a daily basis. A startup pre PMF must find a relevant problem with a big market, solve it in a way that is a magnitude better than the current options and learn how to sell it. The whole team must understand the problem in detail for any of this to work without the founder being responsible for everything.
I’m exactly hiring this first product person now. Before I started looking I sat down to write exactly what I want, what this person will be responsible for and what are the core competencies for it. I arrived at the following: the person must be an excellent problem solver with good communication skills and taste for good interfaces. They must know how to work from first principles. All the other skills can be learned later if they don’t have them. This is because they must understand the problem we are solving for our customer in a deep, first principles way. Then, they need to talk to customers about the pain, prototype this into UI/UX and have the taste for what is good enough. We are pre PMF, so I think this is what is needed at that phase. You don’t have many users and need to go from 0 to 1. The only way you can do this confidently is through first principles. This is the definition of an inventor to me.
People usually hire product people from other big companies that have a completely different set of skills/expertise. In a big company post PMF the product job is no invent, it’s to improve, look at metrics, etc.
@nateberkopec Nate, I think about this a lot too. Maybe it should exist a way to measure the real output of our software: deterministic full automated pentests, performance, cost, etc for each commit?
Agreed. Most people never had to maintain and change software, reliably, for long periods of time.
They don’t have enterprise customers that depends daily on their products.
Although, I’m bullish to see the new forms of verification that will emerge, so we can in the future have deterministic, automated ways to review software in terms of performance, security, architecture, cost, etc.
I can’t stop dreaming of a future where this will be the norm, that we measure fully the output of our products. Until then, let’s keep reviewing every LoC and make something people want and can rely on.