Technical Product Manager

At LaunchBrightly, we are on a mission to automate a process that continually captures and enhances screenshots of all your SaaS product features. The continuous integration and continuous deployment (CI/CD) pipeline and process that engineers adopted over the last decade, is what we ultimately want to build for customer support teams. TLDR; LaunchBrightly = Github Actions/Circle CI for customer support. And we are currently looking to bring onboard a strong Technical Product Manager. 

Everyone at LaunchBrightly is a creator, an owner, or perhaps better, a celebration of the crazy ones. The misfits. The rebels. Most big companies are afraid of entrusting the future of the company and their software to a few makers, and as they defend against that, they end up with three layers of managers and a product designed by a committee. We want the opposite. We need the opposite as we enter virgin territory trying to build that CI/CD pipeline and process for the support organization. As our customer pushes a new feature to production, we automatically update all product images within the help center. This is a thrilling adventure!

Our work is remote, not distant. We believe that being a remote-first organization allows us to build an exceptional team composed of makers and sellers with diverse backgrounds and skill sets from around the globe. Our default work culture is asynchronous and emphasizes written communication to prioritize maker time, focus and company productivity. Our goal is not to eliminate face-to-face interaction, but we should default to a setting where written documentation is so strong that a meeting on most project subject matters would seem odd.  

Founded in 2022, and backed by prominent venture firms including IA Ventures, Tuesday Capital, and B Capital Group, this is a unique opportunity to join this band of misfits on the ground floor. As an early teammate you will be working intimately with the founding team, who has done 0 to 1 five times over while seeing four of them come to an exit.

The Technical Product Manager will become an integral member of an intimate 10-person team consisting of:

• Maker #8 (Technical Product Manager, You!)

• Maker #7 (Esau, Engineer)

• Maker #6 (Melissa, Implementation Specialist)

• Maker #5 (Michel, Engineer)

• Maker #4 (Lucas, Engineer / UX)

• Maker #3 (Jose, Engineer)

• Maker #2 (Hyder, Backend Engineer)

• Maker #1 (Dennis, Founder)

• Seller #1 (Josh, Co-founder)

• Helper #1 (Vibeke)

However, we are looking not just for a Technical Product Manager but, rather, a teammate we see as integral to LaunchBrightly’s long-term journey and vital to our success. Someone who is comfortable in the dark and who sees a certain romance, like we do, in embracing the unknowns that come with being on the startup journey. We have a track record of seeing those colleagues who join us on the ground floor of our ventures ride the startup journey to completion (exit) with us, as we grow and become successful together. This is something we take seriously, and something we are extremely proud of! 

Job Description

Your work will help shape the business logic layer that powers our product — workflows, task runners, state machines, rules engines, and orchestration. This is a hands-on product role for someone who thinks in systems and sequences. You won’t be writing code as your primary responsibility, but you will define and refine the behaviors that drive complex systems, working closely with engineering to turn intent into reliable execution. And you shouldn’t be shy about jumping into code, writing QA scripts, or testing flows yourself when needed.

You’ll be responsible for things such as:

• Owning PRDs and RFCs for larger features, and maintaining a clean, structured Product documentation folder that clearly captures intent, scope, and decisions

• Mapping logic flows: outlining step-by-step behaviors, edge cases, and decision paths

• Modeling state: defining key states, transitions, and triggers (including retries and failure modes)

• Capturing validation rules: both field-level and conditional, across sync and async flows

• Handling exceptions: specifying how to surface, log, or recover from system errors

• Tracing data dependencies: documenting inputs, transformations, joins, and sync logic across services

• Acting as a primary contributor to API documentation and helping ensure our Postman collections are accurate and aligned with shipped behavior

• Serving as first eyes on Sentry reports across repositories and actively monitoring feature releases for regressions

• Acting as an active PR reviewer, helping protect us from sub-optimal code and future technical debt

In this role your work will span early-stage research, feature scoping, documentation and organization of engineering tickets, weekly planning, and internal QA. Your job is to remove blockers before they slow things down, making sure problems are well-defined before they reach engineering, and helping ensure the product we ship is as useful and reliable as possible for our users.

You’ll also help ensure our product help and API documentation remains up-to-date, structured, and reflective of the current system. Where documentation is missing or fragmented, you’ll take initiative to improve it. 

This role will see you work along the following tracks:

• Translating complex ideas and customer needs into structured and well documented engineering tickets

• Turning Slack discussions into actionable GitHub tickets with clear ownership and next steps

• Know when to push for answers and when to leave things alone

• Maintaining clean, well-scoped backlogs with clear labels and status comments so Makers can focus on building

• Helping prioritize the ticket queue to maximize velocity and impact, and setting clear weekly Maker plans — what’s being worked on and why

• Keep a high-level roadmap in place at all times

• Being comfortable debating kindly (but clearly) in GitHub tickets and design discussions

• Performing lightweight QA passes, writing test scripts where helpful, and tightening feedback loops

• Keeping the entire team aligned with clear async updates, structured meeting summaries, and explicit follow-up action items

• Taking initiative to pull others into planning discussions when necessary, and actively following up to keep work moving — less manager, more coach

• Know when process is helpful — and when it’s a tax

To succeed in the TPM role, especially in our environment, it requires sustained, day-to-day activity: driving issues forward, creating and closing loops, engaging actively in GitHub (our primary collaboration tool), Slack, and Figma, and being visibly present as work moves.

This is a high-leverage role for someone who wants to grow into a senior product position by learning how to amplify the work of great builders; while owning planning, execution quality and roadmap clarity in a fast-moving startup environment.

We are looking for previous experience working with

• Strong understanding of HTML, CSS and the DOM (and being able to manipulate elements at will in the console)

• Ability to write your own DB queries when needed (SQL, ideally GraphQL)

• Knowledge of JS/Node.js and an ability to write QA scripts as needed

• Ability to manage Git workflows and use GitHub tooling effectively (branches, PRs, merges, conflict resolution)

• API experience, and specifically work in Postman; Consuming and commenting on internal APIs

• Experience reviewing PRs and engaging meaningfully in technical discussions

• Familiarity with Figma or other UI/UX tool

What you bring to the table

• 2+ years of experience in a technical role (e.g. Software Engineering, Technical Support, QA, or Product Ops) or in a product-facing position at a software company

• A customer-first mentality, with an instinct to imagine how users will react and interact

• Strong and precise communication and documentation skills, with a will to understand and be understood. Comms so crisp that the rest of us can move forward without a meeting

• Great personal organization skills and patience to manage multiple contexts as projects and features come together

• Are curious and comfortable asking questions when things are unclear and not shy to say; “I don’t know” 

• A passion for being part of the startup journey and taking ownership of the company’s success

• A willingness to take initiative and enthusiasm to make an impact and take action

• Thrives in a highly collaborative environment and enthusiasm for being a team player

Bonus point if you

• Having worked a side-gig or built something from 0-1 on your own is a big plus

• Started out as a Software Engineer / Have a CS degree

What we offer

• Flexible working hours and locations. Your success is measured on outcomes

• A culture of NO meetings where maker time and productivity is prioritized

• Excellent start-up culture with openness and inclusiveness

• True ownership and autonomy over your role and the impact on the company

• Prioritization of focus time and productivity 

• Your choice of technical setup and equipment

• Experienced founders with many years of successfully building product across multiple ventures

• Annual meetup as a team in New York City.

What to expect in the interview process

Given the remote nature of our work setting, one of the core principles for how we operate as a remote team is written communication. And we therefore run a slightly unique interview process that begins with an email-based exchange to learn more about your background, communication style and overall fit for the role.

• Stage 1: You’ll begin with an email conversation with our Co-founder, Josh Peacock, to get a sense of your technical background, written communication, and English proficiency.

• Stage 2:  Next, you'll have a follow-up email exchange with one of the Makers on our team on a set of more technical questions to get a deeper understanding of your technical knowledge and capabilities.

• Stage 3: We’ll then ask you to do a call with our Founder, Dennis Mortensen, on a specific use case which we will share ahead of time. This isn’t a pass/fail test or conversation where there is a right/wrong answer — it’s more an exercise to get a better understanding of your thought process and approach to tackling these types of scenarios.

• Final stage: You’ll have a video call with one of the Makers from the team to give us a chance to connect more personally and explore how you'd fit into the team.

Please mention the word **GENEROUS** and tag RMTYyLjIyMC4yMzQuMjY= when applying to show you read the job post completely (#RMTYyLjIyMC4yMzQuMjY=). This is a beta feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.