The questions
- What roles are you hiring — or about to hire? Job titles as you actually post them, and how many seats, if you know.
- What must a new hire be able to do on day one? The tasks, not the traits: the ticket they should close, the machine they should run, the record they should read.
- What tools should they already know? The exact stack — the PLC family on your floor, the cloud on your contract, the software on your desk. Named tools become named training.
- What do applicants most often lack? The gap you keep interviewing into. That answer, more than any other, writes our curriculum.
- What would you accept as proof? A portfolio artefact, a simulation record, a vendor assessment, a supervised build — tell us what evidence would make you take a tour-trained candidate seriously.
- Where and when? Town, site, and the hiring window you are working toward, so a cohort can be timed to land inside it.
How to answer
There is no live form behind this page, and we will not pretend otherwise. Write to events@builderspace.tech with the subject line Employer Needs and your answers in any order — a paragraph per question is plenty. A human steward reads every reply; employer conversations are held by humans, in writing.
Joining this intake is not a purchase and not a partnership. Nothing here obliges you to interview or hire anyone, and BuilderSpace names no company as a partner, sponsor, or employer match until that company has agreed in writing. What your answers do is steer real training toward real work — and when a cohort trains toward your stated needs, we will tell you, and the conversation about candidates can start from evidence.
What happens to the answers
Answers are aggregated into the training targets for each tour region — the same employer-needs pass that shapes the Louisiana strands and the robotics package, where the Lab's research (LAB-009, LAB-010, LAB-011) cross-checks what postings actually ask for against what employers say here. Individual company details stay in the steward's correspondence, not on public pages.