| |
|
Web Yoga, Incorporated
WebMethods Developer
Job Location: Dayton, OH
Shift:
6 Months with extensions
Job Summary:
We are currently looking to augment our existing WebMethods development staff with 1 additional contractor resource.
Because many WebMethods interfaces are already live candidates that can clearly articulate experience supporting mission critical applications and have retail EDI transaction sets (810, 850, 856) experience will stand out. Our business users normally work hand in hand with our WebMethods resources so extremely strong verbal and written communications are required.
We would like to get this resource started as soon as possible.
Client is currently working to implement a very large 3rd party system that will require integration with numerous Client legacy applications.
We are looking for an experienced WebMethods developer to provide support for existing implementation as well as work on new integrations required by the implementation.
All integrations are done in batch. XML will always be either the source or destinations file format so integration experience with batch processing utilizing XML is required. For the non-XML end of the interface we normally either connect to a SQL Server database or get a batch file in a proprietary format.
The requirements for the Web Methods developer are as follows:
- 3 years WebMethods integration design experience
- 3 years WebMethods development experience
- 2 years of WebMethods experience on the most current version(s)
- 2 years experience generating technical design documents
- 2 years XML experience
- Experience mapping EDI documents (purchase order, invoice, advance shipment notice, supplier catalog)
- Strong knowledge of T-SQL
- Excellent verbal communications skills
- Excellent written communications skills
- Strong team player
Skills not required but preferred:
Business analysis experience including working directly with business users in writing business requirements specification documents
The candidate will be expected to:
- Accept responsibility as the lead developer an interface
- Work with the BA and other resources to fully understand the business requirements
- Work with business SME's to understand the impact of the integration on the source and target systems
- Write the technical specifications document for the interface
- Review the tech spec with the BA and other team members to obtain sign-off for the tech spec
- Write a psuedo code document that will detail how the interface will be implemented obtaining sign-off from the lead WebMethods developer
- Work with the BA to develop test cases and test scripts
- Code and unit test the interface
- Work with the BA to system test the interface
- Work with the BA and business users to user acceptance test the interface.
If the interface is small the WebMethods developer will be required to work on more than one interface concurrently and be able to easily shift priorities as needed without impacting productivity
What we're expecting to hear from the candidates in an interview:
- I've written many WebMethods interfaces
- I've connected to many different data sources
- I have significant experience working with XML as either the input or output of an interface
- Explicit descriptions of the interfaces they've implemented that match the types of interfaces they will be expected to build
- I've written at least X number of technical design documents
- I've written design documents on my most recent assignments
- This is the type of information that I include in my technical design documents.....
- I have written pseudo code and performed pseudo code walkthroughs with the development lead prior to coding
- Here is how I typically implement error handling
- I always complete unit testing
- I am always involved in system testing
- I have significant experience performing user acceptance testing.
- I feel very comfortable being the lead developer on integration and can work with minimal guidance from the development lead.
- My written documentation is excellent rarely needing significant modification
- I've implemented integrations between SQL server data and XML
- I've implemented integrations between proprietary file formats and XML
- I've implemented integrations between ANSI EDI documents and XML
Top reasons for disqualifying candidates:
1. Poor verbal communications skills
2. Lack of direct experience building the type of integrations that they will need to build
3. Inability to provide specific examples that directly relates to the type of work to be performed.
4. Answers questions in broad non-specific terms resulting in confusion as to how work experience is actually applicable to role and responsibilities
HOW TO APPLY:
Web Yoga, Incorporated
|
| |
|
|
