As a Software Engineer at Maybank Singapore, you are at the intersection of traditional financial stability and rapid digital transformation. This role is pivotal in maintaining and evolving the digital ecosystem that serves millions of customers across the region. You will contribute to high-impact projects, ranging from core banking system enhancements to the development of cutting-edge fintech applications that define the future of digital banking. The work is characterized by its scale, complexity, and the critical nature of the banking environment. You will be expected to balance performance, security, and user experience while navigating the regulatory requirements inherent to the financial sector. This position offers the unique challenge of modernizing legacy infrastructure while simultaneously building innovative, cloud-native solutions that maintain Maybank Singapore’s competitive edge in the market. ##### Tip The banking industry is high-pressure. Candidates who demonstrate resilience, a proactive mindset, and the ability to work under strict deadlines are highly valued by hiring managers.
Application Review
reportedInitial review of submitted applications to assess qualifications and fit.
What to demonstrate
- Initial review of submitted applications to assess qualifications and fit
- Depth in Java
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Assessment
reportedCandidates may complete take-home assignments or participate in live coding sessions.
What to demonstrate
- Candidates may complete take-home assignments or participate in live coding sessions
- Depth in Java
How to prepare
- Answer aloud and timed: What are the primary differences between RESTful APIs and other communication protocols?
- Answer aloud and timed: Describe a time you had to debug a complex issue in a production environment.
Interviews with Hiring Managers
reportedMultiple rounds of interviews with hiring managers to evaluate technical and problem-solving skills.
What to demonstrate
- Multiple rounds of interviews with hiring managers to evaluate technical and problem-solving skills
- Depth in Java
How to prepare
- Prepare two projects you led end to end, each with the decision you owned and what it cost.
- Have three questions about the team's roadmap and how success is measured in the first six months.
Interviews with Heads of Department
reportedOccasional interviews with Heads of Department to assess cultural fit and alignment with organizational values.
What to demonstrate
- Occasional interviews with Heads of Department to assess cultural fit and alignment with organizational values
- Depth in Java
How to prepare
- Answer aloud and timed: Can you explain your approach to ensuring system availability and fault tolerance?
- Answer aloud and timed: How do you handle data consistency in a distributed microservices architecture?
Final Assessment
reportedFinal evaluations to determine the candidate's overall suitability for the role.
What to demonstrate
- Final evaluations to determine the candidate's overall suitability for the role
- Depth in Java
How to prepare
- Answer aloud and timed: What security considerations are paramount when designing a public-facing financial application?
- Answer aloud and timed: Describe a scenario where you had to choose between two different architectural patterns and justify your decision.
2 candidate reports. Individual accounts describe a particular role and hiring cycle.
Maybank Singapore Software Engineer interview experience: restructuring delay
The process began with a lack of clarity that never got resolved. I never received a proper job description. Although I was scheduled for a senior software engineer track, the interviews felt pitched more at a lead level. I completed two technical rounds, and an HR round was confirmed. Then the process was abruptly put on hold because of internal management restructuring. Long gaps stretched to a…
Read full experienceMaybank Singapore Software Engineer interview with a Git technical assessment
I started with a technical assessment that required me to build something small and upload the result to Git. After it was reviewed, I was invited to a career discussion, where I connected my previous work to the role they were hiring for. The timeline became strange after I passed the first round. I waited about three months before the next round and had to follow up with the recruiter repeatedl…
Read full experiencePracHub editorial advice for the preparation topics above.
Be prepared for the long haul
Given that the process can be lengthy, maintain your motivation and treat every stage as a learning opportunity.
Clarify the requirements
If an assignment or question seems vague, do not hesitate to ask for clarification. It shows you value precision.
Focus on communication
Even if you know the technical answer, explain your thought process clearly. The interviewer wants to know how you think, not just what you know.
Practice your "story
Be ready to discuss your resume in detail, highlighting specific achievements and the challenges you overcame in previous roles.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Identify the heaviest tenants in a five-minute window under memory pressure
The edge service handles about 3,000 requests per second across roughly 50,000 tenants, peaking near 9,000. Expose the 50 heaviest tenants by request count over the trailing five minutes so limits can be tightened before one tenant's backfill starves the fleet. You may not retain five minutes of raw records. Give the exact solution and its memory, then the bounded-memory approximation with its error stated as a formula, and say which you would ship and at what tenant cardinality that choice changes.
Approach
- Do the exact version first, because it is affordable at this cardinality: a ring of 300 one-second counters per tenant, advanced lazily, is 1,200 bytes of counters per tenant and roughly 60 to 90 MB for 50,000 tenants with overhead. Carry a running total and subtract the bucket you overwrite so a window read is O(1) rather than 300 adds.
- Extract the top 50 with a size-k min-heap over the tenant sums: O(d log k) for d tenants, against O(d log d) to sort them all. Maintaining the heap continuously instead of on query requires a tenant-to-heap-index map, because incrementing a count already inside the heap means sifting from a known position, and without that map you rebuild the heap on every request.
- State the approximation precisely rather than gesturing at sketches. Misra-Gries with m counters retains every item whose true count exceeds N/(m+1), and each retained count underestimates the truth by at most N/(m+1). With m = 1,000 and N = 900,000 requests in the window the error is roughly 900 requests, which is fine for spotting a tenant sending 50,000 and useless for ranking two tenants 200 apart.
- Say what breaks when the window slides: Misra-Gries and Space-Saving are insert-only and cannot be decremented as records age out. The workable construction is one summary per sub-window, say ten seconds, with 30 summaries merged at query time, and the merged error is the sum of the per-summary errors, so the bound degrades linearly in the number of sub-windows.
Follow-up
- The heaviest tenant is heavy because of one export job rather than user traffic. Should the limiter treat those as the same tenant?
- Two tenants sit tied at the boundary of the top 50. Does your answer flap, and does the flapping matter?
Merge partitioned event streams into one ordered feed with bounded lateness
The read-model service consumes 64 log partitions carrying about 4,000 events per second in total. Each partition is ordered within itself, but partitions drift by up to 30 seconds, and the activity feed must present a tenant's events in occurred_at order. Produce the merge. State its complexity, the buffer it requires in events and in bytes, what happens when one partition is idle, and what you do with an event that arrives after you have already emitted its position. Payloads average 1 KB.
Approach
- Merge with a min-heap over the 64 partition heads keyed on (occurred_at, event_id): O(log P) per event and O(n log P) overall. The tie-break on event_id is what makes the output deterministic when two partitions carry the same millisecond, which matters because the feed is paginated and a non-deterministic order reorders pages under the reader.
- Emitting the heap head is only correct once every partition has produced everything up to that timestamp, so the emit condition is a watermark: the minimum across partitions of the highest occurred_at seen, less the allowed lateness. Events are held until the watermark passes them, which is what turns individually ordered streams into a jointly ordered one.
- Size the buffer from the lateness rather than guessing: 4,000 events per second times 30 seconds is 120,000 buffered events, and at 1 KB each about 120 MB of heap. That number is the real price of the ordering guarantee and belongs in front of whoever asked for it.
- Handle the idle partition explicitly, because it fails the feed rather than corrupting it: a partition with no traffic never advances its own maximum, so the watermark freezes and output stops entirely. Either every partition emits a periodic idle marker carrying the broker's current time, or the watermark falls back to wall clock for a partition silent beyond a threshold.
Follow-up
- The lateness budget is raised to five minutes. What is the new buffer, and what besides memory changes?
- The consumer restarts. Where does it resume from, and what does the feed look like for the first 30 seconds?
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
Why do you want to join Maybank Singapore specifically, and how do you see yourself contributing to our missio
Why do you want to join Maybank Singapore specifically, and how do you see yourself contributing to our mission?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
How do you approach optimizing database queries in a high-volume transaction environment?
How do you approach optimizing database queries in a high-volume transaction environment?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What are the primary differences between RESTful APIs and other communication protocols?
What are the primary differences between RESTful APIs and other communication protocols?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How familiar are you with modern frontend technologies like React or Redux?
How familiar are you with modern frontend technologies like React or Redux?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you design a simple banking application system from scratch?
How would you design a simple banking application system from scratch?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Can you explain your approach to ensuring system availability and fault tolerance?
Can you explain your approach to ensuring system availability and fault tolerance?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you handle data consistency in a distributed microservices architecture?
How do you handle data consistency in a distributed microservices architecture?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
What security considerations are paramount when designing a public-facing financial application?
What security considerations are paramount when designing a public-facing financial application?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Describe a scenario where you had to choose between two different architectural patterns and justify your deci
Describe a scenario where you had to choose between two different architectural patterns and justify your decision.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Every query on one table stalls for forty seconds mid-deploy
During a release on PostgreSQL, every query touching resource times out for about 40 seconds and then recovers with no intervention. The release ran one migration, ALTER TABLE resource ADD COLUMN archived_reason TEXT, and the migration log shows it completing in 6 ms. Unrelated tables showed no change in error rate. Explain how a 6 ms statement caused a 40-second stall, give the ordered checks you would run on a live system to confirm it, and give the migration procedure that prevents a repeat.
Approach
- Separate the statement's duration from the lock's duration. ADD COLUMN with no default is a catalogue-only change and genuinely runs in milliseconds, but it requires ACCESS EXCLUSIVE, and it cannot acquire that until every transaction already touching the table has finished.
- Account for the queueing, which is the part that surprises people. A lock request that is waiting blocks later requests for conflicting modes behind it rather than letting them overtake, so one long-open transaction holds the DDL and the DDL holds all the traffic. The stall length is set by the longest open transaction, not by the size of the change.
- Confirm on a live system in this order: pg_stat_activity for that table ordered by xact_start, looking for the oldest transaction and specifically for state = idle in transaction; then pg_locks where granted = false to find the waiter; then join them on pid to name blocker and blocked. pg_blocking_pids() does that join for you and is the fastest single call.
- Prevent rather than merely time it better. Set lock_timeout to a second or two on the migration session so the DDL abandons the queue after a bounded wait and is retried, instead of holding it for as long as the oldest transaction lives. Be exact about what that buys: queries arriving during the wait still queue behind the pending ACCESS EXCLUSIVE request, so each attempt costs them up to one lock_timeout of added latency. The outage goes from 40 seconds to about one second per attempt, not to zero. Also run migrations away from deploy-time peaks, and put a statement timeout and an idle-in-transaction timeout on the analytics role that opens the long transactions.
Follow-up
- The same release also wants NOT NULL on that column. What is the sequence that gets there without a long lock?
- Your lock_timeout retry fails ten times in a row because the analytics transaction is always open. What do you change?
Built from the rounds and topics Maybank Singapore candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Maybank Singapore loop
- Write out the reported sequence: Application Review, Technical Assessment, Interviews with Hiring Managers, Interviews with Heads of Department, Final Assessment.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 5 reported rounds, with the weakest marked.
02Work Java
- Spend the session on Java, which Maybank Singapore candidates report being tested on.
- Write one worked example in Java and time yourself on it.
Deliverable: One timed worked example in Java.
03Work System Design
- Spend the session on System Design, which Maybank Singapore candidates report being tested on.
- Write one worked example in System Design and time yourself on it.
Deliverable: One timed worked example in System Design.
04Work Object-Oriented Programming (OOP)
- Spend the session on Object-Oriented Programming (OOP), which Maybank Singapore candidates report being tested on.
- Write one worked example in Object-Oriented Programming (OOP) and time yourself on it.
Deliverable: One timed worked example in Object-Oriented Programming (OOP).
05Answer out loud: Technical Proficiency and Domain Knowledge
- Answer aloud, timed: Can you walk us through your experience with Java and the Spring framework?
- Answer aloud, timed: How do you approach optimizing database queries in a high-volume transaction environment?
Deliverable: Spoken answers to 2 reported Technical Proficiency and Domain Knowledge question(s), under time.
06Answer out loud: System Design and Architecture
- Answer aloud, timed: How would you design a simple banking application system from scratch?
- Answer aloud, timed: Can you explain your approach to ensuring system availability and fault tolerance?
Deliverable: Spoken answers to 2 reported System Design and Architecture question(s), under time.
07Answer out loud: Behavioral and Cultural Alignment
- Answer aloud, timed: Tell us about a time you had to explain a complex technical concept to a non-technical stakeholder.
- Answer aloud, timed: How do you handle disagreements with team members regarding technical direction?
Deliverable: Spoken answers to 2 reported Behavioral and Cultural Alignment question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Can you walk us through your experience with Java and the Spring framework?
Can you walk us through your experience with Java and the Spring framework?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a time you had to debug a complex issue in a production environment.
Describe a time you had to debug a complex issue in a production environment.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell us about a time you had to explain a complex technical concept to a non-technical stakeholder.
Tell us about a time you had to explain a complex technical concept to a non-technical stakeholder.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle disagreements with team members regarding technical direction?
How do you handle disagreements with team members regarding technical direction?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Can you describe a situation where you had to work under significant pressure or tight deadlines?
Can you describe a situation where you had to work under significant pressure or tight deadlines?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Can you walk us through your experience with Java and the Spring framework?
- 02
Describe a time you had to debug a complex issue in a production environment.
- 03
Tell us about a time you had to explain a complex technical concept to a non-technical stakeholder.
- 04
How do you handle disagreements with team members regarding technical direction?
How difficult are the technical assessments?
The difficulty is generally moderate to high. You should be prepared for LeetCode-style medium problems, system design questions, and potentially a take-home assignment that tests your ability to build a small, functional application.
Maybank Singapore Software Engineer candidate reports ↗What is the typical timeline from application to offer?
The process can take anywhere from a few weeks to several months. It is important to remain patient but also to follow up with your recruiter if you haven't received an update after a reasonable period.
Maybank Singapore Software Engineer candidate reports ↗How can I stand out during the interview?
Demonstrate a deep understanding of your past projects, show enthusiasm for the banking domain, and maintain a proactive, solution-oriented attitude even when faced with ambiguous questions.
Maybank Singapore Software Engineer candidate reports ↗Is there a specific focus on company values?
Yes. Familiarize yourself with the core values of Maybank Singapore. During behavioral rounds, interviewers often look for evidence that your personal work style aligns with these values.
Maybank Singapore Software Engineer candidate reports ↗What topics does Maybank Singapore test in interviews?
Maybank Singapore interviews most often cover Problem Solving, Stress Management, Requirements Gathering, Time Management, and Redux. The exact emphasis depends on the specific role you apply for.
Maybank Singapore Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Maybank Singapore Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Zemoso Technologies Software Engineer Interview Guide
What Zemoso Technologies asks Software Engineer candidates, from reported rounds and questions.
WorldWide Technology Holding Software Engineer Interview Guide
What WorldWide Technology Holding asks Software Engineer candidates, from reported rounds and questions.
Upgrade Software Engineer Interview Guide
What Upgrade asks Software Engineer candidates, from reported rounds and questions.
Tyfone Software Engineer Interview Guide
What Tyfone asks Software Engineer candidates, from reported rounds and questions.