Home → The 6Q Method
The 6Q Method
Six intelligences, one of which your degree measured. The programme is designed so that all six get trained by the work itself — and so that you leave with evidence of each.
Why six, and why now
The 6Q framework comes from The Resilient IT Professional, written after roughly 25 years of watching who lasts in Indian IT and who doesn't. The finding is unglamorous: technical ability gets people hired, and almost never explains who is still growing a decade later. As AI absorbs more of the technical execution, the other five stop being "soft skills" and start being the job.
"IQ opens the door. It's also the rail you climb on — you keep sharpening it while the other five intelligences grow."
The entry ticket. Python, APIs, LLM behaviour, agent architecture, and the finance domain your agents operate in. Never "finished" — kept sharp for the whole programme.
- How it's trained
- Briefs that require a skill you don't yet have, with mentor guidance rather than lectures.
- Evidence you leave with
- Working agents in a public GitHub portfolio, with commit history.
Taking a hard review without deflating. Saying "I'm stuck" on day two instead of day nine. Noticing what your own frustration is doing to your judgement.
- How it's trained
- Daily reviews with real pushback, and deadlines that occasionally you will miss.
- Evidence you leave with
- A year of written updates showing how you handled the bad weeks.
Production breaks. The client changes the brief on Wednesday. The approach you spent two weeks on turns out to be wrong. AQ is what you do in the hour after.
- How it's trained
- Deliberate mid-week scope changes and demos where things fail in front of people.
- Evidence you leave with
- Post-mortems you wrote on your own failures — the single most interviewable artefact you can own.
The forward-deployed part of Forward Deployed Engineer. Explaining a technical constraint to someone who doesn't want to hear it, and being believed.
- How it's trained
- Standups, demo days, and defending your own work to a room that asks hard questions.
- Evidence you leave with
- Recorded demos of you presenting and defending your work.
Most bad software is a correct answer to the wrong question. CINQ is the reflex to ask what the customer is actually trying to achieve before writing a line.
- How it's trained
- Briefs written deliberately ambiguously. Asking is rewarded; assuming is expensive.
- Evidence you leave with
- Written problem framings that preceded each build.
Agents touching KYC documents, credit decisions and customer data make this concrete rather than philosophical. Where does automation stop? What do you refuse to ship?
- How it's trained
- Finance-domain briefs where the easy technical answer is the wrong answer.
- Evidence you leave with
- Decisions you argued for and can still explain a year later.
The book behind the method
The Resilient IT Professional sets out the 6Q framework and the career logic underneath 6Qs: what actually keeps an IT career growing when the technology under it keeps changing. 6Qs is that book applied to one specific role, for one specific year of someone's life.
Why not just a certificate?
Because a certificate proves attendance and the market has stopped reading them. Every artefact above is evidence of behaviour under real conditions — which is what an interviewer is trying to infer anyway, usually badly, from a CV.
The method only works in the room.
Start with the Trial Month and see whether it's for you.