Koshalta

Tasks

About These Tasks

This is not a test with a correct answer. We are more interested in how you think than what you build.

Timebox: 1–2 hours total

Systems Thinking

Infrastructure / Backend / Generalist 60 to 120 minutes

You are given an organization with 20+ internal applications, a mix of legacy systems and modern services, and no single source of truth for data. Design a lightweight way to observe how data flows between these systems without rewriting or replacing them. You do not need to implement anything.

Response Expectations
  • Describe your approach
  • Explain why you chose this approach
  • Mention what you deliberately chose not to do
Evaluation Signals
  • Ability to abstract and simplify
  • Restraint in avoiding over-engineering
  • Layered thinking over tool-first thinking

Research and Synthesis

All Roles 45 to 90 minutes

Pick one existing product or open-source project that attempts to unify, observe, or move data across systems. Analyze it from first principles.

Response Expectations
  • What problem the product is actually solving
  • Where it works well
  • Where it breaks down in real-world organizations
  • Sources or references used
Evaluation Signals
  • Ability to leverage existing knowledge
  • Understanding of context beyond features
  • Signal-to-noise filtering

Product Thinking

UI / UX / Product-Oriented Roles 45 to 90 minutes

Imagine a tool that sits on top of existing enterprise systems and gives engineers visibility into what is happening. Design the first user interaction.

Response Expectations
  • What the first screen shows
  • What information is intentionally hidden
  • One decision that may frustrate power users and why you would still make it
Evaluation Signals
  • Prioritization and taste
  • User empathy
  • Willingness to make trade-offs

Handling Ambiguity

Wildcard 30 to 60 minutes

Consider the statement: 'The system should adapt to existing infrastructure.' Interpret what this could mean, select one interpretation, and explain how you would validate whether it is correct.

Response Expectations
  • Multiple possible interpretations
  • A chosen interpretation
  • A validation or feedback mechanism
Evaluation Signals
  • Comfort with ambiguity
  • Assumption-making
  • Feedback-loop driven thinking