Software Engineer

Requirements

• Years of experience: 0-2 years of experience
• Degree requirement:
  Bachelor's degree in computer science, software engineering or relevant field required. Will accept a Master's Degree.
• Do you accept internships as job experience:
  Yes
• Are there past or additional job titles or roles that would provide comparable background to this role:
  Software Engineer, Modernization of COBOL and/or FORTRAN.

• Software development: strong programming fundamentals and practices; ability to understand, refactor, and modernize complex legacy code bases; experience with C++, code conversion, debugging, version control
• Requirements Analysis (see below in additional skills)
• Analytical Thinking: ability to work with large datasets and derive meaningful insights, strong problem solving skills in evaluating simulation outputs and discrepancies, ability to connect quantitative results with real-world business outcomes

(Required)

• Programming
  
  Languages:
  
  Knowledge of basic concepts and capabilities of programming; ability to use tools, techniques and platforms in order to write and modify programming languages.
• Business Statistics:
  Knowledge of the statistical tools, processes, and practices to describe business results in measurable scales; ability to use statistical tools and processes to assist in making business decisions.
• Query and Database Access Tools:
  Knowledge of data management systems; ability to use, support and access facilities for searching, extracting and formatting data for further use.
• Requirements Analysis:
  Knowledge of tools, methods, and techniques of requirement analysis; ability to elicit, analyze and record required business functionality and non-functionality requirements to ensure the success of a system or software development project.

(Required)

• Accuracy and Attention to Detail:
  Understanding the necessity and value of accuracy; ability to complete tasks with high levels of precision.
• Communication and Stakeholder Management: ability to explain technical concepts to non-technical users; requirements gathering and user engagement