Requirements

The tech you will work with
Frontend: React, React Flow (node-based graph editors)
Backend: Python, Node.js, FastAPI
Data: ClickHouse, Kafka (event streaming), Debezium (CDC)
AI/ML: LangGraph (agent orchestration), LLMs (prompt engineering, RAG, tool use), DPT-2 (document extraction), PageIndex (long-document reasoning), Weaviate (vector search)
Permissions: OpenFGA (Zanzibar-based relationship access control)
Observability: Langfuse (LLM tracing), OpenTelemetry
Cost control: LiteLLM (gateway + budgets), Orkestra (model routing)
Infrastructure: dbt (semantic layer / MetricFlow), Temporal (scheduling), DataHub / OpenMetadata (catalog)

Note:You don’t need to know all of this on day one. You need to be the kind of person who can pick up any of it in a week.

What we're looking for
The non-negotiables
You can code. Full-stack, independently, at production quality. You’ve built things — not just assignments, but projects, tools, systems that other people actually used. You’re comfortable across the stack and you don’t need hand-holding to ship a feature.
You can communicate. You can explain a technical architecture to a non-technical client. You can run a discovery call. You can write a clear document. You can present without slides being your crutch. This is not a “nice to have.” Half the job is translating between the worlds of technology and business.
You can think. When someone describes a messy process, you don’t just nod — you ask why before how. You spot patterns underneath apparent chaos. You push back on unnecessary complexity. You can hold a system in your head and reason about what happens when things go wrong.
You learn fast. You don’t need to know logistics. You need to be the kind of person who, after two client calls and a week of reading, can hold their own in a conversation about Bills of Lading, demurrage charges, and incoterm implications. Domain knowledge is teachable. Curiosity and raw learning speed are not.
Strong signals
You’ve built something with LLMs — not just used ChatGPT, but actually integrated an LLM into a working system. Prompt engineering, tool use, agents, RAG — any of it.
You’ve worked on a side project or open-source contribution that required you to understand a domain outside of CS.
You can take a vague, messy brief and turn it into a structured plan without needing everything spelled out.
You default to shipping over perfecting. You’d rather build a rough working version in 2 hours than spend 2 days on a flawless spec.
You’ve done consulting, client-facing work, or been in a situation where you had to understand someone else’s world to solve their problem.