You’re a valuable backend engineer, and proactively seeking [High-Visibility Projects](/high_visibility_projects/) is essential for career growth. This guide provides a script and strategies to confidently articulate your desire for these opportunities to your manager, emphasizing your skills and the benefits to the team.

Advocating for High-Visibility Projects Go/Rust Backend Engineers

advocating_for_high_visibility_projects_gorust_backend_engin

As a backend engineer specializing in Go and Rust, you possess in-demand skills. However, technical proficiency alone isn’t always enough for career advancement. Actively seeking and Securing High-Visibility Projects – those that directly impact key business metrics or are presented to stakeholders – is crucial. This guide addresses the common conflict of wanting more of these projects and provides a framework for a successful negotiation.

Understanding the Conflict

Often, engineers are assigned tasks based on immediate need, not necessarily on their desire for growth or the strategic importance of the project. Your manager might be prioritizing other factors like team balance, experience levels, or perceived risk aversion. They may also be unaware of your ambition or the specific skills you want to showcase. This isn’t necessarily a reflection of your performance, but a communication gap.

1. Preparation is Key

Before approaching your manager, thorough preparation is paramount. Don’t just say you want ‘more high-visibility projects.’ Be specific.

Identify Target Projects: Research ongoing or upcoming projects that align with your skillset and offer high visibility. Understand their goals, stakeholders, and potential impact. Look for projects involving microservices architecture, performance optimization, or new technology adoption.
Quantify Your Value: Prepare examples of how your skills (Go concurrency, Rust memory safety, API design, database optimization) can contribute to the success of these projects. Think in terms of reduced latency, improved scalability, or increased developer productivity.
Understand Manager’s Priorities: What are your manager’s key performance indicators (KPIs)? How can your involvement in high-visibility projects contribute to their success? Aligning your request with their goals significantly increases your chances.
Anticipate Objections: Consider potential pushback. Are you perceived as overloaded? Do you lack experience in a specific area? Prepare thoughtful responses.

2. Technical Vocabulary (and how to use it)

Microservices Architecture: Demonstrates understanding of modern backend design. (e.g., “I’m particularly interested in contributing to the new order processing microservice, leveraging my experience with gRPC for efficient inter-service communication.”)
Concurrency: Highlights your Go expertise. (e.g., “Optimizing the data ingestion pipeline using Go’s concurrency primitives could significantly reduce latency.”)
Memory Safety: Showcases your Rust proficiency. (e.g., “The new authentication service would benefit from Rust’s memory safety guarantees, minimizing potential vulnerabilities.”)
API Design (RESTful/GraphQL): Indicates a holistic understanding of backend development. (e.g., “I’d like to contribute to the API design for the customer portal, ensuring a consistent and developer-friendly experience.”)
Database Optimization (Indexing/Query Optimization): Demonstrates a focus on performance. (e.g., “I’ve identified opportunities for database optimization in the reporting module, specifically around indexing and query optimization, which could improve report generation time.”)
Observability (Tracing/Metrics): Shows a commitment to operational excellence. (e.g., “Implementing robust observability through tracing and metrics in the payment processing service will be crucial for identifying and resolving performance bottlenecks.”)
Event-Driven Architecture: Demonstrates knowledge of modern architectures. (e.g., “I’m keen to explore implementing an event-driven architecture for the inventory management system.”)
CI/CD Pipeline: Shows understanding of the full development lifecycle. (e.g., “I’d be happy to contribute to improving the CI/CD pipeline for the platform.”)
Zero-Copy Networking: (Rust specific) Demonstrates advanced knowledge. (e.g., “Leveraging zero-copy networking techniques in the data transfer service could significantly reduce CPU overhead.”)
Data Serialization (Protobuf/Avro): Highlights expertise in data handling. (e.g., “Using Protobuf for data serialization in the inter-service communication will improve efficiency and reduce bandwidth.”)

3. High-Pressure Negotiation Script

(Assume a 1:1 meeting with your manager)

You: “Thanks for meeting with me. I wanted to discuss my career development and how I can contribute even more effectively to the team’s goals. I’m really enjoying my work on [current project], but I’m also eager to take on projects with a higher level of visibility and impact.”

Manager: “Okay, that’s good to hear. What kind of projects are you thinking of?”

You: “I’ve been following the progress on [Target Project 1] and [Target Project 2]. I believe my skills in [Go concurrency/Rust memory safety/API design – choose relevant skills] would be particularly valuable in [specific contribution, e.g., optimizing performance, ensuring security, improving developer experience]. For example, [briefly explain how your skills will benefit the project – quantify if possible].”

Manager: “Those are important projects. We have a lot on our plate right now. Are you feeling overloaded?”

You: “I’m confident in my ability to manage my workload effectively. I’m not suggesting I take on everything at once. I’m looking for opportunities to gradually transition into these higher-visibility roles, perhaps by shadowing a senior engineer initially or taking on a smaller component of the project. I’m also happy to help unblock others to create capacity.”

Manager: “I see. We need to consider team balance and experience levels.”

You: “Absolutely. I understand that. I’m committed to the team’s overall success, and I believe that by contributing to these projects, I can not only grow my skills but also help the team achieve its objectives. I’m open to discussing how we can strategically integrate my involvement to ensure a smooth transition and maintain team efficiency.”

Manager: “Let me think about it. I’ll see what I can do.”

You: “Thank you. I appreciate you considering my request. Could we schedule a quick follow-up in a week to discuss this further? I’d also be happy to provide more detail on how my skills align with the project requirements.”

4. Cultural & Executive Nuance

Be Proactive, Not Demanding: Frame your request as a desire to contribute more, not as a complaint about your current assignments. Avoid phrases like “I deserve…” or “I need…”.
Focus on ‘We,’ Not ‘I’: Emphasize how your involvement will benefit the team and the company, not just your personal career goals. Use phrases like “We can achieve…” or “This will benefit the team by…”.
Show Humility and Willingness to Learn: Acknowledge that you have more to learn and express your enthusiasm for taking on new challenges. Offer to shadow senior engineers or take on smaller tasks initially.
Be Patient: Securing high-visibility projects takes time and effort. Don’t be discouraged if your request isn’t immediately granted. Continue to demonstrate your value and proactively seek opportunities.
Document Everything: Keep a record of your conversations, the projects you’re interested in, and the skills you’re developing. This provides evidence to support your requests during performance reviews.

By following these steps and tailoring your approach to your specific workplace culture, you can effectively advocate for high-visibility projects and accelerate your career growth as a Go/Rust backend engineer.