Delivery Manager

Cogent Labs; Lahore; On-site; PKR 2,500,000 - 3,500,000; Full time

Job summary

Cogent Labs is seeking a Delivery Manager in Lahore to own project execution from kickoff to go-live. You will translate PRDs into sprints, coordinate engineers, QAs, and designers, and act as the primary client contact for status and deliverables.

You’ll be the first line of defense against scope creep and timeline slippage, ensuring clear communication, risk mitigation, and on-time, quality deliveries across multiple projects in a software services environment.

Qualifications

• 2–5 years in project management or delivery management within software services, product development, or agency environments.
• Familiar with full SDLC from requirements through deployment.
• Experience managing multiple concurrent projects with cross-functional teams.
• Comfortable running client meetings and presenting status updates.

Responsibilities

• Break down PRDs into epics, sprints, and tasks; define realistic timelines with input from engineering and QA.
• Run daily standups, sprint planning, and retrospectives to keep teams aligned and unblocked.
• Serve as the primary client contact for project status, deliverables, and risk management.
• Guard the scope and assess changes for impact on timeline and resources.
• Ensure deliverables meet quality standards and coordinate with QA for UAT readiness.
• Plan and coordinate go-live activities with clients and provide post-launch support.
• Maintain accurate project documentation and timely status reporting.

Skills

Project management

SDLC knowledge

Cross-functional teamwork

Client communication

Risk identification

Documentation & reporting

Tools

Jira

ClickUp

Linear

Job description

Software Development Department · Full-time

Location: 552 College Road, Block 15, Sector B-1, Township, Lahore

Role

The Delivery Manager owns the successful execution of assigned projects from kickoff through go-live. They are the day-to-day driver ensuring projects stay on track, teams stay unblocked, and clients stay informed. The Delivery Manager translates the PRD into actionable sprints, coordinates cross-functional team members (engineers, QAs, designers), and serves as the primary client contact for project status and deliverables. They are the first line of defense against scope creep, timeline slippage, and client dissatisfaction.

Requirements (for an Ideal Candidate)

• Experience: 2-5 years in project management or delivery management within software services, product development, or agency environments. Has managed multiple concurrent projects with cross-functional teams. Familiar with full SDLC from requirements through deployment.
• Technical Understanding: Doesn't need to code but understands how software gets built. Can read a sprint board, follow a technical discussion, and spot when estimates don't add up. Knows enough to ask the right questions.
• Client-Facing Skills: Comfortable running client meetings, presenting status updates, and having difficult conversations when timelines slip or scope changes. Can manage client expectations without damaging relationships.
• Organizational Skills: Highly organized and detail-oriented. Can juggle multiple projects without dropping balls. Keeps documentation current and project tools up to date.
• Communication: Clear and concise communicator-written and verbal. Status reports are useful, not filler. Meetings have agendas and outcomes.
• Problem Solver: Doesn't just surface problems-comes with solutions. Proactive about risk identification and mitigation.
• Team Orientation: Works well with engineers, QAs, and designers. Earns respect through competence and support, not authority. Shields the team from chaos and keeps morale healthy.
• Ownership Mentality: Treats assigned projects as their own. Doesn't wait to be told what to do. When something's off, they fix it or eliminate it—but they don't ignore it.
• Tools: Proficient in project management tools (Jira, ClickUp, Linear, or similar). Comfortable with documentation tools, time tracking, and basic reporting.

Responsibilities

• Project Planning & Execution: Break down PRDs into epics, sprints, and tasks. Define realistic timelines with input from engineering and QA. Maintain project plans andensure the team knows what's expected and by when. Project Discovery Execution: Can independently execute discovery sprint of project end-to-end.
• Team Coordination: Run daily standups, sprint planning, and retrospectives. Ensure engineers, QAs, and designers are aligned and unblocked. Manage dependencies across team members and flag resource needs early.
• Client Communication: Serve as the primary point of contact for assigned clients on project matters. Provide regular status updates, manage expectations, and surface concerns before they escalate. Keep clients informed-no surprises.
• Scope & Change Management: Guard the scope. When clients request changes, assess impact on timeline and resources, document properly, and elevate to Head of Delivery when needed. Prevent scope creep from derailing projects.
• Quality Oversight: Ensure deliverables meet quality standards before UAT submission. Coordinate with QA to confirm testing is complete. Reduce back-and-forth by submitting work that's actually ready.
• UAT Management: Prepare clients for UAT, gather feedback efficiently, prioritize fixes, and drive toward sign-off. Own the UAT cycle time and minimize unnecessary delays.
• Risk Identification: Spot risks early-technical debt, unclear requirements, team capacity issues, client responsiveness gaps. Raise flags, give proposed solutions, not just problems.
• Documentation & Reporting: Maintain accurate project documentation. Deliver weekly status reports on time. Keep project management tools updated so portfolio visibility is never compromised.
• SDLC Compliance: Follow established processes and checkpoints. Ensure your projects adhere to company standards for sprint cadence, code reviews, QA cycles, and deployment procedures.
• Go-Live Coordination: Plan and execute smooth launches. Coordinate with clients on go-live timing, ensure rollback plans exist, and manage post-launch support until stabilization.

Results (What Success Looks Like)

• On-time delivery - Milestones land when promised. Clients trust your timelines because you consistently meet them.
• Happy clients - Clients feel informed and heard. They don't need to chase you for updates or escalation.
• Clean UAT cycles - Deliverables enter UAT ready. Clients aren't rejecting work for obvious issues that should've been caught internally.
• Protected scope - Projects don't balloon. Changes are managed, documented, and communicated - not absorbed silently until the timeline breaks.
• Unblocked teams - Engineers and QAs spend time building, not waiting. You remove obstacles before they slow people down.
• Accurate project visibility - Head of Delivery always knows where your projects stand. No surprises in portfolio reviews.
• Smooth go-lives - Launches happen without drama. Clients go live with confidence.