Careers / People, by invitation
If Sentimech gets in touch, bring your curiosity, your questions and a piece of work you understand.
Prepare, not perform.
This is a preparation guide for a possible conversation, not a list of vacancies or a prescribed interview process. Confirm the actual format and expectations with the person who contacts you.
Headquartered in Toronto, Ontario, Canada. Operating in Tokyo, Hong Kong, Dubai, Tel Aviv, and London. Our current focus is enterprise Super Intelligence harnesses; humanoid field deployment is the future direction.
01 / Before the conversation
Pick something you can explain deeply. Frame the problem, separate your contribution from the team’s, and describe an alternative you rejected. Bring a non-confidential sketch or example, not a polished claim without evidence.
Clarify the objective and constraints before solving. Put assumptions on the page, compare a small number of approaches, and explain what would change your mind. A useful question is better than a concealed uncertainty.
Read unfamiliar code, a schematic or a process diagram. Reproduce a small issue, isolate the cause, then explain how you would validate a change. The point is a traceable line from observation to evidence.
Read the current enterprise-harness story and the future field-robotics direction. Ask about the problem, the other disciplines involved and the open questions. Listen to a new constraint and revise your approach explicitly.
Use these suggestions to make a real conversation more useful. Confirm expectations with the person who contacts you; this is not a prescribed interview loop.
02 / Make it concrete
Choose a familiar discipline, then examine the boundary with another. Use these questions to practise making assumptions explicit and explaining what you would test.
A model gives inconsistent results after an interface changes. What would you inspect first? Separate evidence from assumptions, propose the smallest useful test, and explain how you would know whether the issue is in the model or the integration.
A simulated assembly works, but a maintenance task appears inaccessible. Sketch the affected interfaces and list what you would ask mechanical and electrical specialists before changing anything. Describe the limits of what your sketch proves.
Improving one step makes the overall process slower. Draw the handoffs, queues and feedback delays. What observation would help distinguish a local improvement from a system-wide one?
Ask a colleague to add a constraint. Explain what still holds, what breaks, and what you would test next. Clear communication includes being able to revise a plausible first answer.
03 / Optional reading
Choose what interests you. No purchase or completed reading list is expected. These are optional perspectives to discuss, not an ideological test, recruitment syllabus or statement of company positions.
Skip to practicalitiesA / Super Intelligence perspectives
Essays, a company vision and a philosophical argument. Read them alongside one another, not as a shared doctrine.
Consider the tension between hand-built expertise and general methods that benefit from more computation. Where would you test that argument?
A vision of personal empowerment through Super Intelligence. Ask what access, agency and a balance of power would require in practice.
An argument for Super Intelligence’s potential benefits. Separate the desirable outcomes from the technical and institutional assumptions behind them.
A different lens on capability, control and consequences. Which uncertainties would change a decision about deployment?
B / Fiction
Imagined societies are useful places to question power, perception and technology. They are not forecasts or evidence of feasibility.
A prompt to notice the limits of a familiar model. What might your own discipline leave outside its field of view?
The linked Foundation volume is a starting point for the series. Think about prediction, institutions and long time horizons. Where does an aggregate model stop explaining individual choices?
Explore autonomy, coordination and dependence on technical infrastructure. Whose assumptions become the rules of a system?
Consider how digital spaces, language and physical institutions interact. A vivid imagined interface is a starting point for questions, not a specification.
A wide field for thinking about abundance, agency and intervention. Choose a story that interests you; there is no required reading order here.
C / Building & explaining
Business perspectives and practical references. Borrow a useful question without treating an author’s position as a company policy.
An argument about creating something new. Discuss the problem a venture should solve, and what evidence would challenge its thesis.
A useful lens for boundaries, stocks, flows and feedback. Try mapping a delay or unintended consequence in a system you already know.
An accessible route into the behaviour of physical structures. Use it to practice explaining a load path or a failure mode without hiding behind jargon.
Explore where a system should simplify, where services should separate, and how reliability, security and operations shape architectural decisions.
04 / Practicalities
When contacted, confirm the format, time zone and any tools or material requested. Ask about accessibility needs or adjustments early, and avoid sharing confidential work.
Keep the essentials in view as you prepare.
Clarify what is being asked before choosing an approach. State an assumption when information is missing.
Explain an alternative you considered, the tradeoff you made and a small test that could disprove your answer.
Ask about the actual work, its constraints and the people involved. A conversation should help both sides understand the fit.
This page collects no candidate information and does not accept applications. Your checklist marks stay in this page only.
Explore the engineering disciplines