Academic snapshot
Marks: 7.0+ CGPA or 70% throughout 10th, 12th, graduation
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active
Year: Final-year and recent grads
Bank of America Placement Papers 2026
Bank of America is one of the world’s largest banks offering consumer, corporate, and investment banking services. India technology centers in Mumbai, Hyderabad, Gurugram, and Chennai support global banking platforms, trading systems, and digital customer products.
HQ: Charlotte, North Carolina, USA
Employees: 217,000+
Revenue: $100+ Billion USD
Website: bankofamerica.com ↗
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Bank of America fresher eligibility for campus drives
Bank of America India tech hiring is selective volume, not mass 60% services. The printed floor is often 7.0 / 70% throughout. Coding still decides who sees an interviewer.
Who this hub is for
- For: Students targeting Software Engineer / Analyst (and nearby data/cloud titles) at India tech centres via campus, virtual campus, or careers.
- Not the same track: US retail-bank teller jobs, pure markets/IB analyst loops, or experienced vice-president hiring. Those bars do not map to this OA → two technicals story.
- M.Tech/MCA: Often listed with B.Tech. If your mailer drops a degree, follow the mailer.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus / virtual campus | Batch OA window, college list | Coding + Java/SQL depth |
| Careers portal | Resume screen volume | Still expect OA + two tech rounds |
| Referral | Visibility | You still sit every elimination round |
Off-campus does not mean easier trees. It often means more applicants and the same 90-minute filter.
Degree, 7.0, and “is 70% enough?”
Is 7.0 CGPA enough? It matches the commonly reported floor. A 7.1 with two passing OA programs beats an 8.9 that cannot join two tables. A 7.8 B.Tech with 68% in 12th is how people get dropped when the JD says throughout.
Branches: CS/IT/ECE dominate. Related streams show up with solid DSA.
Gaps and backlogs: Active backlogs are a usual hard blocker. Short gaps need a skills story. Lying is an integrity fail in a bank.
What helps the resume screen: One project you can defend, any internship, readable Java/SQL on the resume if you claim them. See certifications after DSA, not instead of it.
Skills they actually filter
OA: Aptitude + CS MCQs + 2-3 coding
Interviews: DSA, Core Java, SQL, projects
Languages: C, C++, Java, Python
Hygiene: Banking-tech vocabulary lite
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 7.0+ CGPA or 70% | Mailer wins |
| 10th & 12th | Often same throughout rule | Keep scans |
| Branches | CS, IT, ECE, related | Confirm drive |
| Backlogs | None active | Clear before joining |
| Relocation | Mumbai / Hyderabad / Chennai | HR will ask |
Who usually fits and who struggles
Good fit: You can finish a 90-minute mixed paper, you will relocate to one of the three India tech cities, and you can talk about a project without reading the resume aloud.
Harder path: You only practised puzzles and skipped coding; you claim Java on the resume and cannot explain HashMap; you refuse all three cities; you treat a bank HR round like a casual startup chat.
Integrity: Background checks in banking are not a rumour. Percentages and dates must match. A “rounded” CGPA that does not match the marksheet is how people fail after two technicals.
Bank of America previous year paper PDFs
Download 2026 Bank of America placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What these papers train for the written and SQL rounds
Bank of America does not publish one permanent official paper set. Papers on this site are pattern trainers for the OA and early technicals.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed 90 min: aptitude/DI, CS MCQs, 2-3 coding |
| Technical 1 | DSA + Core Java + SQL + project |
| Technical 2 | Deeper tech, follow-ups, sometimes design lite |
| HR | Why Bank of America, city, integrity |
Themes that keep repeating (2024-2026)
- 2024 cycles: Mixed OA with more coding weight than older aptitude-only stories. Arrays, strings, DP. DI charts in aptitude. DBMS/OS MCQs.
- 2025 virtual campus (GFG, Oct-Nov): One virtual assessment, then 46 students shortlisted for interviews on 28 Nov 2025. Two technicals on DSA, Core Java, SQL, project depth. L2 scheduled within about 10 minutes of clearing L1.
- 2026 prep expectation: Keep aptitude speed and two complete coding submits. Keep Java/SQL warm even if your OA language is Python. Treat PDFs as pattern catalogs.
How to use one paper set in a single sitting
- Timed: full ~90-minute mock in your OA language.
- Untimed: rewrite the cleaner coding solution; list three MCQ types you slow on.
- Map coding misses to themes and pull cousins from coding questions.
- Speak a 60-second project story and a 20-second “Why Bank of America / why this city.”
- Write three SQL joins from memory.
Related problems to practice
| Theme you saw | Drill next | Why it shows up |
|---|---|---|
| Arrays / strings | Two pointers, hashing | OA coding |
| Trees / DP | Traversals, knapsack lite | OA + L1 |
| DI / percentages | Timed charts | Aptitude block |
| Java collections | HashMap vs TreeMap | L1/L2 |
| SQL joins | Group by, nulls | Same interviews |
Bank of America placement process, round by round
Bank of America hires freshers through campus cells, virtual campus drives, the careers portal, and referrals. After eligibility, the shape is bank-tech: mixed OA, two technicals, HR.
Application methods
Campus recruitment
Partner colleges and virtual campus batches. PPT, then OA and interviews on a shared timeline.
Online applications
Apply on bankofamerica.com careers for early-career tech roles. Follow the invite for platform and duration.
Referrals
Improve screen odds. You still need passing OA code and clear Java/SQL talk.
1. Resume / eligibility screen
7.0 / 70% throughout when printed, listed degrees, no active backlogs. Gate.
2. Online Assessment (~90 min)
Candidate reports commonly describe a ~90-minute HackerRank-style test.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude & reasoning | 15-20 | ~30 min | Quant, logic, DI |
| Technical MCQs | 10-15 | ~25 min | Programming, DS, DBMS, OS |
| Coding | 2-3 | ~35 min | Arrays, strings, lists, trees, DP |
Pass habit: bank easy DI and quant, do not marry one seating puzzle, leave time for two complete coding submits. Partial marking appears in some notes; a fully passing easy problem still beats a clever half-write. Student rumours put OA pass around 30-40%. Your invite wins on negative marking and section locks.
3. Technical 1 (~60 min)
DSA, Core Java, SQL, project. Virtual or onsite. 2025 virtual notes: this round can be followed by L2 in about 10 minutes. Stay logged in. Keep water. Do not celebrate in a group chat yet.
4. Technical 2 (~60 min)
Deeper follow-ups, more code, more project “what would you change.” Sometimes design lite for a payments or batch job. Fresher depth: correctness, indexes, failure modes.
5. HR (~30 min)
Why Bank of America, city (Mumbai / Hyderabad / Chennai), family/education, joining vs finals, integrity. Know the ₹12-20 LPA reported band so you do not invent a 40 LPA ask.
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | Virtual campus may pack interviews on one date |
| OA → shortlist | A few days | 2025 note: 46 shortlisted after one assessment |
| Technicals | Same day or 3-5 days | L2 can be immediate |
| HR | 1-2 days | Sometimes same loop |
| Offer | 2-3 days common | Written letter wins |
| End to end | ~2-3 weeks campus often | Off-campus can stretch |
Aptitude skip rules
- Percentages, ratio, DI: do first.
- One chart: read the question, then two cells, not the whole legend.
- Puzzle: 45 seconds then skip.
- Technical MCQs: eliminate two options.
- Coding: read all prompts; finish the easiest fully.
Weekend mock that matches a real drive
Saturday 10:00: 90-minute mixed OA.
Saturday 12:00: error log.
Saturday 16:00: Java collections + three SQL queries on paper.
Sunday 11:00: 45-minute mock L1 (one DSA + project).
Sunday 12:00: 15-minute mock L2 follow-up without a break.
Sunday 12:30: HR city + why-bank answers.
Two weekends of that beat twelve nights of random “fintech” YouTube.
Banking vocabulary lite (30 minutes total, not a semester)
Know: what a payment is vs a ledger entry, why batch jobs exist, why downtime at 2 a.m. still matters, what “PII” means, why you do not joke about leaking customer data. That is enough for most fresher HR. If L2 asks you to design “UPI,” stay at actors, APIs, idempotency, and failure. Do not invent a clearing-house from a blog.
Documents pack
10th, 12th, all semesters, ID, resume one page. Throughout 70% means the 12th PDF matters. Banking background checks are not optional flavour text.
Documents pack
10th, 12th, all semesters, ID, resume one page. Throughout 70% means the 12th PDF matters. Name, percentages, and dates must match the campus form and any later BGV portal. A mismatch is a silly way to stall after two technicals.
How interviews get scheduled
Campus: PPT → OA window → shortlist mail → interview date (sometimes one packed virtual day). Off-campus: recruiter mail with HackerRank link, then a loop on Teams or similar. Always screenshot the invite for duration and language list. Blogs on this page lose to that screenshot.
Bank of America practice pages
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
A practical Bank of America prep plan
If a Bank of America invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Bank of America sits around ₹12-20 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Candidate-reported campus floor is often 7.0+ CGPA or 70% throughout 10th, 12th, and graduation; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; final-year or recent grads; no active backlogs. Coding, aptitude, and communication still decide shortlists. Verify the drive notice or careers posting.
What you are training for: Typical India tech fresher loop: Online Assessment (~90 min, aptitude + technical MCQs + 2-3 coding) → Technical 1 (~60 min, DSA/Java/SQL/projects) → Technical 2 (~60 min, deeper tech) → HR (~30 min). Campus batches often finish in about 2-3 weeks. Some virtual drives move L2 within minutes of L1.
Short version of the prep split: Split time roughly 35% DSA/coding, 25% aptitude and DI, 20% Java/SQL/CS fundamentals, 10% banking vocabulary lite, 10% behavioral. Clear the 90-minute OA first. Languages: C, C++, Java, Python. Full plan: /bank-of-america/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Bank of America previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Bank of America drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Bank of America usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Bank of America?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Bank of America-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Bank of America story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Bank of America PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Bank of America papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Bank of America papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Bank of America-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Bank of America paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Bank of America. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to practise this month for Bank of America
Week calendars live on the preparation guide. This H2 is the focus split.
Time split
| Bucket | Share | What “done” looks like |
|---|---|---|
| DSA / OA coding | ~35% | Two complete submits per 90-minute mock |
| Aptitude + DI | ~25% | Timed charts without panic |
| Java + SQL + CS | ~20% | Collections, joins, OOP one-liners |
| Banking vocab lite | ~10% | Ten talking points, not a degree |
| Behavioral + city | ~10% | Why bank, why Mumbai/Hyd/Chennai |
If you already clear aptitude and fail coding, invert 35/25 for two weeks. If you code in Python and freeze on Java in L1, add 30 minutes of collections daily without quitting DSA.
This week
- One full timed mock from online assessment plus aptitude questions.
- Two medium coding problems submitted end-to-end.
- Five SQL queries and one HashMap vs HashSet explanation aloud.
- Record “Why Bank of America” once. Cut fillers.
- Error log: DI miss vs coding miss vs Java blank.
What not to waste time on
- Replacing DSA with CFA/FRM playlists
- Starting Kotlin the week of the drive
- Assuming Bengaluru is the default India hub
- Checking out after L1 on a virtual campus day
- Quoting Goldman CTC in Bank of America HR
Two-week focus if the drive is soon
Week A: three full 90-minute OAs; error log of DI vs coding; one tree and one DP every other day.
Week B: Java collections + SQL every morning (20 minutes); one mock L1; one mock L2 with no break; city + why-bank recorded twice.
If you have a month, keep the same split and add one payments-lite design sketch (actors, idempotent transfer, failure). Do not replace DSA with that sketch.
City answer that does not sound fake
Pick a real constraint: family, rent, language, already living there. “I am flexible to all three” is acceptable if you mean it. “I will only do Bengaluru” is how people waste a loop. If you cannot move, say so in HR and take the other offer. That is cleaner than a day-one no-show.
Project deep-dive that survives L2
Interviewers in the 2025 note wanted project depth, not a tech-name list. Prepare:
- One sentence problem
- Your module (not “we used React”)
- One bug and how you found it
- One metric (latency, error rate, users, time saved)
- One thing you would rebuild
If the project was a college portal, that is fine. Fake-fintech with no code is not. If they ask “how would this look inside a bank,” map to access control, audit logs, and not leaking PII. That is banking-tech hygiene, not a CFA.
Aptitude DI without a CAT course
Bank OAs still throw a chart. You do not need 99 percentile.
- Read the question first.
- Find two cells.
- Compute once.
- If it needs three more lookups, skip and return if time remains.
Log every mock: “DI ate 8 minutes for 1 mark.” That sentence is the prep plan. People who “will do DI at the end” never do.
What a 46-person shortlist means
The 2025 virtual note is useful because it is a number, not a vibe. One assessment, 46 interview seats, then stacked technicals. You cannot control the 46. You can control two passing programs, Java/SQL warmth, and not dropping the call between L1 and L2. That is the whole game on a virtual campus day.
Night-before checklist
- Charger, ID, resume PDF, 10th/12th scans
- Java collections + three SQL queries reviewed once
- City yes/no written in one sentence
- 60-second intro recorded once more
- Sleep. Virtual L2 ten minutes after L1 is not the time to be foggy
What mass-plus-select means
Bank of America is not Hexaware volume and not Goldman quant. A 46-person interview list after one OA is still a filter. You do not need a perfect contest rating. You need two passing programs, a project you can defend, and a city you will actually join. Students who treat it as “just a bank aptitude test” are the ones who leave coding empty. Students who treat it as FAANG system design over-prepare the wrong hour.
Bank of America fresher CTC in India (2026)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location, and written components.
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer / Analyst (fresher) | ₹12-20 LPA | Primary band for this hub |
| Later / senior engineer (indicative) | Higher range | Not the campus default |
Confirm base, bonus, and benefits on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Health insurance, PF/gratuity on the usual India pattern, learning budgets (manager-dependent), and relocation when the letter names Mumbai, Hyderabad, or Chennai. Hybrid language varies by team. Ask HR.
How to talk CTC in HR
Know the ₹12-20 LPA context. Ask how the package splits. One calm question beats aggressive negotiation with no anchor.
Offer-stage discipline
- Read city and joining date
- 10th/12th/degree % must match
- Verbal “selected” is not an offer PDF
- Background check forms are part of the job
What’s changed in Bank of America hiring lately
- India tech centres (Mumbai, Hyderabad, Chennai) remain the fresher story.
- Virtual campus formats continue alongside in-person loops; 2025 notes show same-day stacked technicals.
- Java + SQL still show up even when the OA allowed Python.
- ₹12-20 LPA remains the commonly cited fresher band, not a promise for every college.
- Banking-tech hygiene (reliability, PII, batch jobs) shows up more than “build a crypto exchange” prompts.
Net for 2026: do not treat Bank of America as a pure aptitude bank exam or as Goldman-quant. Double down on timed coding, Java/SQL, and a city answer.
If Wells Fargo or Capital One also visit your campus the same month, reuse the 90-minute mixed OA and the Java/SQL oral. Change only the city list and the “why this bank” sentence. That is the efficient way to sit three bank-tech loops without three prep personalities. Do not build a fourth language for the third bank.
Bank of America placement FAQs
Papers & process
Can I download Bank of America placement papers PDF for free?
Yes. Free 2024-2026 style practice is on this site. Start with the 2026 PDF or the archive.
What is the Bank of America placement process for freshers?
Typical path: OA (~90 min) → Technical 1 (~60 min) → Technical 2 (~60 min) → HR (~30 min). About 2-3 weeks on many campus batches.
How many interview rounds does Bank of America usually have?
Most fresher tech loops report four stages. Some virtual drives stack L1 and L2 on the same day. Count the mailer.
What does the Online Assessment look like?
Often ~90 minutes: aptitude/DI, technical MCQs, 2-3 coding problems on HackerRank-style platforms. Details: online assessment.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly 7.0+ CGPA or 70% throughout; CS/IT/ECE-related degrees; no active backlogs. Your notice overrides this page.
What is Bank of America fresher salary in India?
Candidate-reported SWE/Analyst CTC often ₹12-20 LPA (as of August 2026). The written offer is the only number that matters.
Where does Bank of America hire freshers in India?
Mumbai, Hyderabad, and Chennai are the centres students report. Relocate answers belong in HR, not after the letter.
Prep & bank-specific
How should I prepare?
Roughly 35% DSA, 25% aptitude/DI, 20% Java/SQL, 10% banking vocab lite, 10% behavioral. Guide: preparation guide.
Which programming languages are allowed?
C, C++, Java, Python on most OAs. Interviews often still poke Java and SQL. Confirm the invite.
Do I need banking domain knowledge?
Not as a syllabus. Ten talking points help. DSA and SQL still decide technicals.
Bank of America vs Goldman Sachs vs JP Morgan?
Share DSA prep. Bank of America is India banking-tech with a commonly cited ₹12-20 LPA band and three named cities. Goldman/JPM can be tighter or more markets-adjacent. Compare letters, not brand prestige alone.
Any pro tip that actually changes outcomes?
Two complete OA submits. Java + SQL warm. City answer ready. Do not check out after L1 if L2 can start in ten minutes.
Where can I read real interview experiences?
Bank of America interview experience plus the 2025 virtual campus GFG note linked in the stories section.
Bank of America vs Wells Fargo vs Capital One?
All three hire India tech. Compare city, CTC letter, and how heavy Java/SQL felt in recent write-ups. Prep the same OA muscles; customise HR.
Real Bank of America interview notes from candidates
Virtual campus drive 2025 (GFG)
After one virtual assessment, “46 students were shortlisted for the interview rounds scheduled on Nov 28, 2025,” then two technical interviews focused on DSA, Core Java, SQL, and project depth, with L2 about 10 minutes after L1. Source: GeeksforGeeks virtual campus 2025.
Takeaway: keep Java and SQL warm even if OA was Python. Stay in the chair between rounds. Do not treat L1 as the finish line.
Composite notes students repeated
What helped: two passing OA programs; joins written from memory; a project metric; a clear city preference; calm integrity answers.
What hurt: coding before constraints; “I will do only ML”; refusing all three India hubs; quoting product-company CTC; disappearing after L1.
After you clear OA
- Re-solve every miss cold.
- Speak two STAR stories and one “why this bank” without notes.
- Warm one tree/DP medium in your interview language and one Java collections question.
- Write three SQL queries on paper.
- Sleep and city logistics. Do not open a new advanced topic.
Virtual campus day logistics (from the 2025 note)
If interviews are stacked on one date, treat it like an exam, not a casual Zoom:
- Laptop charged, hotspot ready, ID and resume PDF on the desktop
- Java collections and three SQL queries on a paper cheat-sheet for your eyes only before the call, then put it away
- Water, bathroom, notifications off
- After L1, stay in the meeting lobby or the email thread. Ten minutes is not enough to “take a walk and reset” if L2 is already booked
- Do not text friends “I crushed L1” between rounds. Save it for the offer PDF
Java / SQL oral that keeps coming back
Java: HashMap vs HashSet, equals/hashCode, ArrayList vs LinkedList, checked vs unchecked, what final does not do. Say one real bug you hit.
SQL: inner vs left join with a null example, GROUP BY with a non-aggregated column (and why the engine complains), a slow query you would index. Draw two tiny tables on paper if the interviewer lets you.
If your OA language was Python, still run this oral. The 2025 write-up did not care that you were “a Python person.”
Integrity and banking hygiene
Do not joke about scraping customer data for a side project. Do not claim a CGPA you cannot print. Background checks in a bank are slower and meaner than a services BGV rumour. If you have a gap, say the skills story once, then stop.
More narratives: Bank of America interview experience.
Similar companies
Goldman Sachs · JP Morgan · Wells Fargo · Capital One · Deutsche Bank · Morgan Stanley