Product Owner

SYNCIFY, Product OwnerMidtown Manhattan, New York · Full-Time · On-SiteABOUT SYNCIFYSyncify is a construction scheduling SaaS platform built for the enterprise. We are not a generalist project management tool.

We are purpose-built for the way large-scale construction projects are actually run — Critical Path Method scheduling, Gantt-based project views, Primavera P6 integration, and the operational complexity that comes with managing multi-million dollar construction timelines.

We are backed by Accurise, a construction scheduling consulting firm with over a decade of executive-level relationships with some of the largest construction companies in the industry. Accurise does not just fund Syncify — Accurise runs its own consulting business on Syncify. We are our own most demanding client. The product was not invented. It was built to solve a real problem we live every day.

We are at an inflection point. Enterprise clients are beginning to self-serve in the platform. A public commercial launch is on the horizon. We are growing fast, and we are building the team that will take us there.

THE OPPORTUNITY

This is the role that sits between our co-founders — who have deep, lived construction expertise and a constant flow of product ideas — and a development team that needs those ideas translated into clear, actionable direction before they start building.

Right now, there is no one in that seat. The co-founders think in construction outcomes. The developers build in code. The gap between those two worlds is where features get built twice, requirements arrive half-formed, and good work gets thrown away. You close that gap.

You will be the person our co-founders trust to absorb their vision and sharpen it into something a developer can execute. You will be the person our developers rely on for clarity before they write a single line of code. And you will bring order to a backlog that currently runs on instinct.HOW THIS ROLE FITSYou will report to the co-founders.

You will define what the development team builds and in what order; our engineering lead runs how it gets built.

You will work directly with our development team. There are no layers between you and the people building the product. Decisions move from conversation to code in days, not weeks. This team will grow — you will help shape what it becomes.

WHAT YOU WILL DO

• Sit with the co-founders, absorb their product thinking, and ask the questions that turn a brain dump into a requirement.
• Write user stories with clear acceptance criteria — testable outcomes a developer can act on without guessing.
• Own the product backlog. Prioritize it. Sequence it. Protect the team from working on the wrong thing in the wrong order.
• Be the on-call decision-maker for the development team when co-founders are unavailable and a question needs an answer before work can continue.
• Push back when a feature request is not ready, when requirements are contradictory, or when the timing is wrong — and do it in a way that earns respect, not friction.
• Bridge construction scheduling — CPM logic, how schedulers actually work, what P6 users expect — and software development. Translate both directions fluently.
• Track active development work, communicate progress, and surface risks before they become problems.

WHAT YOU BRING

• You have the right construction background and the mind to move fast.
• You have enough construction in your background to be useful from day one — and you are sharp enough to absorb new tools and context fast, keep up with founders who think quickly, and be understood when you respond.
• You have been close to software.
• Whether as a product owner, an implementation specialist, a customer-facing technical role, or a scheduler who crossed into the technology side — you understand how software gets built.
• You can read a technical conversation, contribute to it, and translate it for someone who is not technical.
• You have owned a backlog or the equivalent.
• You have written requirements a developer could act on and know what “done” means before work starts — or you have done the equivalent under a different title and you know what it takes to navigate that space.
• You thrive in a fast, small environment.
• You are comfortable with ambiguity, energized by pace, and able to make decisions with incomplete information.
• You do not wait to be told what to do next.
• You earn trust, not authority.
• You do not need a title to get things done.
• You get things done because people believe you understand the problem.
• With co-founders and with developers alike, you build credibility by being right more often than not — and honest when you are not.WHAT SUCCESS LOOKS LIKE
• Within 30 days: you understand the product well enough to follow a technical conversation, you know every developer’s name and what they own, and the co-founders trust you to relay a requirement to the team without losing something in translation.
• Within 60 days: the development team has a structured backlog and a go-to person. Developers bring questions to you first, get answers that move them forward, and rarely wait on a founder to unblock them.
• Within 90 days: the co-founders are routing new feature ideas through you before they reach developers — not because they were told to, but because they find it makes things move faster and better.
• Ongoing: the gap between what is asked for and what is built is consistently narrow. Rework is rare. The team has flow.WHAT THIS ROLE IS NOTWe have made hires in this space before. We have learned from them. So we want to be direct.
• This is not a role for someone who arrives with a pre-built methodology and expects the team to adopt it. We have a way of working. You plug into it, improve it from the inside, and earn the right to shape it over time.
• This is not a role for someone who needs construction explained to them.
• This is not a role for someone who is primarily a coordinator or a status reporter. We need a product thinker who gets into the details of what gets built and why.
• This is not a remote role. You will be in our Midtown Manhattan office, alongside co-founders and developers.THE PROFILE WE ARE LOOKING FORIf you have spent time in or around construction — as a scheduler, a project controls analyst, an owner’s rep, a construction technology implementation role, or anything that put you close to how projects are planned and tracked — and you have held a product owner, product manager, business analyst, or similar role where translating requirements into executable work was your job, we want to hear from you.
• You do not need to have come up at a named construction technology company.
• You do not need to be a P6 expert.
• You need to understand how construction projects move, think on your feet when priorities shift, and translate clearly in both directions — from founder intent into developer-ready requirements, and from developer reality back to the people making decisions.