Senior Software Engineer
CurrentBecoming a Senior at DANA Indonesia, I was responsible for becoming a System Owner for DANA Deals and Pesan Instant services with the 2 subordinates' support.System Owner is responsible for Effort Estimation, System Quality, Team Performance, and Stakeholder Satisfaction.The key point for the System Owner1. Accountable Estimatation.The estimation should consider the Product Requirement, Good System Design, and Team workload. Balancing those three aspects is the Art of… Show more Becoming a Senior at DANA Indonesia, I was responsible for becoming a System Owner for DANA Deals and Pesan Instant services with the 2 subordinates' support.System Owner is responsible for Effort Estimation, System Quality, Team Performance, and Stakeholder Satisfaction.The key point for the System Owner1. Accountable Estimatation.The estimation should consider the Product Requirement, Good System Design, and Team workload. Balancing those three aspects is the Art of Tech Leadership.2. Leadership is not by Position but By Influence. - Lead by Example, if you expect your team to produce a clean code, your code has to be there first. If you expect ownership of your team, you have to stand first if any issue comes up. - Expose them to Growth, if your team has challenges, let them explore the solutions with guidance. - Reliable for Teammates, If your team feels stuck, listen and understand their work or personal problems. Take responsibility for any good or bad situations.3. Delivering System Quality. - Measurement of the RPS, Latency, and Success Rate. - Push the API latency to less than 100ms by leveraging Caching and RPC communication within service-to-service, to reduce HTTP network and encoding overhead. - Maximizing the RPS per instance to produce a cost-efficient application. - The developers must review the QA Test Plan and give the context about the Must-Have Scenarios for testing *only the Developer and God know the logic behind the API.4. Maintainable System - Defining the Design Pattern rule with the team. - Documenting your API/Changes Articulatively by API Specs, State Management, Diagram, ERD, etc. - If your engineer develops a new logic or revamps the old logic, please make sure they have the function switcher to switch off.5. Clear Goals and Objectives. - Talk to the Head/Managers/VP to define the Team Objectives. - Set goals and execution strategy. Explain boldly to the members. Show less