Team skills intake · POC readiness

POC Readiness Signal

A quick self-assessment before we build the Vantiq proof-of-concept from zero — so we know where the team is strong, and where to line up help before we're mid-build.

A

Background & exposure

Where you're starting from — no wrong answers, this just sets context.

Your name
Optional — leave blank to answer anonymously.
Your role on the team
1. How many POCs or pilot projects have you built from scratch before?
2. Have you used Vantiq before?
If yes — what did you build, and how long ago? If no, just say "None".
3. What other low-code, event-driven, or IoT platforms have you used?
e.g. Node-RED, Mendix, OutSystems, AWS IoT, Azure IoT, Kepware — or "None".
B

Use-case & requirements readiness

Turning a vague business ask into something buildable.

5. Turning a vague business ask into a concrete technical use case
6. Writing user stories, acceptance criteria, or a solution design doc — alone
7. Identifying what data sources/systems a use case needs, before any code is written
C

Vantiq-specific skills

The platform itself.

8. Core concepts — types, events, sources, procedures/VAIL, rules
9. Connecting Vantiq to an external system (REST, MQTT, Kafka, a database, an IoT device)
Which systems, if any?
9a. Creating simulated/mock data sources in Vantiq to test a flow
10. Building a real-time / event-driven flow (reacting to a stream of events, not just CRUD)
11. Deploying a Vantiq app beyond your local sandbox / working across namespaces
12. Debugging when a rule or event flow isn't firing as expected
D

General technical readiness

Skills that matter regardless of platform.

13. API integration (REST/webhooks) in general
13a. Generating realistic dummy/test data — varied values, edge cases, bad records, not just one happy path
13b. Working with real IoT protocols (vs. only ever testing against mocks)
Which protocols, if any?
14. Basic data modeling — designing types/schemas for a new use case
15. Authentication/authorization setup for a new app or integration
16. Writing basic tests or manually validating an end-to-end flow
E

Process & collaboration

17. Have you worked on a project with no existing codebase or template to start from? How did that go?
18. Estimating effort/time for a task you've never done before
19. Given something unfamiliar, would you rather…
F

Open-ended

These usually tell us more than the ratings do.

20. What's the one thing about this POC you're least confident about right now?
21. Last time you got stuck on something similar, what actually got you unstuck?
Docs, a colleague, trial and error, external training…
22. One hour of training or mentoring before this POC starts — what would you want it on?
23. Is there anything about the use case itself (not the tooling) that's still unclear to you?
24. If we had to build test data ourselves instead of using real devices, how comfortable are you doing that?
Answers aren't saved until you submit.
🔒

Admin only

Enter the results PIN to see how the team is tracking.