Technical rubric
We look at how someone decomposes a problem, reasons about data and failure modes, and reads code they did not write. Languages and frameworks come second to judgment. Interviews use problems from real systems, not puzzles.
Back to Intika
Engineering at Intika
Small team. Senior judgment. Difficult systems.
How we hire, how we work, and what we expect from each other. Written down so candidates and clients can hold us to it.
How we hire
Language rubric
We work mainly in Spanish. Technical English matters: documentation, code, tools, and continuous learning. Speaking it fluently matters when the role requires it. We assess clarity, not accent.
Growth
Engineers are expected to grow in scope over time: from tasks to features, from features to systems, from systems to decisions. We make that path explicit and review it together.
Interpersonal skills
Disagreeing clearly, asking early, giving and taking feedback, and being someone people like working with.
What we value
Responsibility
If we ship it, we remain accountable for how it behaves in production.
Excellence
The standard is work we would hand to the next engineer, and to the client, without needing to explain it.
Judgment
We don’t apply recipes. We understand the problem, make the risks explicit, and choose the simplest solution that solves what matters.
How we work day to day
Mentorship
Senior engineers grow the people around them. It is part of the job, not a side activity, and it is how a small team gets stronger without getting bigger too fast.
Recruiting across Peru
We recruit across the whole country, including outside Lima. Judgment, learning ability, and ownership travel. A postal code does not matter.
AI-assisted development
We use AI throughout the engineering process where it improves speed and understanding, from exploration and implementation to testing and debugging. Every change is still reviewed by an engineer who owns the result.
Technical writing
Design notes, decision records, runbooks, and clear commit messages are part of the work. Writing is how judgment becomes transferable.
Talks, events, and open source
We encourage engineers to speak, attend, and contribute. What we learn building difficult systems is worth sharing, within the limits of client confidentiality.
Roles are published as they open. If this reads like you, write to us.
Write to us