Role : Senior Developer – J2EE Full Stack

Description

To be responsible for the Design, Implementation, Maintenance & Operations of J2EE full stack based
“access & alerts management“applications of Engineering & PLM tools

Needs to follow the software development process by using dedicated tools and ensuring the on-time,
quality delivery of software releases independently.

Qualification & Experience

Engineering graduate (BS/BTech/MS/MTech) with 5-7 years of experience as J2EE full stack Developer.
At least 5 years of experience in applications development, maintenance & run mode operations using
following is preferred.
Backend: JAVA/J2EE
Frameworks: Spring, Hibernate, JPA
DB: Pl/SQL, MySql, Oracle
JS Framework: NodeJs, JQuery, Angular or ReactJS
CI/CD Tools: Ant, Maven, Jenkins, Openshift
Ability to collaborate with a diversity of customer's teams to address important issues and to resolve
them.
Experienced in collaborating with internal and external stakeholders, adaption and learning of the
business processes speak of the customer especially around PDM and Configuration management
processes
Experienced in working within a product delivery lifecycle, Agile/scrum experience in software
development (plus)

Mandatory:
Development experience using JAVA/J2ee, REST, XML Parsing APIs, Threads
Java Frameworks: Spring, Ability to work with Vaadin/GWT or Swing.
Experience in any of the cloud platform: Openshift (preferred)
Development experience in Front End Technologies: JavaScript, JQuery, HTML, CSS
Experience Working with NoSql Database
Expertise in Troubleshooting Issues on Tomcat
Advanced knowledge of PL/SQL (oracle)
Basic Unix and shell scripting knowledge
ORM Frameworks (JPA, Hibernate)

Nice to have:
Software Development and Design Patterns
Data Modeling using Xml and JSON
Analysis skills
UNIX shell scripting (for operational activities)
ANT build scripts
Requirements Engineering / Mgmt.
Communication Moderation & Project Mgmt., Skills
Good Understanding of development activities
Organization
Concepts
Means (e.g. systems, purposes, terminology)
Good Understanding of Operational Support
Incident Mgmt.
Req. Mgmt.
Monitoring
E&A

Environment:
Windows operating system (dev environment)
Unix (solaris 10) (operation environment)
Eclipse / JDK
SVN (Source Code Repository) and GIT.
Jenkins (Continuous build Integration solution), Maven, ANT
ServiceNow: Incident Ticketing System
MS SharePoint Server (Project Mgmt)

Major activities:
Organize workshops (dev team / business / process owner / key users)
Coordinate and Support DevOps Team activities
Priorities / Efforts
Impediments / Escalations
Critical Issues Mgmt. / Service Continuity
Regular Status Reporting
Roadmap Management
Requirements Mgmt.:
Review / Write Requirements / Specification
Classify requirements
Manage Project Backlog (Functional / Non-Functional Requirements)
Deployment Planning / Coordination
Manage required Resources / Means (SVN, accounts, …)
Offer Mgmt. (Specification, Costs and Delivery Due Date)
Product Owner Activities / Support
Process Documentation / Support
Maintain and extend Architecture
Development of:
new functionalities according to customer needs
robustness improvements (improve /stabilize existing functions)
software corrective maintenance (bug fix)
Write Test Procedures (unit tests and integration tests)
Maintain and extend documentation
Reactive Operational Support
L2/L3 Incident Management (Quickest possible Issue resolution, Workarounds)
Root Cause Analysis
Request Mgmt. (apply standard changes / configuration changes / administrative actions)
Data Management (Perform mass data loadings / corrections)
Proactive Operational Support
Monitoring (processes, Interfaces)
Event and Alert Mgmt. (manage events resulting from monitoring service)
Perform daily administrative tasks including fielding user inquiries, user account administration and
identification and resolution of operational issues of applications.
Maintain up to date technical documents (Operation Requirement Sheet, Schedule Requirement Sheet,
Monitoring Requirement Sheet, …)
Prepare and maintain documentation describing configurations and procedures for performing
installations. Maintain the first-time-right approach is must.
Functional Support (Q&A, Product Owner Support, Analysis, data/report extraction)
Perform validation test (functional and data)

Success Metrics

Success will be measured in a variety of areas, including but not limited to

Consistently ensure the on-time delivery and quality (first-time-right) by solving problems, incidents an
requests
Bring innovative cost effective solutions
Achieve the customer satisfaction