The Software Engineer II role is transitioning from a support role into a technical leader on the team. The engineer is also transitioning from learning as a primary focus to mentoring, leading, and helping others grow on the team. They are starting to be recognized as experts in their area.
Key Responsibilities
Improving knowledge and understanding of core concepts of SE, coding small features, coding large features, mentoring others, learning and applying industry trends, creating and improving internal libraries and tools, partnering with team-specific stakeholders, designing features, participating and leading in production support, teaching best practices internally
Breaks large problems into smaller.
Exercises judgment within existing patterns to solve moderately complex problems.
Persistent in the face of roadblocks; dispatches them efficiently, pulling in others as necessary
Requires minimal direction/oversight
Takes the initiative to fix issues before being assigned them
Identifies holes in product direction and works with Product to resolve them
Seeks empirical evidence through proof of concepts, tests, and external research
Delivers complex products that are well-tested and bug-free
Does work that requires deep understanding for one technical domain, language, or platform.
Troubleshoots and resolves functional issues in code
Plans delivery of a coarse-grained business need within one application
End-to-end responsibility on projects of increasing complexity
Contributes to shared code
Understands the business supported by their code
Partners with product and analytics to drive requirements that take into account all parties' needs
Identifies problems/risks of own work and others
Consistently helps new hires and more junior staff to "level up" and become more proficient over time
Works independently on small to medium size efforts within a team or project
Communicates technical decisions through design docs, tech talks, and the wiki
Communicates effectively across functions; is able to work well with Product, UX, Analytics, etc.
Proactively identifies problems with requirements (lack of clarity, inconsistencies, technical limitations) for their own work and adjacent work, and communicates these issues early to help course-correct
Minimum Qualifications
2 or more years of experience and a bachelor's degree in Computer Science, Engineering or related field; OR equivalent relevant professional experience
1 year of experience working with data stores such as SQL or NoSQL databases
Preferred Qualifications
Bachelor's degree in IT, Computer Science, Engineering, or related field
