Notion Press
Website:
notionpress.com
Job details:
About the role:
Notion Press runs a technology platform used by tens of thousands of authors and readers. Behind it sits an in-house product and engineering team building web applications, internal tools, integrations and a growing amount of AI assisted automation. We are currently rebuilding how that engineering team runs, with a new delivery pipeline and a new pod structure, and we need someone to run projects through it.
Every piece of engineering work we take on, whether it is a new product feature, a research bet, a third party integration or a critical production bug, moves through one defined pipeline. Intake, research, technical definition, proof of concept, UI, production planning, build, demo, deployment, and then measurement once it is live. Every stage has an owner, and every project has success metrics agreed before a line of code is written.
We are looking for the person who holds all of that together.
You will pick up a project at intake and stay with it until the 90 day post release metrics are in. You will sit in the CTO's office rather than inside one delivery team, which means you see everything that is in flight, across every project, all the time.
If you like being the person who knows exactly where every build stands, this is a very good seat.
What you will do
- Own the tracker. Every item, every stage, every timeline, every owner, in Jira Product Discovery and the sprint backlog. Our rule is simple: if it is not in the tracker, it is not happening. Keeping that true is your job.
- Hold the stage gates. Nothing moves forward until it has met its exit criteria. PoC results tested against the metrics we defined upfront, UI signed off, production plan complete, end user sign off before anything is called done. You are the person who says "not yet, this is incomplete", including to engineers more senior than you.
- Run the daily scrum. You run it, with the CTO in the room. Blockers surface the same day rather than at the end of a sprint.
- Run releases. You coordinate deployment planning across development, QA and infrastructure, and you make sure rollback plans exist before anything goes to production.
- Track and report the metrics. Everything we ship gets measured at 24 hours, 48 hours, 1 week, 30, 60 and 90 days against its defined metrics. You set the cadence for each item, gather the numbers, and give the CTO a clean read so the next decision, whether that is scale it, iterate on it, roll it back or kill it, gets made on evidence rather than instinct.
- Keep the process healthy. Timesheets, debriefs, documentation. Not glamorous, and the whole system falls apart without it.
What we are looking for
- 3 to 6 years managing software projects, as a technical project manager, delivery manager, programme manager or scrum master, inside a software product or engineering team
- Direct experience running sprints for a team of developers, QA and infrastructure engineers. Your day should already look like standups, grooming, dependency tracking and release coordination.
- Hands on ownership of a backlog in Jira, Linear or similar, including sprint planning, grooming and dependency tracking
- A track record of running parallel software workstreams at the same time without losing track of any of them
- Enough technical grounding to follow a conversation about architecture, APIs, tech stack choices, staging and production environments, and deployment approaches. You will not be writing production code, but you do need to ask the right questions and know when an answer is thin.
- Comfort with metrics. You can define a measurable success criterion, go and get the number, and report it straight, including when the news is not good.
- Clear, precise writing. A lot of this role is written communication.
- The confidence to hold a line. Telling an experienced engineer that something is not ready to move forward is a weekly part of this job.
Good to have
- Experience with Jira Product Discovery
- A background in e-commerce, marketplaces, consumer internet or SaaS platforms
- An engineering or computer science degree, or a career that started in development or QA
- Exposure to AI or ML assisted product work
- Scrum or Agile certification
Please note: this is a role inside our software engineering team, reporting to the CTO. It is not an editorial, book production or publishing project management role. If your background is in managing manuscripts, print schedules or author deliverables, this is not the right fit.
Click on Apply to know more.