> Markdown version of [/jobs/ext/2154469-lead-systems-analyst](https://www.wearedevelopers.com/jobs/ext/2154469-lead-systems-analyst). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Lead Systems Analyst - **Company:** Simon & Schuster, Inc. - **Location:** New York, NY, United States (Remote available) - **Experience:** Expert - **Salary:** $175,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Automation of Tests, CA Workload Automation Ae, COBOL (Programming Language), Computer Programming, Electronic Data Interchange (EDI), Systems Analysis, Software Tools, SQL Databases, Data Processing - **Published:** August 20, 2026 - **Apply:** https://www.juju.com/job/00000000go1fnx ## About the Role + **7+ years of business/systems analysis experience** , including significant experience on large-scale order processing, fulfillment, or supply-chain systems. + **Experience with EDI, order processing, and shipment-confirmation processing for large-scale distribution or publishing operations** - including order intake and acknowledgements, distribution/warehouse orchestration, and invoicing flows. + **Experience using AI tools for discovery and documentation** - e.g., AI-assisted code or system analysis, requirements extraction, or documentation generation - and the judgment to validate AI output against real system behavior. + **Demonstrated ability to work effectively with both business users and engineers** - comfortable eliciting requirements from operations staff in business language and defending those requirements in technical design discussions. + **Proven ability to translate business requirements into coding/solution requirements** - data mappings, rule specifications, and acceptance criteria precise enough for direct implementation and test automation. + Strong analytical writing: able to produce documentation that becomes the authoritative record of system behavior. + The judgment to distinguish a true business rule from a historical implementation accident. Preferred Qualifications + Publishing-industry experience. + Experience on a legacy-modernization, system-replacement, or platform-migration program. + Exposure to legacy or mainframe-style environments (e.g., COBOL-era batch systems) - enough familiarity to work effectively with legacy specialists when documenting system behavior. No programming or code-reading skills required. + Familiarity with SQL - able to read queries and data-reconciliation reports and reason about data-level parity between systems. + Familiarity with batch scheduling environments (AutoSys or similar) and overnight batch operations. + Experience with warehouse management (WMS), 3PL, or drop-ship integration workflows. + Experience coordinating user acceptance testing and production cutover approvals. ## Description The Lead Systems Analyst works directly with business owners across order management, distribution, EDI, and finance operations to document required behavior, validate what is actually used, prioritize what gets modernized first, define acceptance criteria, and coordinate business sign-off for production cutovers., + **Discovery and documentation** - Work with business and technical teams to document required functionality, production usage, business rules, interfaces, reports, and dependencies for each modernization module, using AI-assisted analysis and documentation tooling to accelerate the work. + **Usage validation and retirement analysis** - Determine which legacy programs, jobs, reports, and interfaces are still used and still needed; build the evidence case for retiring what is not; obtain business-owner approval for retirement decisions. + **Requirements translation** - Convert business requirements and legacy behavior into clear, testable solution requirements that engineers can implement directly: data mappings, business-rule specifications, acceptance criteria, and edge-case definitions. + **Prioritization with the business** - Run recurring priority reviews with business stakeholders; translate operational pain (failures, delays, manual workarounds) into modernization sequencing. + **Validation and cutover sign-off** - Review reconciliation and parallel-run results (first-pass data comparison is performed by the QA / Test Automation Engineer) from the business perspective: confirm that differences are explained, that required business behavior is preserved, and that edge cases the business cares about are covered. Coordinate business user testing and provide the business sign-off that gates each production cutover. + **Stakeholder communication** - Serve as the credible, consistent voice between the modernization team and the business users who depend on the system daily: what is changing, when, and why it is safe. ## Related Videos - [Fault Tolerance and Consistency at Scale: Harnessing the Power of Distributed SQL Databases](https://www.wearedevelopers.com/videos/1146-fault-tolerance-and-consistency-at-scale-harnessing-the-power-of-distributed-sql-databases) - [ Secure Code Superstars: Empowering Developers and Surpassing Security Challenges Together](https://www.wearedevelopers.com/videos/422-secure-code-superstars-empowering-developers-and-surpassing-security-challenges-together) - [Implementing continuous delivery in a data processing pipeline](https://www.wearedevelopers.com/videos/73-implementing-continuous-delivery-in-a-data-processing-pipeline) - [The Software Engineer 2030: From Coder To AI Orchestrator? - Patrick Schnell](https://www.wearedevelopers.com/videos/1825-the-software-engineer-2030-from-coder-to-ai-orchestrator-patrick-schnell) - [Fault Tolerance and Consistency at Scale: Harnessing the Power of Distributed SQL Databases](https://www.wearedevelopers.com/videos/1520-fault-tolerance-and-consistency-at-scale-harnessing-the-power-of-distributed-sql-databases) - [Grappling With Clunky Old Software? Start by Understanding What’s Inside!](https://www.wearedevelopers.com/videos/1189-grappling-with-clunky-old-software-start-by-understanding-what-s-inside) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [13 AI Tools You Have to Try](https://www.wearedevelopers.com/magazine/219-13-ai-tools-you-have-to-try) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)