What are the responsibilities and job description for the IT Business Analyst Japanese (942) position at Sharp Decisions?
Location: Jersey City, NJ (Hybrid)
Experience Level: Mid (5–7 years)
Language Requirement: Japanese and English bilingual required
SummaryWe are seeking a bilingual (Japanese/English) consultant to support SMBC ADs Sponsored repo enablement. The consultant is responsible for the analysis, design, and delivery governance required to rationalize downstream data flows following the FOX Upgrade Project. This individual will lead and complete the assessment of existing downstream data flows and legacy RDB dependencies, define the target-state data architecture with Izumi positioned as the enterprise-wide primary data hub, and produce a structured transition roadmap to enable migration from a fragmented data landscape to a unified Golden Source Architecture.
ResponsibilitiesPhase 1 – Discovery: Identify All Systems Referencing FOX- Lead and coordinate stakeholder interviews to identify all systems referencing FOX, including non-RDB consumers.
- Map data flows and dependencies between FOX and downstream systems.
- Document current-state system interaction diagrams and data lineage.
- Prepare a discovery report summarizing findings, risks, and recommended scope and approach.
- Lead cross-functional workshops across business, IT, and architecture teams; capture and document decisions.
Deliverables: Discovery deliverable package with system list and dependency mapping; project governance and monthly status reporting.
Phase 2 – Design Governance: Izumi Ingestion Layer & Snapshot Logic- Lead requirements definition sessions for ingestion logic covering pre-batch and post-batch scenarios.
- Produce functional and non-functional requirements documentation.
- Lead and document solution design reviews with architecture and engineering teams.
- Maintain authoritative design decisions, assumptions, and traceability documentation.
- Govern alignment across data, architecture, and FOX teams.
- Produce stakeholder-approved design and requirements artifacts required by implementation teams.
Deliverables: Requirements and design documentation package approved by stakeholders; project governance and monthly status reporting.
Phase 3 – Validation Oversight: Data Parity Between RDB and Lakehouse Outputs- Define the overall parity validation strategy, approach, and acceptance criteria.
- Lead data comparison reviews and defect triage governance.
- Review and assess test results provided by technical teams; identify gaps and remediation recommendations.
- Document discrepancies, root cause classifications, and resolution recommendations.
- Produce validation summary reports and sign-off documentation.
Deliverables: Data parity testing summary and UAT support documentation; project governance and monthly status reporting.
Phase 4 – Transition Management: Group-Based Migration of Downstream Systems- Define the downstream group migration strategy to minimize business disruption.
- Lead readiness assessments and cutover planning coordination with each system owner.
- Produce migration runbooks, checklists, and communication materials.
- Govern risk assessments, dependency planning, and mitigation strategies.
- Lead go/no-go decision forums and document final migration decisions.
- Produce final transition summary and lessons learned documentation.
Deliverables: Approved transition plan and migration coordination package; project governance and monthly status reporting.