At Bmll Technologies, a Software Engineer plays a pivotal role in democratizing access to complex financial data. The company is a pioneer in historical financial data science, specializing in Level 3 order book data and analytics. As a engineer here, you are not simply building standard web applications; you are designing, optimizing, and scaling the backend systems and APIs that process billions of financial messages daily. Your work directly impacts global investment banks, quantitative hedge funds, and asset managers who rely on Bmll Technologies to backtest trading strategies, conduct market microstructure research, and comply with regulatory requirements. You will work on high-performance computing pipelines, cloud-native architectures, and data delivery systems that must handle petabyte-scale datasets with absolute precision and minimal latency. This role requires a unique blend of deep software engineering principles, rigorous analytical thinking, and a passion for optimization. Whether you are refactoring core data processing libraries or architecting a new microservice, your contributions will directly influence the speed, reliability, and capability of the platform, making it an intellectually stimulating and highly impactful environment for engineers who love hard technical challenges.
Initial Conversation
reportedA two-way discussion with the hiring manager about your background, engineering experience, and the role's scope.
What to demonstrate
- A two-way discussion with the hiring manager about your background, engineering experience, and the role's scope
- Depth in Python
How to prepare
- Answer aloud and timed: Given a set of strings, write an optimized algorithm to find the longest common subsequence using dynamic programming.
- Answer aloud and timed: Implement a memory-efficient parser for a stream of financial transaction logs.
Live Coding Session
reportedA rigorous technical evaluation where you demonstrate your coding capabilities in real-time.
What to demonstrate
- A rigorous technical evaluation where you demonstrate your coding capabilities in real-time
- Depth in Python
How to prepare
- Answer aloud and timed: Write a function to detect cycles in a directed graph representing dependency chains in a data pipeline.
- Answer aloud and timed: How would you optimize a search algorithm to run in sub-linear time over a sorted but continuously updating dataset?
System Design Discussion
reportedAn in-depth discussion focused on designing systems and understanding architectural principles.
What to demonstrate
- An in-depth discussion focused on designing systems and understanding architectural principles
- Depth in Python
How to prepare
- Answer aloud and timed: Explain how the Global Interpreter Lock (GIL) affects multi-threading in Python, and how you would bypass it for CPU-bound tasks.
- Answer aloud and timed: Describe the difference between deep and shallow copying in Python, and how memory allocation is managed under the hood for large lists.
Deep-Dive Technical Interview
reportedA thorough interview concentrating on language internals and specific engineering concepts.
What to demonstrate
- A thorough interview concentrating on language internals and specific engineering concepts
- Depth in Python
How to prepare
- Answer aloud and timed: How do Python decorators work? Write a custom decorator that profiles memory usage and execution time of a function.
- Answer aloud and timed: Explain the difference between generators and iterators, and demonstrate how generators optimize memory when processing large data files.
PracHub editorial advice for the preparation topics above.
Master Python's "Why
Do not just know how to write Python code; understand why a specific approach is faster or more memory-efficient. Be prepared to explain the inner workings of generators, memory allocation, and the GIL.
Focus on Trade-offs in System Design
There is no single "correct" architecture. When designing a system, always present multiple options and explain why you chose one over another based on throughput, latency, cost, and complexity.
Drive the Coding Collaboration
If you get stuck during a coding round, do not freeze up. Talk through your thought process, state what you are trying to achieve, and actively invite the interviewers to collaborate with you.
Highlight Data-Scale Experience
Throughout your interviews, emphasize any past experience you have working with large datasets, pipeline optimization, or high-performance computing, as this directly aligns with the company's core business challenges.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Given a set of strings, write an optimized algorithm to find the longest common subsequence using dynamic prog
Given a set of strings, write an optimized algorithm to find the longest common subsequence using dynamic programming.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Implement a memory-efficient parser for a stream of financial transaction logs.
Implement a memory-efficient parser for a stream of financial transaction logs.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Write a function to detect cycles in a directed graph representing dependency chains in a data pipeline.
Write a function to detect cycles in a directed graph representing dependency chains in a data pipeline.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you optimize a search algorithm to run in sub-linear time over a sorted but continuously updating da
How would you optimize a search algorithm to run in sub-linear time over a sorted but continuously updating dataset?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain how the Global Interpreter Lock (GIL) affects multi-threading in Python, and how you would bypass it f
Explain how the Global Interpreter Lock (GIL) affects multi-threading in Python, and how you would bypass it for CPU-bound tasks.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Describe the difference between deep and shallow copying in Python, and how memory allocation is managed under
Describe the difference between deep and shallow copying in Python, and how memory allocation is managed under the hood for large lists.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
How do Python decorators work? Write a custom decorator that profiles memory usage and execution time of a fun
How do Python decorators work? Write a custom decorator that profiles memory usage and execution time of a function.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Explain the difference between generators and iterators, and demonstrate how generators optimize memory when p
Explain the difference between generators and iterators, and demonstrate how generators optimize memory when processing large data files.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Discuss the trade-offs between using SQL versus NoSQL databases for storing structured financial market events
Discuss the trade-offs between using SQL versus NoSQL databases for storing structured financial market events.
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?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
What are dunder (double underscore) methods, and how would you use them to customize class instantiation or op
What are dunder (double underscore) methods, and how would you use them to customize class instantiation or operator overloading?
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 distributed, fault-tolerant system to ingest and process gigabytes of financial market
How would you design a distributed, fault-tolerant system to ingest and process gigabytes of financial market data per second?
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 your approach to scaling a RESTful API that serves historical data queries to thousands of concurrent
Describe your approach to scaling a RESTful API that serves historical data queries to thousands of concurrent institutional clients.
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
How would you design a caching layer to minimize database load for frequently accessed historical order book s
How would you design a caching layer to minimize database load for frequently accessed historical order book states?
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?
Edge instances grow 400 MB per hour until the nightly restart
Edge API instances start at 700 MB resident and grow about 400 MB/hour; a nightly rolling restart has hidden it for weeks. Growth continues unchanged when request rate halves overnight, p99 degrades in the last hours before an instance is recycled, and heap used immediately after a forced full GC rises monotonically. The service holds no product state. Name the discriminating measurement that separates the plausible causes, give the most likely cause, and give the fix and how you would verify it.
Approach
- Separate resident memory from live heap first, because they fail differently. Resident size can grow from fragmentation, native buffers or thread stacks while the heap is flat; heap used after a full GC rising monotonically is the measurement that says objects are reachable and not being released. You already have it, so this is retention, not fragmentation, and that closes off half the candidate list.
- Use the rate's independence from traffic as the discriminator. Growth that continues at half the request rate rules out per-request objects that are merely slow to collect and points at a structure that grows with distinct values observed rather than with call volume. Write the candidates that have that property: a metrics registry keyed on a high-cardinality label, an unevicted cache, an interner, a per-key lock map.
- Take two heap snapshots an hour apart and diff by retained size, reading the dominator tree, not by allocation count or instance count. Expect one root holding a map with millions of entries, then follow the reference chain to the code that inserts and never removes. Allocation profilers point at churn, which is the wrong signal here.
- The candidate that fits this service is an observability label carrying an identifier, such as a request path recorded before templating so that /v1/resources/48213 becomes its own metric series. That grows with distinct ids seen, is independent of rate, and explains the late p99 degradation, since GC cost rises with the size of the live set.
Follow-up
- Post-GC heap is now flat but resident size still creeps. What are you looking at, and does it matter?
- How would you have detected this before an OOM, given the nightly restart masked the trend?
Built from the rounds and topics Bmll Technologies candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Bmll Technologies loop
- Write out the reported sequence: Initial Conversation, Live Coding Session, System Design Discussion, Deep-Dive Technical Interview.
- 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 4 reported rounds, with the weakest marked.
02Work Python
- Spend the session on Python, which Bmll Technologies candidates report being tested on.
- Write one worked example in Python and time yourself on it.
Deliverable: One timed worked example in Python.
03Work Dynamic Programming
- Spend the session on Dynamic Programming, which Bmll Technologies candidates report being tested on.
- Write one worked example in Dynamic Programming and time yourself on it.
Deliverable: One timed worked example in Dynamic Programming.
04Work System Design
- Spend the session on System Design, which Bmll Technologies 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.
05Answer out loud: Coding and Algorithmic Problem Solving
- Answer aloud, timed: Given a set of strings, write an optimized algorithm to find the longest common subsequence using dynamic programming.
- Answer aloud, timed: Implement a memory-efficient parser for a stream of financial transaction logs.
Deliverable: Spoken answers to 2 reported Coding and Algorithmic Problem Solving question(s), under time.
06Answer out loud: Python Core and Internals
- Answer aloud, timed: Explain how the Global Interpreter Lock (GIL) affects multi-threading in Python, and how you would bypass it for CPU-bound tasks.
- Answer aloud, timed: Describe the difference between deep and shallow copying in Python, and how memory allocation is managed under the hood for large lists.
Deliverable: Spoken answers to 2 reported Python Core and Internals question(s), under time.
07Answer out loud: System Design and Scalability
- Answer aloud, timed: How would you design a distributed, fault-tolerant system to ingest and process gigabytes of financial market data per second?
- Answer aloud, timed: Describe your approach to scaling a RESTful API that serves historical data queries to thousands of concurrent institutional clients.
Deliverable: Spoken answers to 2 reported System Design and Scalability 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.
Walk me through the most technically challenging backend system you have designed and deployed to production.
Walk me through the most technically challenging backend system you have designed and deployed to production.
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?
Explain a scenario where you had a technical disagreement with a teammate or lead. How did you resolve it and
Explain a scenario where you had a technical disagreement with a teammate or lead. How did you resolve it and arrive at a solution?
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?
Why do you want to work at Bmll Technologies, and how does your background in backend engineering align with o
Why do you want to work at Bmll Technologies, and how does your background in backend engineering align with our data-intensive product?
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 when you had to optimize a slow-performing system. How did you identify the bottleneck, and wh
Describe a time when you had to optimize a slow-performing system. How did you identify the bottleneck, and what was the outcome?
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
Walk me through the most technically challenging backend system you have designed and deployed to production.
- 02
Explain a scenario where you had a technical disagreement with a teammate or lead. How did you resolve it and arrive at a solution?
- 03
Why do you want to work at Bmll Technologies, and how does your background in backend engineering align with our data-intensive product?
- 04
Describe a time when you had to optimize a slow-performing system. How did you identify the bottleneck, and what was the outcome?
How difficult is the interview process for a Software Engineer?
The process is intellectually rigorous and average-to-hard in difficulty. It places a strong emphasis on deep language internals (particularly Python) and complex algorithmic problem-solving. However, prep work focusing on core programming principles and system design trade-offs will position you well for success.
Bmll Technologies Software Engineer candidate reports ↗What is the culture like within the engineering team?
The engineering team operates like an intellectual hub, valuing deep technical curiosity, precision, and high-quality code. While some interviewers can be highly analytical and academic, the team is generally collaborative and focused on solving genuinely hard data-scale problems together.
Bmll Technologies Software Engineer candidate reports ↗How much preparation time should I allocate before the interviews?
It is recommended to spend at least 2 to 3 weeks preparing. Focus your time on practicing medium-to-hard algorithmic challenges, reviewing advanced Python internals (such as memory management and concurrency), and studying distributed system design patterns.
Bmll Technologies Software Engineer candidate reports ↗What is the typical timeline from the initial screen to an offer?
The entire process typically takes between 3 to 5 weeks, depending on candidate and interviewer availability. The recruitment team generally keeps candidates well-informed of their status between rounds.
Bmll Technologies Software Engineer candidate reports ↗What topics does Bmll Technologies test in interviews?
Bmll Technologies interviews most often cover Python, Order Book Data (Level 1/2/3, T+1), Dynamic Programming, Quantitative Finance, and Derivatives (Exchange-traded derivatives). The exact emphasis depends on the specific role you apply for.
Bmll Technologies 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.
- 01Bmll Technologies 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.
Scale Ai Software Engineer Interview Guide
Data structures and algorithms practice for Scale Ai candidates, where stating a bound means stating its precondition: constant-time hash lookup is an average case over keys that spread.
Lambda Software Engineer Interview Guide
Failure-handling practice for Lambda software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.