Project Manager - Full-time, onsite

Grayhat Developers Private Limited; Islamabad; On-site; PKR 1,800,000 - 3,000,000; Full time

Job summary

Grayhat Developers Private Limited seeks a high-agency Project Manager to own end-to-end delivery across engineering, product, research, design, clients, sales, and leadership. You will turn requirements into concrete plans, create and manage sprint plans, and ensure cross-team alignment to ship high-quality software on time.

The role demands taking initiative in a fast-changing environment, balancing priorities, and continuously improving processes to drive better outcomes for clients and

Qualifications

• Lead projects from concept to shipped delivery by turning requirements into concrete plans and milestones.
• Break large problems into executable work items for multiple teams.
• Create sprint plans aligned with client requirements and business priorities.
• Keep engineering, product, research, design, and clients aligned throughout the project lifecycle.
• Track dependencies, capacity, risks, and deadlines; escalate blockers with context.

Responsibilities

• Facilitate daily stand-ups, sprint planning, reviews, and retrospectives.
• Ensure tickets are clear, actionable, and properly scoped.
• Monitor sprint progress and adjust capacity to meet release targets.
• Adapt Agile practices to the needs of different teams and projects (hybrid Kanban/Scrum).
• Communicate project status and business impact to stakeholders regularly.

Skills

Project management

Cross-functional collaboration

Agile methodologies

Stakeholder management

Communication

Job description

The backbone of Grayhat's reliability and consistency.

Grayhat is looking for a high-agency Project Manager who can take ownership of projects, bring clarity to complex problems, and keep teams moving toward outcomes.

This isn't a role limited to managing timelines and asking for status updates. You'll work across engineering, product, research, design, clients, sales, and leadership to make sure projects are well-planned, well-executed, and continuously improving.

You'll wear multiple hats, operate in an environment where things change quickly, and be expected to take initiative when you see something that can be improved.

If you enjoy solving problems, building better systems, and helping teams do their best work, you'll fit right in.

What You'll Own

Take projects from "we should build this" → "it's shipped."

• Turn requirements and discussions into concrete plans, milestones, deliverables, and timelines.
• Break large problems into work that teams can execute effectively.
• Create sprint plans aligned with client requirements and business priorities.
• Keep engineering, product, design, research, and clients aligned.
• Track dependencies, capacity, risks, and deadlines.
• Identify blockers and risks early and drive them toward resolution.
• Facilitate daily stand-ups, sprint planning, reviews, and retrospectives.
• Ensure tickets are clear, actionable, prioritized, and properly scoped.
• Track sprint progress and adjust capacity planning to meet release targets.
• Adapt Agile practices to the needs of individual teams and projects, including hybrid Kanban/Scrum approaches where appropriate.

The goal isn't perfect Agile ceremonies.

The goal is to ship better software, more consistently.

Stakeholder Management

Projects work best when everyone understands what we're building, why we're building it, and where things stand.

You'll work across:

Your job is to keep those groups aligned.

• Communicate continuously with clients, executives, product owners, and internal stakeholders.
• Make sure important information reaches the right people at the right time.
• Translate technical progress into clear business impact.
• Translate business requirements into something technical teams can execute.
• Conduct regular roadmap and project reviews with leadership.
• Understand stakeholder influence, expectations, and interests and tailor communication accordingly.
• Mediate competing priorities between engineering, product, research, and business.
• Balance user simplicity against the needs of administrators, organizers, and other power users.
• Know when to push back, when to escape, and when to take ownership and resolve an issue directly.

Escalate blockers with context, impact, and a proposed path forward.

Project Reporting & Visibility

Leadership shouldn't have to chase you for project status.

You will build reporting systems that clearly answer:

• Where are we?
• Where were we supposed to be?
• What's late?
• What's blocked?
• What's at risk?
• Why?
• What changed?
• What do we need to do about it?

You'll:

• Establish reliable reporting mechanisms that give teams and leadership a clear picture of project health.
• Track metrics such as sprint velocity, burndown, cycle time, throughput, capacity, and delivery timelines.
• Identify trends and bottlenecks through project data.
• Keep project documentation, decisions, requirements, and status information accurate and accessible.
• Build a culture where project status is transparent and predictable.

Good project management means identifying problems early enough that we can do something about them.

Process Engineering & Continuous Improvement

Grayhat is growing, and our processes need to grow with it.

You'll be expected to look at how we work and ask:

"Can we do this better?"

Then help make it happen.

You'll help design and improve processes across:

• Software Development Lifecycle
• Product Lifecycle
• QA Lifecycle
• Release management
• Internal operations

You'll:

• Identify inefficiencies in how projects are planned, developed, tested, and delivered.
• Observe how teams work and turn recurring patterns into repeatable processes.
• Build systems that make project execution faster, more predictable, and less dependent on individual people.
• Continuously improve processes based on real project outcomes.
• Balance process consistency with the flexibility required by different products and teams.

If the same problem keeps happening, don't just solve it again.

Improve the system that caused it.

Technical Enablement & Automation

You don't need to be a software engineer.

But you do need to be technically curious.

Learn enough coding, scripting, APIs, and automation to identify opportunities for improvement and eliminate repetitive work.

You will:

• Develop a strong understanding of software engineering practices and development workflows.
• Learn enough coding to understand technical problems and communicate effectively with engineers.
• Identify repetitive manual work and automate it wherever possible.
• Build or facilitate automations, scripts, integrations, and internal tools.
• Improve project reporting, ticket management, communication, QA, and operational workflows through technology.
• Become comfortable navigating technical discussions and identifying dependencies.
• Work effectively in an environment where AI-assisted development and AI agents are increasingly part of engineering.
• Project reporting automations
• Slack/Discord/Email integrations
• Automated QA checks
• Notifications and alerts
• AI-assisted workflows

We're surrounded by powerful tools.

Use them to make the team more effective.

Team Development

Your job isn't to become the team's permanent coordinator.

It's to help the team become better at managing itself.

You'll:

• Mentor team members on planning, prioritization, communication, and accountability.
• Help people develop stronger self-management and ownership habits.
• Encourage teams
• f…

...