Job Description :

.Net Application Developer (US Citizen Only)

Portland, OR

Duration – 12+ months (one Base Period of 12 months and four Option Periods of 12 months each)

 

Need write-up for below highlighted points.

 

• Experience in large “enterprise” development projects

• Especially .NET intranet line of business apps Page 24 of 34

• History of starting work on existing codebases

• Especially ones with a backlog of bugs

• Experience working with business owners turning business needs into technical requirements.

• Experience working as a part of AGILE teams

• Support by organization to keep key personnel regularly trained and up to date

• Organizational “reach back” to support key personnel on project.

 

 

 

Application Developer Demonstrate professional experience in designing and developing web-based applications. Narrative response shall highlight the proposed candidate’s experience with app design and development including:

 

Mandatory Skills and Qualifications:

 

• Reading, analyzing, and understanding complex code bases of existing projects.

• .NET programming languages. (C# or VB)

• Web services

• Browser stack (HTML, CSS, JS)

• Accessible (WCAG) and secure development practices (e.g., OWASP, NIST)

• Formal AGILE development as a part of team environment.

• Formal DevOps, working knowledge of well-known version control systems (such as git or team foundation services).

• Intranet and internet focused, browser based, large scale applications.

• Database operations and design for Oracle and SQL Server.

• Working with business owners and subject matter experts to turn business needs into technical requirements. Optional Experiences:

• PHP development background.

• Familiarity with natural resource management, especially Forestry.

• Experience in a government contracting. Page 3 of 34

• Experience developing in a government intranet.

 

15.1. Operations and Maintenance

 

• Complete all BLM training and follow policies for network access.

• Communicate with BLM interdisciplinary teams. (e.g., IT Security, IT System Engineers, Data Standards, GIS, etc.)

• Fully document all work needed or completed.

• Participate in the monthly/weekly BLM conference calls and in-person meetings.

• Available to work hours so they are available during hours in PWS 7.0

• Stay current with the state of the industry (including but not limited to attending vendor conferences, career development training, role development training).

• Provide technical, operational, and troubleshooting support to FRIS development team and field staff in the use of FRIS application modules or related software.

• Be able to plan to respond to emergency events that fall outside of normal working hours. (For example, the rare instance of working on a weekend to restore a system or attending an afterhours deployment. For perspective the team has had two such events in the past ten years.)

 

15.2 . Application Development

 

Create and maintain a work log (e.g., user stories, bugs, tasks, etc.) and maintain project management software (e.g. Microsoft Azure DevOps) in relation to the development of applications.

  1. Writing entries in the work log.
  2. Estimating time to completion of tasks. Page 7 of 34
  3. Tracking tasks in development cycles.
  4. Validating work from development.

Analysis

  1. Work with project manage and team or understand requirements and offer best practices in a team environment.
  2. Troubleshoot existing software.
  3. Troubleshoot dev environments, hosting environments and deployment tools.

Create or maintain BLM code and 3rd party software frameworks.

  1. Follow OR 955.4 coding standards.
  2. Analyze most appropriate needs (build vs buy).
  3. Create pull requests for BLM to review and deploy.
  4. Keep project dependencies up to date.
  5. Proactively apply security updates.
  6. Working in multiple environments (e.g., dev, prod, stage, train)
  7. Managing source control in a team environment. (e.g., Git, TFS)
  8. Create and maintain WCAG 2.0 (or better) accessible deliverables.
  9. Responsive development practice for mobile devices.

• Testing

  1. Create automated tests for all submitted code due when the code is submitted
  2. Create testing procedures for manual testing delivered as written documentation submitted with any code if automated testing is not reasonable due when the code is submitted.
  3. Protecting against regression by utilizing existing tests and test documentation before submitting any code.

• Deployment and Documentation

  1. Track released versions, features, patches, and bug fixes.
  2. Document release note or other customer communication documents
  3. Create technical documentation when directed.

 

Technical Factor 1 – Qualifications of Key Personnel:

 

The Offeror shall demonstrate its technical approach in performing the tasks outlined in the PWS – including a discussion on the background and experience of the organization and its key personnel to demonstrate their ability to work on the BLM’s existing project.

 

• Experience in large “enterprise” development projects

• Especially .NET intranet line of business apps Page 24 of 34

• History of starting work on existing codebases

• Especially ones with a backlog of bugs

• Experience working with business owners turning business needs into technical requirements.

• Experience working as a part of AGILE teams

• Support by organization to keep key personnel regularly trained and up to date

• Organizational “reach back” to support key personnel on project.

 

Technical Factor 2 – Technical Approach:

 

• The Offeror shall demonstrate its quality control procedures and review; the Offeror’s discussion shall support how the tasks/deliverables will be evaluated for full performance and acceptability of work from the Offeror’s viewpoint.

• The Offeror shall provide a discussion of the proposed methods and techniques for completing each task; appropriateness and cost efficiency in the use of resources should be considered.

• The Offeror shall demonstrate an understanding of the issues that may occur during the contract period and how these issues might be resolved.

• The Offeror shall demonstrate proposed work schedules according to PWS tasks/deliverables and provide a timetable for tasks/deliverables.

• The Offeror shall demonstrate its quality control procedures to ensure services are performed in accordance with the PWS. The Offeror shall define its quality control management approach that satisfies the requirements defined herein.

             

Similar Jobs you may be interested in ..