Taking Initiative

In the realm of software engineering, "taking initiative" varies based on your role within the team. Understanding your position and how you can contribute effectively is essential.

Exhibiting initiative demonstrates your ability to think critically about your work and to solve problems independently, without waiting for direction from your manager.

Consider these initiatives:

• Streamlining code by eliminating duplication and refactoring where necessary.
• Adding tests to areas that lack coverage.
• Enhancing documentation for clarity and future reference.
• Identifying cost-saving opportunities, similar to how Uber significantly cut down logging expenses.
• Optimizing the performance of slow services by addressing quick wins.
• Improving the onboarding process by documenting key workflows.

Taking initiative doesn't mean you have to handle everything on your own. If you spot an issue, you can propose potential solutions and create a task for your team lead or project manager to prioritize. To ensure the task gains traction, clearly articulate the business value of addressing the gap you identified.

By proactively working to enhance the overall system, you will gain appreciation from your peers. Making a noticeable impact will certainly help you stand out—but this won't happen without some self-promotion.

Promote Your Achievements

Taking initiative and doing great work means little if no one is aware of your contributions.

Standing out hinges on recognition. Share your successes with your team and highlight how your initiatives have improved processes. Use your company's communication tools (like Slack or Teams) to inform other engineers and managers about your accomplishments.

Promoting your achievements is vital, as it positions you as a self-motivated professional who drives change within the organization. Additionally, consider documenting your wins for future reference during performance reviews or interviews.

Reviewing with Purpose

Regardless of your experience level, make it a habit to review pull requests (PRs) frequently and thoroughly. This practice not only enhances your learning but also allows you to influence your team positively without writing code.

Effective communication and providing constructive feedback are invaluable traits for any team member. Even if you're at a junior or mid-level, don't hesitate to review, inquire, and present new ideas to more experienced colleagues.

You have two potential outcomes:

1. You present a valuable idea that is recognized and acted upon—a clear win.
2. You propose something that may not be well-received, but this offers a learning opportunity—still a win.

Recognizing that you can contribute meaningfully, even as a junior, will help you stand out. For additional insights into effective code reviews, I recommend exploring content by Curtis Einsmann.

It's important to remember to pace yourself; implementing these strategies takes time and effort, and it's a continuous journey for many, including myself. Avoid burnout by focusing on impactful work.

Conclusion

These three strategies can significantly enhance your career as a software engineer. Keep them in mind during your performance evaluations and strive to integrate them into your daily work routine. Your proactive efforts can lead to substantial improvements for your team, your company, and the broader community.

Explore strategies to stand out among software engineers with insights from this video.

Discover four essential tips to differentiate yourself as a software engineer through this informative video.