S. Jebaraj

Hyderabad, India — MBA candidate

Samuel Jebaraj

Describe. Infer. Decide. Operations work moves in that order — you establish the facts, read what they imply, then act. I spent my early career on the first phase, keeping records and processes clean enough to be trusted. I am now building the quantitative side so I can carry a problem all the way through.

Looking for a banking and finance operations internship — reconciliation, payments, onboarding, controls, reporting.

Get in touch

The three moves

One framework, applied in sequence. Most operational failures happen when a step is skipped.

  1. 1

    Describe

    Get the record right before anything else. Complete, timestamped, reconciled, and legible to the next person who opens it.

    Ledger hygiene, document control, SOPs, audit trails, version discipline.

  2. 2

    Infer

    Ask what the record is telling you. Where does the queue build, which exceptions repeat, what is noise and what is signal.

    Variance analysis, turnaround times, exception patterns, descriptive statistics.

  3. 3

    Decide

    Change the process, not just the number. A decision that no one can execute on Monday morning is not a decision.

    Control design, escalation paths, rework removal, handover documentation.

Experience

2022 — 2024

Full time

Administrative Coordinator

Organisation name — Hyderabad

  • Maintained records and filing systems for a high-volume desk, keeping documentation complete and retrievable for internal review.
  • Coordinated the flow of approvals between departments, tracking each request through intake, verification, sign-off and closure.
  • Reconciled internal registers against source documents and raised exceptions before they reached month-end.
  • Wrote and updated the standard operating notes new joiners used to run the same process without supervision.

2024 — present

Postgraduate study

MBA — Finance

Institution name — Hyderabad

  • Coursework in financial accounting, corporate finance, operations management and business statistics.
  • Case work on banking processes: account onboarding, payment cycles and internal control design.
  • Self-directed build-up of the quantitative toolkit described below.

Projects

Self-directed and coursework builds. Each one exists because a process was slower, or less certain, than it needed to be.

Self-directed — Excel

Daily cash reconciliation workbook

Matches a bank statement extract against a ledger export on date, amount and reference, then splits the result into matched, unmatched and partially matched buckets.

Uses lookup formulas, helper keys for near-matches and conditional formatting so an exception is visible without reading a single row.

Coursework — process mapping

Invoice-to-payment cycle map

A SIPOC and swimlane map of accounts payable from invoice receipt to release, with ownership marked at every handoff.

Surfaced a rework loop where invoices missing a purchase order number returned to the submitter twice before anyone checked the master data.

Self-directed — data hygiene

Vendor master cleanup

De-duplicated a vendor list by normalising names, tax IDs and bank details, then wrote the validation rules that stop duplicates being created again.

The point of the project: bad master data is a control problem long before it is a reporting problem.

Coursework — operations analysis

Loan onboarding turnaround study

Broke application-to-disbursal into stages and measured time spent in each, separating work time from waiting time.

Document verification held the queue; the fix was a front-loaded checklist at intake rather than more capacity downstream.

Concept study

Settlement fails under T+1

A written breakdown of why trades fail to settle — inventory, standing instructions, reference data mismatches — and which control catches each cause.

Built to understand what a settlements desk actually watches during the day.

In progress

Reading the formulas, not just the outputs

A targeted refresher on statistical notation — summation, means, exponents — so a formula in a textbook or a model reads as an instruction rather than a wall of symbols.

Applied immediately to spread, distribution and control limits on operational data.

Concepts explored

Reading and case work outside the syllabus, chosen because operations roles assume you already know the vocabulary.

  • Nostro and vostro reconciliation
  • Maker–checker controls
  • Three lines of defence
  • Straight-through processing
  • KYC and periodic CDD refresh
  • Exception management
  • SLA and turnaround metrics
  • Liquidity coverage ratio
  • Chargeback lifecycle
  • Risk and control self-assessment
  • Root cause analysis
  • Segregation of duties

Toolkit

Excel — pivots, lookups, cleanup
Working
Process mapping and SOP writing
Working
Records and document control
Working
Business statistics
Building
SQL — SELECT, JOIN, GROUP BY
Building
Power BI dashboards
Building

Open to internships

If your operations team needs someone who will keep the record clean and then ask what it means, I would like to talk.

samuel.jebaraj@example.com

LinkedIn

Hyderabad, India — open to relocation