Intermediate Software Developer

Responsibilities include, but are not limited to

• Responsible for full-stack software development to include back-end database script artifacts (tables, indexes, functions, stored procedures, etc.), middle tier software code that moves data from databases, applies any business rules and responds to client requests, and client software that covers a wide range of user / data consumer interactions.
• Work under general technical direction, to develop, modify moderately to highly complex web-based applications.
• Design, code, test, debug, document, and maintain full stack web-applications.
• Work in a software development life cycle, apply security and vulnerability best practices, and require little or no instruction and guidance in performing routine tasks.
• Collaborate with other members of the DEVCOM CBC software development team, understand and implement change requests, have superb interpersonal and communication skills.
• Participate in team meetings with the government to improve understanding of the mission, tools, concepts, frameworks, and increase effectiveness in delivering software code.
• Develop and deliver C# and Microsoft .NET Software Code for DEVCOM CBC KDM. Includes proficiency with old and new Microsoft .NET Frameworks (.NET Framework, .NET Core, etc) There is legacy code that needs to be maintained. Some of the legacy code may need to be refactored, which may include re-writing to use newer framework versions.
• Work proficiently in the latest in library code for Microsoft .NET and demonstrate the ability to effectively apply Microsoft and other 3rd party library code written for .NET to delivered software code solutions.
• Develop and deliver Web Based Client Software Code for DEVCOM CBC KDM using HTML, JavaScript, CSS, and associated frameworks such as Bootstrap, jQuery, etc.
• Develop and deliver SQL Database Scripts for DEVCOM CBC KDM; includes developing SQL database scripts to create, remove, update database objects such as tables, indexes, stored procedures, user functions, etc. Scripts not only must account for changing the schema, but also transforming any data because of a schema change. Scripts must be written with database version control in mind. The IS solutions exist in several environments such as developer, test, staging and production on one or more devices. Therefore, the database in these environments may exist in various versions or states. Any developer or build machine should be able to run scripts from a given database version / state up to the latest.