How to Excel as a Technical Project Manager in Internet Companies

Goal Analysis

In technology companies, especially internet firms, engineers often serve as project managers (PM). Success depends on clear goals: on‑time delivery, quality assurance, and complete project output, combined with the crucial factor of people + process.

Project goals : on‑time delivery, quality, complete results. Personnel goals : comfort, achievement, growth. Process goals : risk control, information sync.

Goal Achievement

Project Initiation

The key is a compelling requirement presentation ("painting the cake and pulling people"). PMs must define the project’s purpose, measurable outcomes, and the people involved. Suggested questions cover why the work matters, clarity of the goal, significance, key metrics, impact, team composition, and individual benefits.

Requirement Review

After the presentation, the review stage refines requirements. Common issues include unclear requirements, missing key personnel, and scope creep. Solutions: clarify descriptions, involve all stakeholders early, and split large requirements into manageable pieces.

Project Scheduling

Avoid overly long schedules—break work into units no larger than two person‑days.

Resolve conflicts between product rhythm and resource availability.

Allocate sufficient time for critical phases such as design, integration, smoke testing, and QA.

Communicate schedule details and risks to all participants.

Design & Test Review

Ensure design documents contain diagrams, text, and use‑case coverage. Discuss design and test plans early, list risks, and create checklists for security, performance, and other concerns.

R&D Process

Use tools such as task lists, schedule boards, change‑log tables, personnel responsibility sheets, risk‑tracking lists, and daily progress reports to keep the project transparent and on track.

Smoke Test, Integration & Test

Conduct comprehensive smoke tests (70%+ coverage) and staged integration tests. Define classic business scenarios for integration, prepare dedicated test environments, and enforce logging requirements for critical paths.

Testing

Set up stable test environments, coordinate code reviews, plan release procedures, define version compatibility, enable feature toggles, and prepare rollback plans. For complex projects, consider pre‑release rehearsals.

Product Acceptance

After testing, perform a thorough product acceptance phase with checklists, environment preparation, data validation, issue tracking, change review, and BI/analytics verification.

Project Release

Execute the release with careful coordination of multi‑system dependencies, API and data schema changes, post‑release verification, feature switches, and night‑time deployment if needed. Notify stakeholders promptly.

Retrospective Summary

After release, evaluate whether original goals were met, gather metric data, conduct a pros‑and‑cons review, and celebrate successes where appropriate.

Other Reflections

What is the true business demand?

Has the project deviated from its track?

Do team members gain growth and achievement?

Are risks identified and mitigated?

Does the project build a stronger team?

Beyond outcomes, the human factor—comfort, growth, and collaboration—remains the core of successful technical project management.