IT - Software Engineer II

Bozzuto’s is seeking a Software Engineer II

BASIC PURPOSE AND OBJECTIVE OF THE POSITION:

Designs, modifies, develops, writes, and implements software programming applications. Supports and/or installs software applications/operating systems. Participates in the testing process through test review and analysis, test witnessing and certification of software. Requires a bachelor's degree in a related area and 2-5 years of experience in the field or in a related area. Familiar with standard concepts, practices, and procedures within a particular field. Relies on limited experience and judgment to plan and accomplish goals. Performs a variety of tasks. Works under general supervision; typically reports to a manager. A certain degree of creativity and latitude is required.

MAJOR RESPONSIBILITIES OF THE POSITION:

Analyses, designs, estimates, codes, tests and implements new programs or enhancements to new/existing business computer systems                                                

Document and maintain existing computer systems by reviewing current programs and workflows.                                                                  

Investigates and resolves system and program problems with customers both Internal or external.   Provide 24-hour support of assigned key systems.                              

KNOWLEDGE OR KNOW-HOW REQUIRED:

• Proven skills in the area of analysis, problem-solving, and good communication skills
  (2-5) years in technical programming; MUST include OO (Object Oriented) design and development.
  Experience with full life-cycle software applications development (i.​e.​, design, construction, testing, and implementation)

MAJOR CHALLENGES:

Solve difficult system problems (maintenance)

Solve design problems and define basic system requirements

Complete the above with little or no documentation available for reference

RESPONSIBILITY AND DECISION MAKING:

  Most often the responsibilities of the position will require analyzing information where established procedures may not exist.  Conclusions to issues may be reached were there could be considerable variation in the interpretation of the solution.  Information Systems is subject to rapidly changing technology and procedures must change to reflect this.   For some existing systems there is no documentation that is useful, and for new systems it is often necessary to develop new procedures to adopt the new technology.