Software Development Engineer 2

Responsibilities:

• Take a business problem and come up with the technical strategy (push vs pull, etc., real-time vs batch sync vs async) within the team's high-level design and lead the implementation.
• Need minimal directions or guidance and collaborate with SDEs across teams working on the same or similar business problem.
• You showcase exemplary behavior in your work, your design, delivery, and code processes, setting examples for your team.
• Influence your team's technical and business strategy by suggesting novel approaches.
• Able to communicate your ideas and get feedback from different stakeholders and drive convergence to achieve the right outcomes.
• Proactively mentor the rest of the team and help in hiring.
• Ensure design or architectural deficiencies are addressed and routinely simplify integration of your peer teams with your team's software.
• Consistently lead delivery of valuable features.
• Continually propose and drive process improvements.
• Help elaborate requirements where necessary.

Programming:

• Demonstrate in-depth knowledge of IDE, language, and toolset in the language of choice.
• Implement critical path components in a large or complex project.
• Demonstrate excellent understanding of language and framework and a good working knowledge of the abstraction layer underneath.
• Profile and optimize code.
• Understand the threading model and concurrent programming.
• Comfortably test drive any feature/comfortable with the TDD cycle.
• Demonstrate a good knowledge of other programming languages and paradigms and when to apply them.
• Comfortably debug/find complex problems.

Design:

• Identify and apply appropriate design patterns to problems.
• Comfortably develop large features.
• Understand idempotence.
• Actively practice the Boy Scout principle of leaving design code in a better state than when it arrived.
• Demonstrate a good understanding of cohesion, SOLID, and how to apply it.
• Understand the importance of the domain model and can coherently model a problem domain within a given context.
• Anticipate medium-term (3-6 month) vectors of change and design and abstracts accordingly.
• Understand and appreciate simplicity and the value of removing code.
• Understand design patterns such as CQRS and eventual consistency.
• Understand how to design for performance at all levels.

Development Practice:

• Automate everything by default.
• Build a CI/CD pipeline.
• Automate security scanning and performance testing as part of the build.