Being passed over for a promotion is a setback, but not a defeat. Schedule a meeting with your manager to understand the reasoning and collaboratively develop a plan for future advancement.
Promotion Pass Game Developers (Unity/Unreal)

It’s a disheartening experience: consistently delivering high-quality work, demonstrating leadership potential, and then being passed over for a promotion. This guide provides a structured approach for game developers using Unity or Unreal Engine to navigate this challenging situation, focusing on professional communication, understanding the underlying reasons, and charting a path forward. It’s not about demanding the promotion; it’s about understanding why you weren’t selected and what you can do to earn it next time.
1. Understanding the Landscape: Why It Happened
Before you even consider a meeting, take a moment for self-reflection. Consider these possibilities:
-
Skill Gap: Are there specific technical skills (e.g., advanced shader programming, procedural generation, networking optimization) or soft skills (e.g., team leadership, project management, communication) where you need improvement?
-
Performance Perception: Do you accurately perceive your performance? While you might believe you’re exceeding expectations, your manager might have a different view. Consider seeking feedback from trusted colleagues.
-
Strategic Fit: Does the promoted individual possess qualities or experience that better align with the role’s strategic objectives? Perhaps they have experience with a specific platform or genre.
-
Company Politics: While uncomfortable to consider, internal politics can sometimes influence promotion decisions. This isn’t necessarily a reflection of your abilities.
-
Timing: The company might be restructuring, facing budget constraints, or simply not have the resources for a promotion at this time.
2. The High-Pressure Negotiation Script
This script assumes a one-on-one meeting with your manager. Adjust the tone and language to suit your relationship. Crucially, maintain a calm, professional, and curious demeanor.
You: “Thank you for taking the time to meet with me. I was disappointed to learn I wasn’t selected for the [Promotion Title] position. I’m committed to my growth at [Company Name] and would appreciate the opportunity to understand the reasoning behind the decision.”
Manager: [Likely explanation – listen carefully and take notes. Don’t interrupt.]
You: “Thank you for sharing that. Could you elaborate on [specific point from manager’s explanation]? I want to ensure I fully understand the areas where I need to focus.”
Manager: [Further explanation]
You: “I understand the concerns regarding [specific area]. I’ve been actively working on [mention specific actions taken or planned to address the concern]. Could you provide specific examples of how I could demonstrate improvement in this area? What metrics would indicate I’m on the right track?”
Manager: [Feedback and suggestions]
You: “That’s incredibly helpful. Based on our conversation, could we collaboratively develop a performance improvement plan (PIP) with clear, measurable goals and a timeline for review? I’d like to understand how I can position myself for consideration for the role, or a similar opportunity, in the future.”
Manager: [Response – likely agreement or discussion about the plan]
You: “Thank you. I appreciate your honesty and willingness to work with me. I’m committed to addressing these areas and contributing to the team’s success. Can we schedule a follow-up in [Timeframe - e.g., 3 months] to review my progress?”
Manager: [Agreement]
You: “Thank you again for your time and feedback.”
3. Technical Vocabulary
-
Shader Programming: Writing programs that control how surfaces appear in a game, impacting visual fidelity and performance.
-
Procedural Generation: Algorithmically creating game content (levels, textures, models) instead of manual design.
-
Networking Optimization: Techniques to reduce latency and improve performance in multiplayer games.
-
Collision Detection: The process of determining when two objects in a game world are touching or overlapping.
-
Game Engine Architecture: Understanding the underlying structure and components of game engines like Unity and Unreal.
-
Asset Pipeline: The workflow for importing, processing, and integrating assets (models, textures, audio) into a game project.
-
Blueprint Scripting (Unreal Engine): Visual scripting system in Unreal Engine.
-
**C
Scripting (Unity):** Primary scripting language for Unity.
-
Performance Profiling: Analyzing game performance to identify bottlenecks and areas for optimization.
-
Version Control (Git): System for tracking changes to game code and assets.
4. Cultural & Executive Nuance
-
Assume Positive Intent: Start from the assumption that your manager’s decision wasn’t malicious. They likely believe they made the best choice for the company.
-
Focus on Learning, Not Blame: Frame the conversation as an opportunity for growth and development. Avoid accusatory language or defensiveness.
-
Be Specific and Data-Driven: Don’t just say you’re a hard worker. Provide concrete examples of your accomplishments and contributions. Refer to project metrics or positive feedback from colleagues.
-
Show Initiative: Proposing a PIP demonstrates your commitment to improvement and proactive approach.
-
Understand Executive Priorities: Senior management often makes promotion decisions based on strategic goals. Align your development plan with these priorities.
-
Document Everything: Keep a record of your meeting, the agreed-upon PIP, and your progress. This provides a clear audit trail.
-
Don’t Publicly Complain: Venting to colleagues can damage your reputation and create unnecessary drama. Maintain professionalism.
-
Consider Alternatives: If the promotion isn’t possible now, explore other opportunities for growth, such as leading a smaller project or mentoring junior developers.
-
Be Prepared for a “No”: Sometimes, despite your best efforts, the decision remains unchanged. In this case, evaluate your long-term career goals and consider whether the company is the right fit for you.
5. Post-Meeting Actions
-
Implement the PIP: Diligently work on the areas identified for improvement.
-
Seek Regular Feedback: Schedule regular check-ins with your manager to discuss your progress and receive ongoing feedback.
-
Network: Build relationships with colleagues and mentors who can provide support and guidance.
-
Continue Learning: Stay up-to-date with the latest technologies and trends in game development.
-
Re-evaluate: After the review period, assess your progress and discuss future opportunities with your manager.