No training dumps. Every file you touch ships to a real site with a real programme. You see the coordination call happen; you hear what the contractor said on Monday.
Draft the model.
Close the gaps.
Hand over something that builds.
We're a small studio in India authoring federated BIM models for architects, engineers, and contractors in the EU, Middle East, and US. The bar is craft — measured in clean families, not hours logged.
Why build
from here.
We didn’t start a BIM shop. We started a practice that happens to deliver BIM — which is a different thing, and it shows in the work.
The person who authored a wall is the person who defends it in Navisworks. Ownership runs the length of a package — model, clash, response, resolution.
India team, caseload in London, Dubai, Singapore, Austin. You'll write concise English, work to overlapping time-zones, and develop an eye for how each market reads drawings.
Five roles.
All authored, not posted.
Each line is a seat we’re actively filling. We write the briefs ourselves — no recruiter filter between you and the team you’d join.
BIM Coordinator
Run weekly coordination on live packages. Author clash reports that resolve, not just filter. Revit + Navisworks, ACC.
MEP Modeler
Model mechanical, electrical, and plumbing systems to LOD 350–400. Clean families, clean views, clean worksets.
Structural Modeler
Concrete, steel, and composite framing. Translate structural drawings into constructible families without losing the engineer's intent.
Scan-to-BIM Specialist
Point clouds to federated models. Recap, Cyclone, Revit — register, segment, author. You know why a 6mm tolerance matters.
Information Manager
Own the BEP. Draft the EIR response. Run the CDE. Senior role, reports to practice lead.
Don’t see your seat? Write anyway. We keep a short list for roles we’ll open next quarter — careers@twintech.co.
The bar, written
in plain ink.
Two lists. One you can measure in a file, one you can only measure in a room. We weigh them the same.
- 01Clean families. Clean views. Clean worksets.
- 02Navisworks clashes resolved, not just filtered.
- 03Knows why LOD 350 isn't LOD 400.
- 04Reads a structural drawing as fluently as a floor plan.
- 05Writes a BEP you'd actually follow.
- 01Defends the model in coordination meetings.
- 02Notices when a detail lies.
- 03Writes short emails.
- 04Says "I don't know" when they don't.
- 05Sends the file on time, or flags it early.
Four steps.
No take-home grind.
Same shape for a modeler or a lead. Every round has a clear purpose — we’ll tell you what it is before it starts.
Write
A short cover note and three portfolio links — not a scanned CV. Tell us what package you authored, what you'd do differently, and why.
Call
Twenty-five minutes. Technical, then context. We want to hear you talk about a file you cared about — what broke, what held.
Task
A scoped, paid piece of work — real-ish in shape, small in scale. You walk us through it after. This is the round that matters.
Offer
Within ten working days of the task. Clear compensation, clear progression, no take-home surprises.