Systems Engineer

The software engineer should be seen as a rock-solid engineer who is a master of their specific domain. The software engineer is capable of owning technical design for projects of moderate complexity, and understands the tradeoffs in creating good software in their area. They hold a depth of knowledge in systems that enables them to debug those systems effectively without flailing. In addition to writing consistently high-quality code they are aware of industry best practices and trends, and have acquired at least one major skill outside of programming such as monitoring, performance optimization, documentation, integration testing, visual design.

The software engineer gets a lot done. They are responsible for complex tasks and complete them despite roadblocks, grabbing others for help or insight as necessary. The engineer 1 requires very little oversight beyond high-level direction; they can take a complex user story, break it down into sub-tasks, and complete their sub-tasks with relative ease. The software engineer shows initiative beyond knocking tasks off a list; they are able to identify and suggest areas of future work for themselves or their teams. They seek evidence to support their ideas and start to build cases for these ideas. They deliver products to QA that they believe are well-baked and bug-free.

The software engineer has end-to-end responsibility for projects of increasing complexity that encompass more than their own development. They contribute to the common code bases and standards for the team. They understand the business that their code supports, and possess empathy for the users of their software; they use this understanding to influence their task prioritization. They assist QA in identifying and validating test cases and can identify regression risks in their features. In general, they can identify risks in code, features, and design, and communicate these to the appropriate parties.

The software engineer is known outside of their core team as a technology leader. They participate extensively in code reviews, and mentor others via code reviews and pairing, as well as frequently presenting at Lunch and Learn and team meetings. They work effectively with non-tech members of their pillar. They are able to identify problems with requirements and help their team course-correct around these issues.

Minimal Qualifications

• 4- 5+ years software development experience including expertise in C#/.NET
• Experienced in Window Presentation Foundation (WPF)
• Web Development using HTML5 and CSS
• Expert full stack, full time software development professional
• Demonstrated expertise of software delivery processes - ability to work both independently and as technical member of an agile team
• Exceptional written, verbal, interpersonal, and influencing skills
• Mastery of relational database design patterns and querying skills
• Mastery of many/all Unit, Web, Integration, and Performance testing frameworks
• Expert with source control tools and methodologies (Subversion or TFS or Git)
• Expert in using dependency injection frameworks.
• Deep experience with business intelligence, data visualization and reporting platforms.
• API/Web Services development experience.
• JavaScript frameworks (AngularJS, jQuery etc)
• Experience in using ASP.NET, .NET Framework, MVC, JavaScript frameworks (AngularJS, jQuery etc.), UML, TFS, HTML4 5, CSS, XML, SOAP, IIS, SQL Server, Oracle, Team Foundation Server as well as Unit Testing

Preferred Qualifications

• Financial industry knowledge/experience is a plus
• Azure, SaaS, PaaS, IaaS, SOA, web services and micro-services

Essential Duties and Responsibilities

Understands and makes well-reasoned design decisions and tradeoffs in their area; able to work in other areas of codebase without guidance.

Doesnt flail while debugging.

Persistent in the face of roadblocks; dispatches them efficiently pulling in others as necessary. Requires minimal direction/oversight.

End-to-end responsibility on projects of increasing complexity; contributes to common code.

Looks at test cases and advises QA on adjacent code/regression impact.

Understands the business supported by their pillar or the pillars they support.

Communicates technical decisions through design docs, tech talks, and the wiki.

Mentors junior engineers via pairing, design reviews, and code review. Contributes frequently to Lunch and Learns.

Additional Duties and Responsibilities

Demonstrates knowledge of industry trends, our infrastructure and our build system, including VSTS/TFS, Octopus Deploy and git.

Takes the initiative to fix issues before being assigned to them. Seeks empirical evidence through proof of concepts, tests and external research.

Delivers complex products to QA that they believe are well-baked and bug free.

Partners with product and analytics and drive requirements that take into account all parties needs.

Possess empathy with the user of the software they are producing and uses that empathy to guide decision-making.

Identified problems/risks of own work and others.

Communicates effectively across functions; is able to work well with product, Design, Analytics, etc, as necessary.

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.