/ apply · Def-tech company

Junior+ Full Stack Developer

Two steps. Rate your own spectrum honestly — we show the role's spectrum beside it. Then a few details. No résumé parsing.

01 · Your spectrum
02 · Details
01 Pick your thinking level

Not seniority — the scope of problem you hold in your head. Pick the largest scope you regularly own end-to-end, not the biggest you've ever touched. Be honest; we calibrate the interview to it.

01
Task
A single work item.
02
Component
A bounded module end-to-end.
03
Subsystem
Multiple interacting components, architectural trade-offs.
04
Team
People, processes, collective work.
05
System
The whole organization, strategy, market.
Your level
02 Rate yourself, honestly
Move every axis to where you honestly sit.
What spectrum means and how we read it

We use the spectrum to identify a person's core strengths and leanings — not to measure the value of any single axis. What matters is the shape, not the precise numbers under it.

The values are indicators of the style of work, thinking strategies, and professional profile. They show what someone reaches for first, where their attention naturally goes, what they keep building muscle around.

Self-rating is subjective — we know that. We treat the spectrum as a source of topics for the conversation, not a matching decision tool. Two engineers with very different shapes can both be right for the same role; two with the same shape can land in opposite directions in the interview.

Honest beats flattering. What we care about is having something real to talk about together.

Systems Thinking Systems Thinking Understanding connections and emergent behavior, not just isolated components. Engineers who see the whole system catch problems before they become production fires.
Building the model that solves the problem.
Orientation Orientation Setting the goal, not just hitting it. Defining what the work actually is under ambiguity. AI solves framed problems; framing them is the human part.
Choosing the frame the work is seen from.
Antifragility Antifragility Your tech stack will change. Your market will shift. You need engineers who install lessons into how they work next, not engineers who collect war stories.
Turning failures into structure, not into stories.
Security Awareness Security Awareness AI-generated code ships fast. The vulnerabilities ship with it. Can your engineer find what the model missed — in others' code and in their own?
Reading code the way an attacker would. Especially the code you just wrote.
AI Symbiosis AI Symbiosis Using AI as a force multiplier — delegation, verification, calibration. Winners know when to delegate and when to override, and keep their map current.
Knowing what to hand to the model, what to hold, and how to check the result.
Reciprocity Reciprocity The value an engineer returns to the team. One engineer who makes the whole team stronger is worth more than three who ship in isolation.
Value passes through you — and leaves stronger.
Honest self-assessment beats flattering one. We interview against this spectrum — the signal, not the score, is what gets you through.