dwij in pilot
chapter 1 of 7 · start

your cv sounds like everyone’s.
your work doesn’t.

map your skills once, in a conversation about what you’ve actually built. startups find you for what you’ve shown, and if it’s a no, you’ll hear why.

get mapped first try a practice question ↓
free, alwaysone cv, that’s allno github neededyou’re told before anyone sees you
d dwijsample conversation
hi, i’m dwij. send your cv, or just tell me what you’ve built.
pdfmy_cv.pdf1 page
i rebuilt our audio relay last year. that’s the part i’m proud of.
your cv, as i read it results-driven engineer passionate about scalable, low-latency solutions rebuilt the websocket audio relay after one slow stream stalled every live call leveraged llms to drive impactful outcomes
the strongest line is the relay. that’s what i’ll ask you about, not the buzzwords.
your mapping · tonight, 10:14 pmstage 2 of 3
p99 jumps to 3.2 s at 7 pm. this is your code from before the fix:
r.queue.Push(f) // one queue, all calls r.asr.Send(r.queue.Pop())
“the queue was shared, so one slow stream made everyone wait…”
voice or typing
your skill map
real-time streaming● ● showntail latency● ● shownmodel fallbacks● ○ understandstenant isolationnot mapped yet
you see it before anyone else. strengths first.
dwij · thursday 11:02 your profile is going to a voice ai startup in bengaluru for a backend role. okay? that’s finehold it
they see only what this role needs.
before your interview · thursday 4 pm they’ll probably ask about: model fallbacks. you understand them, haven’t run one live. your relay, again. look at stream/relay.go first. what they’ll ask about. never what to say.
interview done · thursday 4 pm✓
their answer, two days later “strong on streaming. we need someone who’s run fallbacks in production.”
next on your skill map: run a fallback for real. two other startups are still talking to you.
illustration send your cv. that’s all.
chapter 2 of 7 · practice

try one first. nothing’s at stake.

this is how a mapping feels: a situation that unfolds as you answer. no trick questions, no definitions to recite. at the end you’ll see what a strong answer usually covers, so you can check yourself.

a self-check · nothing is marked, saved or sent
a situation · concurrencystage 1 of 3
support says two passengers both got seat 14c on the same flight. both have boarding passes. where do you look first?
chapter 3 of 7 · map your skills

one conversation. about your work.

about 25 minutes, on your laptop, tablet or phone, whenever suits you. the questions come from your own cv and code, so there’s nothing to cram for.

voice or typing.switch any time. no video, ever. plain english is enough.i mark what you mean, not your grammar. pausing to think is fine.“i don’t know” is a real answer too. no github? fine.most work lives in private repos. the conversation carries it.
dwij.io/map · skill map session · sample 11:42 / 25:00
anchor 2 of 4 · real-time streaming stage 2 of 3
the situation at 7 pm, p99 jumps from 700 ms to 3.2 s. the llm traces look normal. this is from your repo:
// stream/relay.go · your commit 9e14c2 func (r *Relay) onFrame(f Frame) { r.queue.Push(f) // one queue, all calls r.asr.Send(r.queue.Pop()) }
tap a line to point at it.
dwij › what in this code lets one slow call slow down every call?
“the queue is shared… if one asr stream is slow, everyone’s frames wait behind it. i’d give each call its own bounded buffer.”live transcript
so you mean: a buffer per call, so one slow consumer can’t block the rest? yes, thatnot quite
⌨ type instead listening i don’t know
anchor 2 of 4 · real-time streamingstage 2 of 3 · 11:42
at 7 pm, p99 jumps to 3.2 s. the llm traces look normal. from your repo:
func (r *Relay) onFrame(f Frame) { r.queue.Push(f) // one queue, all calls r.asr.Send(r.queue.Pop()) }
dwij › what lets one slow call slow down every call?
“the queue is shared… i’d give each call its own bounded buffer.”
so you mean: a buffer per call, so one slow consumer can’t block the rest?yesnot quite
⌨ type i don’t know
streaming · stage 2 of 311:42
p99 jumps to 3.2 s at 7 pm. your code:
r.queue.Push(f) // all calls r.asr.Send(r.queue.Pop())
dwij › what lets one slow call slow every call?
“the queue is shared… a bounded buffer per call.”
so you mean: a buffer per call?yesnot quite
⌨ type skip hold to talk
your skill map sample · mapped 3 oct 2026
strongest at keeping real-time systems fast under load.
real-time streaming● ● shown tail latency● ● shown model fallbacks● ○ understands tenant isolationnot mapped yet · asked for in 4 roles you match
next steprun a fallback for real: connect a repo where you did, or take the agent task. connected · voice-relaycompanies see the summary. your code itself is never shown. change
chapter 4 of 7 · your skill map

you see it first. all of it.

strengths first. what’s thin shows up as a next step, not a mark against you. if i wrote down something you said wrongly, you can correct it before anyone else sees it.

done once. reused for every company. refresh it when you grow.
chapter 5 of 7 · told first

nothing goes anywhere without telling you.

before your profile reaches a company, i message you with its name and the role. reply hold, and it doesn’t go. companies see only what that role needs.

dwij · now · sample your profile is going to a voice ai startup in bengaluru for a backend role: real-time voice, mid to senior. that’s finehold itsee what they’ll see →
what they’ll see
real-time streaming · ● ● shown
tail latency · ● ● shown
model fallbacks · ● ○ understands
not shown: anything this role didn’t ask for
before your interview · thursday 4 pm · sample they already know you’re strong on streaming. they’ll probably ask about:
model fallbacks. you understand them; you haven’t run one in production. be ready to say what the caller hears. tenant isolation. not mapped yet. think about how one bank’s data stays away from another’s. your relay, again. they’ll ask you to walk through it. look at stream/relay.go first.
chapter 6 of 7 · prepared

prepared, not coached.

before each interview you get what the founder will likely ask about, and where to look in your own work. never what to say. the point is to show them you, ready.

chapter 7 of 7 · you hear why

and if it’s a no, you hear why.

after every interview i ask the company for its reason and pass it on, in plain words. if they haven’t answered, you see that too, and for how long. nobody else in hiring does this.

your reasons · sample
voice ai startup · bengaluru · 2 days ago “strong on streaming. we needed someone who has already run model fallbacks in production.”
fintech · gurugram · 3 weeks ago “good fit, but we hired someone who could join in 15 days.”
logistics startup · noida · no reason yet, 6 days and counting
the pattern2 of your last 3 reasons mention production fallbacks. that’s your next step on the skill map.
questions

what engineers ask first.

all questions, answered plainly →
what is dwij for engineers?

a free way to be found for your real work instead of your cv. you map your skills once, in a conversation about what you have built, and startups find you for what you have shown. you see your skill map before any company does.

what is a skill map?

a skill map is your record of the concepts you understand and the things you have done, each with the evidence behind it: a quote from your mapping, the stage of a situation you reached, or a line of code you chose to share.

is my mapping run by a person?

no. dwij, an ai agent, runs the whole conversation. a person only sees it if something is flagged, and they talk to you before anything happens.

is dwij free for engineers?

yes, always. companies pay dwij when they hire. you never pay anything, at any point.

do i need a github profile or a good college?

no. sharing code can add evidence, but having no public code is never held against you, and neither is your college. the conversation about your work is what counts.

is dwij live?

dwij is in pilot. right now you can join the first list by dropping your cv. mapping opens to that list first, and we will write to you when it does.

your data, plainly.

recordings and transcripts exist to build your skill map and to tell you why. that’s all they’re for.

free, always.companies pay when they hire. you never pay, at any point.
never sold, never shared.used to put you forward, and for nothing else. private code is never shown to anyone.
stop any time.reply “delete” to any email from dwij and everything goes. otherwise it’s all deleted after 12 months.
no emotion or stress reading from your voicedwij never rejects anyonea person reviews anything flagged, and talks to you first

show them what you’ve built.

dwij
dwij is built by Codeclowns Technologies LLP · Gurugram · © 2026