Applications Architect - Java and Oracle
The Application Architect is responsible for defining the system, technical, and application architectures for small to medium systems development projects.
Core Job Responsibilities
· Serve as a technical design lead on small- to medium-sized development projects using complex technologies and integrations (e.g. Java/Java EE).
· Guides project lifecycle, including requirements definition, design, development, testing and deployment.
· Applies a deep understanding of modern development techniques and best practices (e.g. Java/Java EE).
· Serves as a mentor, providing guidance to less experienced developers.
· Create and manage standards and standard compliance as part of design.
Qualifications for this role
· Preferred practical experience with Oracle ADF, Jdeveloper, Oracle Fusion Middleware products (Web Center Portal, Web Center Content, OBIEE, SOA/BPEL and Oracle Identity and Access Management), and Oracle EBS and related modules.
· Experience with Java EE application servers (e.g. WebLogic) and modem server techniques such as Spring Boot.
· Experience with deployment methodologies ( i.e. Docker).
· Experience creating and securing Micro and Web Services.
· Familiarity or experience with popular open source Java frameworks such as: Spring, Hibernate, STRUTS, JUnit, and JSON.
· Experience using iterative/agile development methodologies such as RUP, XP or SCRUM, desirable.
· Comfortable working in both the Windows and Linux/Unix environments.
· Must have current hands-on coding skills in addition to strong architecture and design experience.
· Strong interpersonal, written, and verbal communication skills.
· Bachelor’s Degree in Computer Science or Engineering; or equivalent experience is required.
· Any relevant certifications are a plus.
· Four+ years of experience developing web-based systems using Java/J2EE (including exposure to older technologies such as JSP, JMS, EJB, XML and related technologies) as well as more modern techniques and tools such as AngularJS, JSON over REST.
· Must have experience using modern/accepted software design patterns and other proven design idioms.
· Travel required when necessary; expected to be less than 5%.