Programmer Analyst

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not put Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. We need to parse the posting. Key sections: - About the role: The posting includes "Position Overview" and description of role. Could be "About the role". We'll include a

About the role

with paragraph(s) summarizing the overview. - Responsibilities: "Your Day To Day As a Programmer Analyst" bullet list of duties. We'll create

Responsibilities

with

• items. - Requirements: Might be "Required Qualifications". Could be Requirements section. We'll include

  Requirements

  with list. - Qualifications: Might be "Preferred Qualifications". Could be Qualifications section. We'll include

  Qualifications

  with list. - Skills: Might be overlapping with required/preferred. But we can include a Skills section if there is distinct skill list. The posting includes many skill items; but we already have required and preferred. Might combine. However instruction: Prefer a few substantive sections over many thin ones. We could combine Required and Preferred into Requirements and Qualifications. Skills maybe not needed. But we need to decide. - Benefits: "What We Offer" includes competitive salary and benefits package, health, dental, retirement, flexible work schedules, paid time off, professional development, inclusive atmosphere, mission-driven, continuous learning. Also Pay section separate. So we can have Benefits with list of benefits (excluding salary). Pay: we have salary range $70,000 - $103,000. So we include Pay section. - Schedule: Not explicitly mentioned besides flexible work schedules. Could be Schedule section if we have info about schedule. The posting mentions "Flexible work schedules". That's schedule info. So we can include Schedule section with that detail. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title heading. Not include Job ID etc. We must remove boilerplate: The long intro about BWXT, mission statement, etc. That's basically company overview; is that substantive? It's not about the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview may be considered substantive? But it's not about the role; but it's part of posting. However typical job posting includes company description; we might keep it under About the role? The instruction says use headings for sections like About the role, Responsibilities etc. The company overview could go under About the role? Might be considered "About the role" includes role description and maybe company context. But we already have Position Overview. We could include a paragraph about the company under About the role as well. However we need to avoid too much boilerplate. The company description is somewhat generic but still part of posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company overview is not exactly boilerplate; it's descriptive. Might keep. But we need to decide what to include. The posting includes a lot of fluff at start: "At BWX Technologies, Inc.... For more information, visit www.bwxt.com . Follow us on LinkedIn , X , Facebook and Instagram . Welcome to BWXT We believe in empowering our employees..." That's basically marketing. Could be considered boilerplate? Not exactly legal/EEO. Might be okay to keep as part of About the role. But we need to avoid duplication: The posting repeats some phrases like "Familiarity with HTML, CSS, JavaScript (basic to intermediate)." and earlier "Familiarity with front-end technologies such as HTML, CSS, and JavaScript." That's duplicate; we should deduplicate. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep the specifics: e.g., "Must be a U.S. citizen. Must be able to obtain and maintain a U.S. Department of Energy (DOE) Q clearance." That's a requirement. Also "Selected applicants are required to successfully complete a pre-employment check and drug screening." etc. That's also requirement/legal but maybe we keep as part of Requirements. We need to exclude EEO statement, etc. The posting includes a long EEO paragraph at end; we should remove that. Also remove lines about recruiters/agencies, etc. Also remove "Job Segment: .NET, Testing, Web Design, Developer, Recruiting, Technology, Creative, Human Resources" maybe not needed; it's metadata but could be considered minor; we can drop. We need to output only HTML fragment. Let's structure:

  About the role

  ... (company overview + position overview)

  Responsibilities

  • Design, develop, test, and maintain applications using C#, .NET Framework / .NET Core.
  • Debug, troubleshoot, and optimize application performance.
  • Reading and writing SQL queries.
  • Work independently or collaboratively in a team environment.
  • Collaborate with team members and stakeholders within the business to gather and analyze requirements for software development projects.
  • Contribute to all phases of the software development lifecycle using Agile/Scrum methodology.
  • Participate in code reviews and follow best practices.
  • Maintain existing applications and implement enhancements.

  Requirements

  • Bachelor’s degree in computer science, information technology, or a related field.
  • Minimum of two (2) years of directly relevant, hands-on experience in .NET development.
  • Strong knowledge of C#, .NET Core / .NET Framework.
  • Experience with .NET, ASP.NET, Entity Framework, and API-based integrations.
  • Good understanding of SQL Server and database design.
  • Strong understanding of Object-Oriented Programming (OOP) principles.
  • Familiarity with front-end technologies such as HTML, CSS, and JavaScript.
  • Experience with source control systems such as Azure TFVC / Git.
  • Excellent attention to detail and time-management skills.
  • Strong oral and written communication skills.
  • Strong analytical thinking and problem-solving capabilities.
  • Ability to work independently or on a team.
  • Must be a U.S. citizen.
  • Must be able to obtain and maintain a U.S. Department of Energy (DOE) Q clearance.

  Qualifications

  • Experience with Entity Framework / LINQ.
  • Experience with WPF (Windows Presentation Foundation).
  • Knowledge of CI/CD pipelines.
  • Experience maintaining or replacing legacy application systems.
  • Experience working in Agile/Scrum environments.

  Benefits

  • Competitive salary and benefits package, including health, dental, and retirement plans.
  • Flexible work schedules and paid time off to promote a healthy work-life balance.
  • Professional development opportunities, including mentorship programs and sponsorship for continuing education.
  • An inclusive atmosphere that celebrates new perspectives and supports collaboration between different generations.
  • The chance to be part of a mission-driven organization making a positive impact on the future of energy.
  • Opportunities for continuous learning and training to grow throughout your career.

  Pay

  The base salary range for this position in Tennessee (US-TN) at the start of employment is expected to be between $70,000 and $103,000 per year.

  Schedule

  Flexible work schedules are offered.

  We need to ensure we didn't include any filler like "commensurate with experience". Not present. Check for duplication: We listed familiarity with HTML, CSS, JavaScript only once under Requirements. Good. Check that we didn't include any legal/EEO boilerplate: We omitted the long EEO paragraph, recruiter agency stuff, etc. Check that we preserved all substantive info: Did we miss location? Location: Onsite in Erwin, TN. Should we include that? It's substantive. Could be part of About the role or maybe a separate section? Not among headings list but we could include in About the role paragraph. Let's add location in About the role. Also we missed "Your Day To Day As a Programmer Analyst" heading; we turned into Responsibilities. Also we missed "Through development and maintenance of software applications, this team member will support the BWXT focus on applying technology to solve business problems and create better customer experience." That's part of About the role. Also we missed "Our ideal Programmer/Analyst is highly skilled in development and maintenance of software applications using Microsoft technologies in an agile environment." That's also part of About the role. Also we missed "Successful candidate will have a proven and thorough knowledge of analyzing, designing, developing, testing, implementing, problem-solving, and understanding of best practices for software solutions." That's covered in Requirements maybe. Also we missed "This person will be a core member of the development team, having various opportunities to work as a part of a development team and with stakeholders across the organization." That's covered. Also we missed "As a federal government contractor, BWX Technologies, Inc. and any subsidiaries, affiliates and related entities (“BWXT” or the “Company”) complies with all federal, state, and local laws and customer requirements regarding health and safety protocols. As such, all BWXT new hires will be required to adhere to applicable Company health and safety requirements within the workplace as a condition of employment." That's substantive but maybe could be part of Requirements or Benefits? It's a condition of employment. Could be added to Requirements as a bullet. But we might consider it boilerplate? It's not EEO; it's a specific requirement about health and safety compliance. Might be worth including. However the instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is about health and safety compliance, not exactly EEO. Might be considered legal boilerplate? It's a statement about complying with laws. Could be considered boilerplate. Safer to omit? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is legal boilerplate about health and safety. Likely to be removed. So we can omit. Also we missed "All candidates must be U.S. citizens. Selected applicants are required to successfully complete a pre-employment check and drug screening. In addition, the position may require the ability to obtain and maintain applicable federal eligibility requirements for access to classified/sensitive information or matter which involves an extensive criminal and financial background investigation, drug test, previous employment, and reference verifications." That's substantive about citizenship, clearance, background check. We already have citizenship and DOE Q clearance. The pre-employment check and drug screening, plus background investigation details are extra. Should we include? It's substantive. Could add to Requirements. We need to decide whether to include that. It's not boilerplate; it's specific to the role. So we should include. Add bullet: "Must successfully complete a pre-employment check and drug screening." And maybe "May require ability to obtain and maintain applicable federal eligibility requirements for access to classified/sensitive information, involving extensive criminal and financial background investigation, drug test, previous employment, and reference verifications." But that's somewhat redundant with DOE Q clearance. However we can include as separate bullet. But we must avoid duplication. The DOE Q