The role
We’re looking for someone to become the day-to-day leader of product and engineering for our core product, .
Today, important product and engineering decisions still flow through our cofounder. That worked well to get us here, but it is no longer how we want to run the company. Your job is to change that.
You’ll work directly with the cofounder to understand the vision, then own turning that vision into shipped software. You’ll make product decisions, lead the engineering team, improve how we build, and make sure we consistently release high-quality work.
This is not a traditional Product Manager role. It is not a traditional Engineering Manager role either.
It sits between the two.
You’ll own the space where product, engineering, and execution meet.
What you’ll own
Your main responsibility is simple: Make it so the cofounder no longer needs to be involved in day-to-day product development.
● Turn ideas into clear product requirements.
● Lead engineering planning and help decide what gets built next.
● Make product and implementation decisions without waiting for the founder.
● Unblock engineers before work stalls.
● Review architecture, technical plans, and important pull requests.
● Coordinate QA, releases, and follow-up after launch.
● Improve our development process, tooling, and release reliability.
● Keep projects moving from idea through release.
When we’re doing our jobs well, the founder should be able to explain the problem we want to solve and trust you to handle almost everything else.
You’ll probably enjoy this role if…
● You naturally take ownership instead of waiting for detailed direction.
● You enjoy both product thinking and engineering.
● You care about the small details customers notice.
● You like improving systems as much as building features.
● You enjoy helping good engineers become more independent.
● You are comfortable making decisions with incomplete information.
● You are willing to challenge the founder when you believe there is a better solution.
● You want meaningful responsibility at a growing, founder-led company.
This role probably isn’t for you if…
● You need complete requirements before starting.
● You prefer coordinating work over making decisions.
● You only want to write code and do not want to lead people or product decisions.
● You escalate most important decisions instead of owning them.
● You want a large-company environment with mature processes already in place.
● You are uncomfortable working directly with a founder.
What success looks like
After one year, you will have:
● Built a product and engineering process that runs without constant founder involvement.
● Helped the team ship faster and with less confusion.
● Improved the quality and reliability of our software.
● Made releases predictable and low stress.
● Helped engineers take more ownership of their work.
● Shaped the product alongside the founder.
● Built systems that can support a larger team and a growing customer base.
Most importantly, should be able to keep shipping excellent software without the founder being involved in every implementation decision.
Our stack
● React Native
● Expo
● TypeScript
● React
● Sveltekit
● Node.js
● PostgreSQL
● Supabase
● Vercel
● GitHub Actions
● EAS
● Digital Ocean
You do not need experience with every technology listed above. You should be able to understand unfamiliar systems quickly and make sound technical decisions.
What we’re looking for
We care more about how you think and what you have owned than a specific number of years of experience.
You may be a strong fit if you have:
● Led engineers at an early-stage or founder-led company.
● Owned products or major features from idea through launch.
● Built and shipped high traffic consumer-facing mobile software.
● Strong experience with TypeScript, React, and React Native.
● Worked across mobile, backend, infrastructure, and release systems.
● Improved engineering processes without adding unnecessary bureaucracy.
● Worked directly with founders or small leadership teams.
● Balanced speed, product quality, and long-term technical health.
How we’ll work together
You’ll work closely with the founder, especially at the beginning. The goal is not for him to disappear from product direction. The goal is for him to stop being required for daily execution.
The founder will continue to set the company vision, major product direction, business priorities, and the standard for the customer experience.
You’ll own the decisions, planning, and leadership needed to turn that direction into a working product.
The first 90 days
1. Learn the product, customers, codebase, team, and current release process.
2. Take ownership of planning and day-to-day product questions.
3. Identify the biggest reasons work still depends on the founder.
4. Lead at least one important project from planning through release.
5. Improve how requirements, QA, and releases are handled.
6. Create a practical plan for making the engineering team more independent.
Schedule
● Standard business hours with flexibility based on release rollouts and leadership
● As needed. You will lead the team responsible for reliability and availability. Production outages are unusual, but you will ideally be able to resolve issues without the cofounder stepping in.
Location
● Full-time, remote (US-based)
Location: , ,
LinkedIn: Apply Here