Self Review as Senior Engineer @ Podium

How did you have an impact since the last review cycle?

Identify the areas where you excel and connect them to relevant areas of the competency matrix. Share specific instances where your actions led to meaningful outcomes. Emphasize how these successes benefited your team or advanced organizational objectives.

Boosted Inbox Magic's test coverage by 56%, adding around 14,000 lines of code. This improved reliability and maintainability. This cut down future technical debt and lowered the risk of bugs for the team. (Technical Craft: Code Quality, Efficiency).
Introduced contact statuses in inbox, enabling intent-based routing and automated lead status assignment. Despite unexpected complexity, the successful launch streamlined customer workflows and increased operational efficiency.
Led the Review Rocket (RR) deprecation in Kazaam. This was a key, high-risk project that affected many teams. I migrated Azeroth calls while ensuring minimal impact on customers. Leadership recognized this achievement.
Led the effort for ROI-based conversation views in Jerry Reporting from the Home Page. Orgs can now better grasp customer value from Jerry and view related conversations.

What didn't go well since the last review cycle?

Be candid about any competencies or behaviors where you see room for improvement, and link them to situations or projects where outcomes fell short of expectations. Discuss why these challenges arose, how they impacted results, and what you've learned that can inform future efforts.

Contact Status Initiative Complexity: Architectural links caused delays and more ADRs. This experience improved my understanding of architecture. It prepared me to manage similar projects, like Group Messaging.
Review Rocket Migration Challenges: The work revealed unpredicted instances. Dealing with this complexity improved my communication and project management skills. It showed me how important it is to work together with other teams.
Cortex Workload Management: Managed tough Cortex maintenance tasks for KTLO services. These tough tasks offered a chance to improve prioritization. They also highlighted the need for better resource planning in future quarters.

What growth areas do you want to focus on?

Outline the specific competencies and skills you plan to reinforce or improve. Explain how building upon existing strengths or addressing gaps can lead you to better outcomes for your projects and team. Highlight concrete steps, resources, or support you'll use to drive meaningful improvements in performance.

System Architecture: I want to improve my skills to lead changes in projects lasting over 2 years. I will dive deeper into cross-team architecture talks. I'll work with architects to understand and shape Podium-wide architecture choices.
Efficiency: Find and lead projects that boost engineering productivity beyond my team. This can include making reusable tools or automating tasks. I will suggest solutions for cross-team problems. I'll use my recent experience with Cortex and big refactors to help.
Influence: Increase my organizational impact by facilitating meaningful, cross-pod technical discussions. I want to boost my leadership visibility. I will share insights from successful projects and support improvements in documentation. This will help raise the technical quality and clarity across Podium.