← Bank of America Interview Insights

Bank of America·Software Engineer·Technical Phone Screen·Intermediate

Intermediate
Apr 2026

Summary

Brief technical screen for a software engineer role, focused on a chargeback ingestion system. Not much to report, pretty surface-level stuff.

Questions Asked (1)

Q1

Walk me through how you would design a chargeback ingestion system where final transactions are exported to CSV and sent to a payment network via FTP on a scheduled basis.

System DesignAPI & IntegrationsTechnical Trade-offs
Author's notes

Talked through the pipeline end to end.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then outline the end-to-end flow from ingestion to export. Focus on reliability, data integrity, and security, and discuss trade-offs for each design decision.

Pro tip: Emphasize idempotency and reconciliation to prevent duplicate chargebacks, and mention how you would handle FTP failures with retries and alerting, as these are critical in banking systems.

1. Clarify Requirements

Ask about volume, latency, data sources, and compliance needs. Confirm the schedule, file format, and FTP details.

2. Design Ingestion

Propose a scalable ingestion layer (e.g., message queue, API) to receive chargeback events. Ensure idempotency and validation.

3. Process and Store

Design a processing pipeline to transform and enrich data, then store in a durable database. Include reconciliation and error handling.

4. Export and Transfer

Describe generating CSV files from final transactions and securely transferring via FTP on a schedule. Include retry and monitoring.

5. Address Trade-offs

Discuss trade-offs like batch vs. stream, FTP vs. SFTP, and how to ensure exactly-once delivery.

Key Points to Mention

  • Idempotency and deduplication to handle duplicate chargeback events
  • Data validation and schema enforcement at ingestion
  • Reliable scheduling (e.g., cron, Airflow) with monitoring and alerting
  • Secure FTP (SFTP/FTPS) and encryption of sensitive data
  • Reconciliation and audit trails for compliance
  • Scalability and fault tolerance (e.g., retries, dead-letter queues)

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.