Why pre-screen creative technologists before the portfolio review
The title is used for two very different people. One is a designer who can prototype and hands off to engineers; the other builds production systems and has an eye. Both are valuable and they are not interchangeable. A short screen finds out which by asking what they built themselves and what broke when real people used it, which a showreel never shows.
What actually matters when screening Creative Technologist candidates
- 01
Portfolio
Review their reel of shipped interactive work: installations, WebGL microsites, Unity or Unreal experiences, physical prototypes. Ask what they personally built versus what the studio or vendor delivered.
- 02
Craft and rationale
Probe the toolchain: TouchDesigner, three.js, openFrameworks, Arduino or Raspberry Pi, projection mapping, sensors, MadMapper. Ask why they chose a stack over an easier off-the-shelf option.
- 03
Feedback and iteration
Test how they handle client and creative director notes mid-build, plus onsite failures during install week. Look for versioned prototypes, playtests and paper-to-screen iteration evidence.
- 04
Working with the brief
Assess how they translate a vague brand or campaign brief into technical scope: feasibility notes, budget for kit, install schedule, failover plan for unattended public running.
Pre-screening questions to ask Creative Technologist candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Things they built
3 questions01Can you describe a project where you used technology most inventively?
Listen forSomething that ran with real users, with what they built themselves stated clearly.
Concepts and pitches only, or projects where an engineer built everything technical.
02Have you developed any applications or software, and which are you proudest of?
Listen forCode they wrote themselves with the difficult part described, and the result available to look at.
Development described as directing, or nothing they can point at that they built.
03Can you explain a challenging project and how you resolved it?
Listen forA real technical or production problem, with the constraints and the compromise described.
Challenges described as client difficulty, or no technical problem that resisted a solution.
Technical depth real
3 questions04What is your level of experience with programming languages?
Listen forHonest depth stated per language, distinguishing what they build in from what they can read.
Many languages claimed at similar depth, or capability overstated relative to their examples.
05What is the primary language or environment you work in?
Listen forOne environment they are genuinely fluent in, with a sense of its limits and where they reach elsewhere.
No primary environment, or a stack chosen by fashion rather than by fit for the work.
06How have you used emerging technologies in your work?
Listen forNew technology used where it served the idea, with an honest account of what it did not deliver.
Technology used for novelty, or capability described from marketing rather than from building.
Intent survives build
3 questions07How do you keep the technical work aligned with the creative intent?
Listen forTechnical constraints raised early so the concept adapts rather than being compromised at the end.
Concepts fixed before feasibility is checked, or intent lost during implementation.
08Can you explain your process when starting a new project?
Listen forFeasibility explored alongside the idea, with prototypes used to test the risky part first.
Process starting from a finished concept, or the hardest technical question left until last.
09Can you share your experience with interface and interaction design?
Listen forInteraction designed for people unfamiliar with the work, with testing on someone outside the team.
Interaction designed for the demonstration, or usability tested only within the project team.
Feedback taken
3 questions10What methods do you use to ensure the quality of your work?
Listen forTesting under realistic conditions including duration, with failure modes anticipated for live use.
Quality checked only in short demonstrations, or no plan for something failing during an event.
11How do you work within a team and handle feedback?
Listen forFeedback taken without defensiveness, with a specific change that improved the outcome.
Creative decisions defended regardless, or collaboration described as handing work over.
12How do you explain technical ideas in a way non-specialists understand?
Listen forExplanation pitched at what the audience needs to decide, without overstating what is possible.
Capability oversold to clients, or explanations that leave stakeholders expecting too much.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Portfolio
35%5Shows named live builds with runtime, footfall or engagement figures, and clearly separates their own code and rigging from team contributions.
Craft and rationale
25%5Explains stack choices against latency, calibration, hardware cost and gallery constraints, and names the trade-off they accepted.
Feedback and iteration
25%5Describes discarding a working prototype after user testing, and cites specific notes that changed the interaction model rather than just the visuals.
Working with the brief
15%5Turns loose creative ambition into a scoped build with kit list, contingency for crashes, and honest statements about what was not technically possible.
The title covers a designer who scripts and an engineer with taste. A one-way video screen finds out which.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async, alongside a portfolio. Enough to establish what they built, test their technical depth, and check how they take feedback.
How do I screen a role this broad?
Decide first whether you need prototyping or production capability, and weight the technical questions accordingly. The same screen answers both, but you must know which you are hiring for.
Evaluating answers
What is the strongest signal when screening this role?
Something they built that people used, and what broke. Technologists with real experience have both. Anyone whose work is installations that ran once has prototyped rather than shipped.
How do I judge their technical depth?
Ask what they built without help. Real answers name the language and what was hard. Anyone whose work always involved an engineer doing the difficult parts is a designer who prototypes.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
