cswork / libraryOpen practice workspace

Interview guides · Konfío

Konfío Software Engineer Interview Guide

Konfío Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Konfío, you play a pivotal role in shaping the technological backbone of our innovative financial solutions. Your work directly impacts the efficiency and usability of our products, enabling us to serve our customers better and expand our reach in the competitive fintech landscape. By developing robust software solutions, you help bridge the gap between complex financial products and user-friendly applications that empower small businesses across Mexico. In this role, you will be involved in designing, implementing, and maintaining systems that support Konfío's mission to streamline financial access for the underserved. You will collaborate with cross-functional teams, including product, design, and operations, to tackle challenging problems that require both technical expertise and creativity.

This guide is scoped to a Software Engineer candidate at Konfío.

Focus areas

  • Object-Oriented Programming (OOP)
  • REST APIs (API REST)
  • Coding exercises / code challenges

The Konfío interview process

Konfío candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Call

Initial call from the recruiter to discuss the position and assess fit.

What to demonstrate

  • Initial call from the recruiter to discuss the position and assess fit
  • Depth in Object-Oriented Programming (OOP)

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 Interviews

Multiple interviews focusing on coding capabilities and conceptual understanding.

What to demonstrate

  • Multiple interviews focusing on coding capabilities and conceptual understanding
  • Depth in Object-Oriented Programming (OOP)

How to prepare

  • Answer aloud and timed: What are the key differences between SQL and NoSQL databases?
  • Answer aloud and timed: Describe how you would optimize a slow-performing application.

Cultural Fit Discussion

Discussion around company values to assess alignment with the organization.

What to demonstrate

  • Discussion around company values to assess alignment with the organization
  • Depth in Object-Oriented Programming (OOP)

How to prepare

  • Answer aloud and timed: What are some best practices for writing clean, maintainable code?
  • Answer aloud and timed: How would you approach debugging a system that is experiencing intermittent failures?

Where candidates lose points

Engage with Your Interviewers

Show genuine interest in the company and the role. Ask thoughtful questions about the team and projects to demonstrate your enthusiasm.

Prepare Real-World Examples

Be ready to share specific experiences that highlight your skills and achievements, particularly in collaboration and problem-solving.

Practice Coding Challenges

Utilize online platforms to sharpen your coding skills, focusing on algorithms and data structures that are relevant to the role.

Understand the Company Mission

Familiarize yourself with Konfío’s products and services, and be prepared to discuss how your skills align with our mission of empowering small businesses.

Questions & practice

Write a function to reverse a linked list.

Medium · Coding / Algorithms

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. 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 implement a binary search algorithm?

Medium · Coding / Algorithms

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. 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?

Solve a problem involving arrays and provide an optimal solution.

Medium · Coding / Algorithms

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. 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?

What are the key differences between SQL and NoSQL databases?

Medium · Technical / Domain Questions

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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?

Find version gaps and relay lag with window functions

Medium · window functions · event tables · frame semantics

outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.

Approach

  1. Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
  2. Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
  3. Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
  4. Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.

Follow-up

  • Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
  • Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?

Explain the principles of object-oriented programming.

Medium · Technical / Domain Questions

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 do you design a RESTful API?

Medium · Technical / Domain Questions

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 how you would optimize a slow-performing application.

Medium · Technical / Domain Questions

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 some best practices for writing clean, maintainable code?

Medium · Technical / Domain Questions

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Given a set of requirements, how would you prioritize features for a new application?

Medium · Problem-Solving / Case Studies

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 approach debugging a system that is experiencing intermittent failures?

Medium · Problem-Solving / Case Studies

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics Konfío candidates report.

Day 1 — Map the Konfío loop

  • Write out the reported sequence: Recruiter Call, Technical Interviews, Cultural Fit Discussion.
  • 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 3 reported rounds, with the weakest marked.

Day 2 — Work Object-Oriented Programming (OOP)

  • Spend the session on Object-Oriented Programming (OOP), which Konfío 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).

Day 3 — Work REST APIs (API REST)

  • Spend the session on REST APIs (API REST), which Konfío candidates report being tested on.
  • Write one worked example in REST APIs (API REST) and time yourself on it.

Deliverable: One timed worked example in REST APIs (API REST).

Day 4 — Work Coding exercises / code challenges

  • Spend the session on Coding exercises / code challenges, which Konfío candidates report being tested on.
  • Write one worked example in Coding exercises / code challenges and time yourself on it.

Deliverable: One timed worked example in Coding exercises / code challenges.

Day 5 — Answer out loud: Technical / Domain Questions

  • Answer aloud, timed: Explain the principles of object-oriented programming.
  • Answer aloud, timed: How do you design a RESTful API?

Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.

Day 6 — Answer out loud: Problem-Solving / Case Studies

  • Answer aloud, timed: How would you approach debugging a system that is experiencing intermittent failures?
  • Answer aloud, timed: Given a set of requirements, how would you prioritize features for a new application?

Deliverable: Spoken answers to 2 reported Problem-Solving / Case Studies question(s), under time.

Day 7 — Answer out loud: Behavioral / Leadership

  • Answer aloud, timed: Tell me about a time you had to work as part of a team to accomplish a goal.
  • Answer aloud, timed: How do you handle conflicts or disagreements with team members?

Deliverable: Spoken answers to 2 reported Behavioral / Leadership question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe a time when you faced a significant technical challenge. How did you overcome it?

Medium · Problem-Solving / Case Studies

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 me about a time you had to work as part of a team to accomplish a goal.

Medium · Behavioral / Leadership

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 conflicts or disagreements with team members?

Medium · Behavioral / Leadership

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?

What motivates you to excel in your work?

Medium · Behavioral / Leadership

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?