**The Role in One Paragraph**
We are looking for a Technical Project Manager who can take a product vision and turn it into structured, shippable work. The vision exists. The roadmap direction exists. What we need is someone who can sit with C-Suite and engineers, absorb the vision in detail, break complex features down into smaller, well-defined chunks, and then run the team that ships them - on time, with clear scope, and without chaos.
**Why This Role Matters**
Right now, the gap between "this is what we want to build" and "this is what the team is actually working on this sprint" is too big. Features are too vague when they reach engineering, dependencies are not mapped, estimates slip, and small misalignments turn into big delays. We need someone who closes that gap full-time.
This is a hands-on execution role, not a strategy role. You will not own product direction - you will own that the product gets built, on schedule, with quality, and with everyone aligned. If running a tight ship is what makes you happy, you will love this job.
**What You Will Do**
**Translate vision into structured work**
- Sit with C-Suite and stakeholders to deeply understand the product vision, priorities, and constraints.
- Take high-level features and break them down into epics, user stories, and tasks with clear acceptance criteria.
- Map dependencies, sequence work intelligently, and call out hidden complexity early — before sprint planning, not during.
- Maintain a backlog that is actually usable: every ticket should be clear enough that an engineer can start without asking five questions.
**Run the team and the process**
- Run sprint planning, daily standups, refinement sessions, and retrospectives - cleanly, without ceremony for ceremony's sake.
- Manage the day-to-day flow of work: who is doing what, what is blocked, what is at risk, what slipped and why.
- Keep engineers focused on building - absorb the noise, manage stakeholders, protect deep work time.
- Coordinate across design, engineering, marketing, and customer success so releases land cleanly.
**Be technical enough to be useful**
- Challenge estimates when they don't add up. Ask the right questions when an engineer says "this is complicated."
- Understand our architecture well enough to spot when a small request hides a big technical change.
- Read code at a basic level, follow technical discussions, and translate between technical and non-technical stakeholders.
- Make trade-offs explicit: scope vs. timeline, technical debt vs. speed, ideal vs. shippable.
**Communicate, document, and protect predictability**
- Give honest, frequent status updates. No surprises. If something is at risk, flag it early.
- Keep documentation tight: roadmap, sprint goals, release notes, decisions, post-mortems.
- Track delivery metrics that matter: velocity, cycle time, predictability of estimates, and use them to improve, not to police.
**Who We Are Looking For**
- 2 to 4 years as a Technical Project Manager, Delivery Manager with technical depth, or Engineering Manager (light) on a software product.
- You have actually broken down complex features into shippable work and run a team through delivery. Not just attended ceremonies.
- Strong technical background: a degree in computer science / engineering, or several years as a developer, QA engineer, or technical lead before moving into delivery.
- Comfortable reading code, reviewing architecture diagrams, and pushing back on engineering when estimates or scope feel off.
- Fluent in agile/scrum and kanban, and able to adapt the process to the team rather than forcing rituals on it.
- Strong written English - your tickets, updates, and documents should leave no room for interpretation.
- Calm under pressure. You don't panic when things slip. You replan, communicate, and move forward.
- Based in Tirana or willing to relocate - hybrid, 4 days office / 1 day remote.
**Nice to Have**
- Experience with B2B products and multi-tenant web platforms.
- Hands-on familiarity with our typical stack (web technologies, REST/GraphQL APIs, cloud infrastructure, CI/CD).
- Experience working directly with C-Suites or technical leadership.
- Familiarity with tools like Linear, Jira, GitHub, Notion, Figma, and AI-assisted workflows for ticket breakdown and documentation.
- Certifications such as PSM, CSM, or PMP - not required, but appreciated if backed by real delivery experience.
- Albanian and English fluency (Italian is a plus).
**What We Offer**
- A real ownership role: you run delivery, you don't just track tickets.
- Direct work with C-Suite and engineering leadership — short feedback loops, fast decisions, no political layers.
- A small, capable team where good process improvements ship the same week you propose them.
- Hybrid setup: 4 days at our Tirana office, 1 day remote per week.
- Competitive salary aligned with your experience, reviewed yearly.
We are looking for a Technical Project Manager who can take a product vision and turn it into structured, shippable work. The vision exists. The roadmap direction exists. What we need is someone who can sit with C-Suite and engineers, absorb the vision in detail, break complex features down into smaller, well-defined chunks, and then run the team that ships them - on time, with clear scope, and without chaos.
**Why This Role Matters**
Right now, the gap between "this is what we want to build" and "this is what the team is actually working on this sprint" is too big. Features are too vague when they reach engineering, dependencies are not mapped, estimates slip, and small misalignments turn into big delays. We need someone who closes that gap full-time.
This is a hands-on execution role, not a strategy role. You will not own product direction - you will own that the product gets built, on schedule, with quality, and with everyone aligned. If running a tight ship is what makes you happy, you will love this job.
**What You Will Do**
**Translate vision into structured work**
- Sit with C-Suite and stakeholders to deeply understand the product vision, priorities, and constraints.
- Take high-level features and break them down into epics, user stories, and tasks with clear acceptance criteria.
- Map dependencies, sequence work intelligently, and call out hidden complexity early — before sprint planning, not during.
- Maintain a backlog that is actually usable: every ticket should be clear enough that an engineer can start without asking five questions.
**Run the team and the process**
- Run sprint planning, daily standups, refinement sessions, and retrospectives - cleanly, without ceremony for ceremony's sake.
- Manage the day-to-day flow of work: who is doing what, what is blocked, what is at risk, what slipped and why.
- Keep engineers focused on building - absorb the noise, manage stakeholders, protect deep work time.
- Coordinate across design, engineering, marketing, and customer success so releases land cleanly.
**Be technical enough to be useful**
- Challenge estimates when they don't add up. Ask the right questions when an engineer says "this is complicated."
- Understand our architecture well enough to spot when a small request hides a big technical change.
- Read code at a basic level, follow technical discussions, and translate between technical and non-technical stakeholders.
- Make trade-offs explicit: scope vs. timeline, technical debt vs. speed, ideal vs. shippable.
**Communicate, document, and protect predictability**
- Give honest, frequent status updates. No surprises. If something is at risk, flag it early.
- Keep documentation tight: roadmap, sprint goals, release notes, decisions, post-mortems.
- Track delivery metrics that matter: velocity, cycle time, predictability of estimates, and use them to improve, not to police.
**Who We Are Looking For**
- 2 to 4 years as a Technical Project Manager, Delivery Manager with technical depth, or Engineering Manager (light) on a software product.
- You have actually broken down complex features into shippable work and run a team through delivery. Not just attended ceremonies.
- Strong technical background: a degree in computer science / engineering, or several years as a developer, QA engineer, or technical lead before moving into delivery.
- Comfortable reading code, reviewing architecture diagrams, and pushing back on engineering when estimates or scope feel off.
- Fluent in agile/scrum and kanban, and able to adapt the process to the team rather than forcing rituals on it.
- Strong written English - your tickets, updates, and documents should leave no room for interpretation.
- Calm under pressure. You don't panic when things slip. You replan, communicate, and move forward.
- Based in Tirana or willing to relocate - hybrid, 4 days office / 1 day remote.
**Nice to Have**
- Experience with B2B products and multi-tenant web platforms.
- Hands-on familiarity with our typical stack (web technologies, REST/GraphQL APIs, cloud infrastructure, CI/CD).
- Experience working directly with C-Suites or technical leadership.
- Familiarity with tools like Linear, Jira, GitHub, Notion, Figma, and AI-assisted workflows for ticket breakdown and documentation.
- Certifications such as PSM, CSM, or PMP - not required, but appreciated if backed by real delivery experience.
- Albanian and English fluency (Italian is a plus).
**What We Offer**
- A real ownership role: you run delivery, you don't just track tickets.
- Direct work with C-Suite and engineering leadership — short feedback loops, fast decisions, no political layers.
- A small, capable team where good process improvements ship the same week you propose them.
- Hybrid setup: 4 days at our Tirana office, 1 day remote per week.
- Competitive salary aligned with your experience, reviewed yearly.
