A recent Hacker News thread on the realities of management roles drew 29 points and 15 comments from developers and technical leads.
The post and discussion focus on the shift from individual technical work to people coordination, specifically relevant for AI teams where model training cycles and research velocity depend on clear prioritization.
What Management Actually Involves
Management centers on resource allocation and conflict resolution rather than direct model building. Practitioners report spending 60-70% of time in meetings, status tracking, and career conversations instead of code or experiments.
The original post highlights that promotion to manager often removes the direct dopamine of shipping models or papers.
Numbers from the Discussion
Commenters shared concrete time splits:
- 4-6 hours daily on 1:1s and cross-team syncs
- 2-3 hours on performance reviews and promotion packets
- Remaining time on unblocking experiments or hiring pipelines
One thread noted that AI-specific teams see higher meeting load due to compute budget reviews and safety alignment checkpoints.
How to Test the Role
Engineers can shadow an existing manager for two weeks by joining staff meetings and helping draft project charters. Many teams allow "manager on-call" rotations lasting one sprint.
Start by documenting decisions in a shared repo and tracking team velocity metrics before requesting a formal trial period.
Tradeoffs Reported by AI Practitioners
- Pros: broader impact on multiple projects, direct influence on hiring and tooling budgets, clearer path to director-level compensation.
- Cons: loss of deep technical flow states, higher emotional labor during layoffs or reorgs, slower personal publication record.
Early commenters noted the compensation delta averages 15-25% but requires sustained output on non-technical deliverables.
Alternatives Within Technical Tracks
Individual contributor ladders at labs like OpenAI and Anthropic allow principal engineers to reach similar pay without people management. These roles emphasize architecture reviews and research direction instead of headcount oversight.
| Path | Focus | Meeting Load | Publication Impact |
|---|---|---|---|
| Engineering Manager | Team outcomes | High | Low |
| Principal IC | Technical direction | Medium | High |
| Tech Lead | Project execution | Medium-High | Medium |
Who Should Consider the Move
Strong candidates show consistent interest in mentoring and process design, plus tolerance for ambiguous outcomes. Skip the transition if primary satisfaction comes from writing training loops or debugging model failures.
Teams with 8+ engineers benefit most from dedicated managers; smaller groups often succeed with rotating tech leads.
Practical Verdict
The HN thread reinforces that management success hinges on enjoyment of enabling others rather than personal technical wins. AI organizations continue to need both strong ICs and capable managers, with the better fit determined by individual preference for coordination versus creation.
The discussion suggests testing the role through temporary projects before committing to a permanent title change.
Top comments (0)