DUTIES AND RESPONSIBILITES:
• Responsible for elicitation, analysis, and documentation of business requirements.
• Research and exploration of user requirements, costs, and benefits in support of documentation required for the demand management process.
• Responsible for analyzing the business needs to identify new processes and process improvements that will meet those needs.
• Documents current business processes and models to define requirements and/or gaps.
• Analyze detailed system factors including input/output requirements, information and paper flow, hardware, and software needs.
• Analyze “soft" system factors including roles, responsibilities, policy, culture, etc.
• Evaluate the impact of potential software and process changes on the organization.
• Develop and facilitate groups as necessary in pursuit of eliciting and defining requirements.
• Assist in the creation of the business case documentation.
• Understanding of architectural consistency and usability standards.
• Defines and develops user test cases and validates test results during testing.
• Executes unit and functional test cases.
• May conduct system demonstrations and training sessions, as well as participate in design/review of training content.
• Plays a third level support role by helping to troubleshoot and resolve issues with production systems.
• Participates in associate meetings and communicates any concerns to management.
QUALIFICATIONS AND REQUIREMENTS:
• Bachelor’s degree in computer science, Information Systems, Business, or another related field or equivalent work experience.
• Proven experience leading data migration requirements from legacy systems into a new ERP (Sage X3) environment
• Strong hands-on expertise in requirements elicitation, documentation, and management, with emphasis on data mapping, transformation rules, and validation
• Deep understanding of data structures, data quality, and migration best practices, with the ability to identify gaps and risks early
• Self-driven and accountable professional with strong stakeholder management and communication skills, able to drive outcomes with minimal oversight
• Working knowledge of Confluence and JIRA.
• Experience in any of the following business areas is desired: Sales operations, order entry, accounting, finance, procurement, warehouse operations, order management, and order fulfillment.
• Minimum of 3-5 years’ business analysis or systems analysis experience is preferred.
• Bonus: Sage X3 experience (ERP).
Associate is expected to operate at a proficient level across the following areas of technical knowledge and skill:
• Ability to organize and prioritize work.
• Detail oriented, proactive, creative, and efficient
• Intermediate level abilities in Excel, Outlook, PowerPoint, Visio, and Word
• Familiarity with application integration methods to include understanding of data mapping process.
• Ability to effectively work both independently and collaboratively in a team environment
• Ability to work on simultaneous and complex projects, with domain expertise in at least one business area.
• Expertise in ERP solution selection and implementation is a plus
• Ability to communicate effectively to both technical and non-technical audiences in written and non-written format
• Ability to work with all levels of associates
• Ability to work with minimal supervision in a very dynamic environment
• Ability to learn new systems and tools
• Knowledge of software development life cycle methodologies, processes, and procedures.
• Active listener
• Effective in a variety of formal/informal presentation settings: one-on-one, small, and large groups.
Job Title: Mainframe Developer
Location: REMOTE
Duration: 6 Months
W2 Only
About the role
We are adding new composite reservoir accounts to our existing mainframe accounting platform: a pooled account structure in which balances from multiple subsidiary accounts are concentrated into, and drawn back from, a single reservoir account under defined sweep and allocation rules.
This is additional function inside a legacy system. You will be reading a large body of COBOL that has been in production for an extended period, much of it lightly documented, and extending it so that the new account type posts, settles, accrues, reports, and reconciles exactly as the existing types do. Correctness and traceability of every cent matter more than speed of delivery.
What you will do
- Analyze the current account master, posting, and balance-maintenance programs to establish where composite reservoir accounts must be recognized, and document what you find.
- Design and code the new account type end to end: master file and table structures, account opening and closing, participant linkage, sweep and reverse-sweep logic, allocation and interest apportionment, and closing balance derivation.
- Modify batch COBOL programs and JCL and extend the nightly and month-end cycles to include the new processing without lengthening the batch window beyond agreed limits.
- Add new CRAs to the audit trail, exception reporting, and reconciliation controls the new function requires, working with accounting stakeholders on what must be evidenced.
- Produce test data, unit and regression test packs, and parallel-run comparisons against current production output; investigate every difference until it is explained.
- Support implementation, conversion of any in-scope existing accounts, and early-life production runs, including on-call cover during the first cycles.
- Leave behind program documentation, data-flow notes, and runbook updates that the support team can work from.
Required Skills
- 5+ years of Enterprise COBOL development experience in a z/OS environment
- 5+ Years of Experience with NaturalOne
- 3+ years of JCL development and production support experience
- 3+ years of experience with financial/accounting systems development or support including double-entry posting, balance/accrual maintenance, value dating, reconciliation, and month-end closeouts in a regulated environment
- 3+ years of experience working with Adabas and VSAM
- 3+ years of experience with tracing undocumented logic through copybooks, call chains, and job streams
These are the skills we expect to see evidence of in the first conversation.
- COBOL — substantial production experience in Enterprise COBOL on z/OS, both batch and online; comfortable extending large existing programs and reading code you did not write.
- NaturalOne — the Eclipse-based Software AG development environment; developing, debugging, and deploying Natural applications from it, including local development and remote z/OS projects.
- Natural and Adabas — Natural programs, subprograms, and maps; DDMs, descriptors and superdescriptors, and Adabas file design and performance behavior.
- z/OS and JCL — writing and debugging JCL, procs, GDGs, utilities, SORT, and restart/rerun handling; fluent in TSO/ISPF.
- Mainframe data stores — VSAM file design and access, and Adabas for z/OS.
- Financial accounting logic — double-entry posting, balance and accrual maintenance, value dating, reconciliation, and month-end close in a regulated environment.
- Analysis of legacy systems — tracing undocumented logic through copybooks, call chains, and job streams, and stating clearly what a change will and will not affect.
Preferred Skills
- Experience with cash management, account pooling, sweeps, or treasury applications
- Experience with CA-7 scheduling and batch operations
- Experience with REXX, Python, or Java
Not required to apply. Each of these will shorten your ramp-up, and we will support you in learning the ones you do not have.
- Mixed-estate integration — calling between COBOL and Natural, and exposing mainframe function through z/OS Connect, IBM MQ, or REST services.
- Scheduling and operations — CA-7 batch window analysis and performance tuning.
- Scripting and adjacent languages — REXX or CLIST for tooling, plus Java or Python for data comparison and migration work.
- Cash management domain — notional and physical pooling, cash concentration, sweeps, and intercompany allocation.
Additional Skills
- Track record of taking a specification from analysis through production implementation with limited supervision.
- Clear written communication: you can explain a change to an auditor, a business analyst, and another developer, and adjust the explanation for each.
- Degree in computer science or a related field, or equivalent practical experience.
