• Experience as a mentor, tech lead or leading an engineering team
• Experience leading the architecture and design (architecture, design patterns, reliability and scaling) of new and current systems
• Experience programming with at least one modern language such as Java, C++, or C# including object-oriented design

Desirable

• The AWS Load Balancing team is looking for software engineers to join the Migration Analytics team, this team builds services to allow safe migration and on-boarding to AWS Load Balancing products
• As a Software Engineer, you will play an integral role in building migration tools, services and health analytics for the AWS load balancing org
• You’ll have a unique opportunity to build software that accelerates on-boarding of customers to AWS services, you’ll drive a step-change in Amazon’s ability to simplify our customer’s journey to AWS and build their confidence by creating Analytics to expose migration health insights
• You’ll work on Amazon’s hardest problems, building high quality, architecturally sound systems that are aligned with our business needs. You’ll strive for simplicity, demonstrate significant creativity and high judgment, and contribute towards intellectual property through patents.
• Solving problems at scale excites you
• You are considered a technical leader on your team. You work efficiently and routinely deliver the right things with limited guidance
• Your work focuses on complex, ambiguous problem areas in existing or new software initiatives. You take the long term view. You consider where each system is at in its lifecycle and where appropriate, proactively fix architecture deficiencies
• You make existing systems simpler (e.g. by consolidating redundant systems, deleting unnecessary code, or removing/updating out of date documentation)
• You are able to take the lead on large projects that require the work of your team. You know how to divide a software project into parallel work that can be performed by you and other SDEs and then reassembled successfully into a cohesive launch
• You understand the business impact of your systems and show good judgment when making technical trade-offs between your team’s short-term business or operational needs and long-term technology needs. You are a key influencer in team strategy
• You drive mindful discussions with customers and peers. You bring perspective and provide context for current technology choices and guide future technology choices
• You understand that not all problems are new (or require new software). You make appropriate architectural trade-offs (e.g., coarse or fine grained service separation?) Your code submissions and approach to work are exemplary – your solutions are inventive, secure, easily maintainable, appropriately scalable, and extensible
• You write software that is easy for others to contribute to. You take ownership of team architecture, providing a system-wide view and design guidance. You make things simpler. You drive engineering best practices (e.g., Operational Excellence, Security, Quality, etc.) and set standards
• You work to resolve the root cause of endemic problems including areas where your team limits the innovation of other teams (bottlenecks). This may require you to influence software decisions made by other teams. When confronted with discordant views, you are able to find the best way forward and influence others to follow that path (build consensus)
• You contribute to the professional development of colleagues, improving their technical knowledge and the engineering practices. You ensure your team is stronger because of your presence, but does not require your presence to be successful