Sr. Systems Middleware Analyst
Location: Bothell WA
Duration: 12+ months
Position Purpose
- The Principal Systems Analyst provides technical system design recommendations to meet business and functional requirements. This position relies on the Business Systems Analyst and, in some cases, on the Architect or Technical Administrator for input into implementation of the technical design.
Primary Duties and Responsibilities
- Collect information to analyze and evaluate existing or developed T-Mobile applications or systems, prepare detailed flow charts and diagrams outlining systems capabilities and processes. Translate business and user requirements into accurate system requirements specification documents through systems and data analysis
- Coordinate and manage project Change Requests. Communicate effectively to keep business, IT and project personnel up to date
- Ability to estimate task and workload to achieve deliverables and goals, delivering on time and on estimation
- Interacts regularly with Business Analysts, Architects, Developers, Application Support and Operations
- Assist in definition, design, and management of Enterprise Architecture components and low-level technical Architecture design documents.
- Utilize departmental Software Development Lifecycle Methodology as a guide for analyst activities.
Secondary Duties and Responsibilities
- Contribute to and work to meet project schedules by providing accurate estimates of effort required for analyst and development deliverables, by providing updates on project progress to team members, project management and project personnel, and by escalating issues that might affect project success to management.
- Maintain technical skills and expertise through continuing education and training.
- Collaborate/Partner with other teams including Enterprise Testing, Release Planning and Management, Development, Project Management, and Application Support on successful delivery of systems enhancements.
- Provide on call and after hours support as required for production releases.
Qualifications
Functional/Technical Skills
- Minimum 5 years of development and analysis experience of medium to large-scale projects
- Minimum 5 years of experience designing and supporting complex multi-tiered applications
- Working knowledge of UML, SQL, JMS, SOAP/WSDL
- 1 -2 years experience with Java and/or C++, XML
- Experience with integration platforms such as Tibco, WebMethods, MQ Series, Vitria, Weblogic Integration Platform a plus
- Must possess strong analytical and problem solving skills
- Excellent communication and documentation skills are required
- Ability to handle multiple concurrent activities and projects
- Must possess solid project management skills and minimum 3 years leading small to medium-sized projects
- Strong working knowledge of SDLC practices and procedures
- Solid knowledge of canonical data models and management/governance of the model.
Experience
- Experience with multiple functional areas including billing and retail a plus
- Experience working with at least 3 business applications/systems
- Experience providing tier 4 production support
- Experience with canonical models and management/governance, service governance, SOA architecture, and preferably with commercial tools like igniteXML
- Application Development background required. This is a technically focused position and generally seen as a progression from a Development role.
- Knowledge of T-Mobile applications and systems a plus
- Knowledge of wireless industry a plus
- Experience mentoring other members of analyst/development staff
Education and Experience
- A bachelor's degree in business, computer science or management information systems or equivalent experience (8 years minimum related experience/training preferred).
Why work for this team?
- This person will be F2F with business partners and outside vendors such as Walmart, Best Buy and Costco. High visisbilty within the organizations. Middleware is the lifeline and arteries of the T-Mobile business.
What does a good Sr. Systems Middleware Analyst look like:
- The most important skill a middleware analyst uses is not technical, it is surely cultural. SOA does require people to think of business and technology differently. Instead of thinking of technology first, middleware analysts must first think in terms of business functions, or services. It is expected that adoption of SOA will change business IT departments, creating service-oriented (instead of technology-oriented) IT organizations. Middleware analysts perform crucial evangelization of this concept.
- The enterprise service bus is a core element of any SOA. ESBs provide the "any to any" connectivity between services within a company, and beyond that company to connect to the company's trading partners. Therefore, middleware analysts need to be skilled in SOA and enterprise service bus concepts first and foremost. Middleware analysts rely on an SOA reference architecture to lay out an SOA environment that meets the company's needs and priorities. The ESB is part of this reference architecture and provides the backbone of an SOA but is not considered an SOA by itself.
Thanks & Regards,
Divya
Sr. Resourcing Specialist
IDC Technologies, Inc.
1851 McCarthy Boulevard, Suite 116, Milpitas, CA - 95035
Phone : 408-868-5125
Fax : 408-608-6088
Email: divya.r@idctechnologies.com
Website: www.idctechnologies.com
You received this message because you are subscribed to the Google Groups "CVMSCRM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cvmscrm+unsubscribe@googlegroups.com.
To post to this group, send email to cvmscrm@googlegroups.com.
Visit this group at https://groups.google.com/group/cvmscrm.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment