Our internships run from our Kathmandu studio — Hazesoft’s engineering home — and most of the questions applicants send us are the same ten. This post answers them once, and then explains exactly what we look for in an application, because our format is unusual: one email, three things in it.
What an internship at Hazesoft actually is
You sit inside one of our client squads with a named mentor. Your code ships to production and goes through the same review gates as everyone else’s — static analysis, eval suites, human sign-off. From day one you work in our AI-assisted delivery loop: agentic tooling handles the mechanical work under senior architecture, and you spend your time on the judgement calls.
Internships are paid and run 3–6 months. Interns who clear our bar are considered for an offer — the same bar we hire senior engineers against.
The four tracks
- AI, ML & research — retrieval systems, evaluation harnesses and model ops on real client systems. Research-grade problems that ship to production.
- Software engineering — product engineering across web and mobile: TypeScript, Kotlin, Swift.
- QA & test automation — test pyramids, automation, and the eval-gated review discipline our teams run.
- Data & platform — pipelines, observability and cloud infrastructure.
Our Kathmandu studio takes interns across all four tracks. Hazesoft is the internal engineering team of HDL Group — Nepali culture, Swedish design — so the bar and the delivery discipline are the group’s own.
The questions everyone asks
Do I need AI or agent experience?
No. You need the appetite to work in a loop where tooling does the mechanical and you own the judgement. The workflow is something we teach; the curiosity is something you bring.
Do you read CVs?
We read for signal, not CVs. A repo, a shipped side project, a thesis prototype — anything real we can run or read beats a two-page PDF. Polish matters less than the decisions you made.
When are applications open?
Always. Scheduled intakes are posted on the internships page when they open, and spontaneous applications are open year-round. We reply within a week, yes or no.
How to stand out: the three questions
Our application is one email with three things in it. Here is how to answer each one well.
1. The thing you built
A link — repo or live version. It does not need to be finished or beautiful. A readme counts as a writing sample, so a clear one is worth an evening of your time. What we are checking: did you build something real, and can we run or read it?
2. The hardest decision in it
Ten lines, maximum. What you traded away and why — the dead ends, and what you would do differently now. This is the part we read twice, because judgement is the thing we cannot teach fast. An honest “I chose X and it cost me Y” beats any list of technologies.
3. When and where
Your window (for example “Jan–Jun 2027”). Internships are based in our Kathmandu studio.
The application form pre-fills all three into an email for [email protected]. Twenty minutes if you have actually built something.