Careers

Builders who communicate

Customer conversations · Written alignment · Honest demos

Talk to customers. Then argue about why before you fall in love with how.

You’ll be in workshops, demos, and the occasional awkward Slack thread. We want people who can listen without turning into a buzzword fountain, write down what got decided, and show up when the news is bad.

Customers hear you clearly

You recap calls, spell out tradeoffs in normal words, and ask “did we get that right?” Silence feels polite until scope explodes.

Why before how

Figure out the outcome—minutes saved, money not lost, auditors satisfied—then pick tools. Not the reverse.

Demos are a conversation

Show something working, ask what would make them stop trusting it, adjust. Pretty decks that lie are worse than ugly code that doesn’t.

Write it down

If it isn’t in email or docs with the client copied, it didn’t happen. Future-you—and their new hire six months out—will thank you.

Applying? Send something that proves you can talk to humans: a recap you wrote, a workshop plan, a war story about a scope fight you didn’t walk away from. A list of frameworks isn’t a conversation.

careers@vytrixlabs.com

Non-optional skill

You will talk to customers (yes, even “IC” engineers)

Demos, design research, legal threads—everyone represents the work sometimes. If that sounds like a bug, we’re not your place. If it sounds like part of the craft, you’ll like how we coach it.

Actually listen

Ask what “good” looks like on their floor or in their spreadsheet, then read it back. Saves forty emails later.

Same story, different room

Legal needs one vocabulary, the line lead another. You don’t perform intelligence; you translate.

Bad news early

Week-two problems are fixable. Week-ten surprises torch budgets. Say the thing, offer a next step.

Recap like a grown-up

Short note after calls: decided, open, owners. Memory is a terrible database.

Run a meeting that ends

Agenda, outcomes, pull quiet people in, kill rabbit holes that don’t ship anything.

Train people you’d hire

Customer engineers aren’t the enemy. Patience on handoff is how we get referenced.

Open roles

Roles we're actively recruiting

Each card has a “with customers” block on purpose. Coding and clarity aren’t two jobs; they’re two halves of the same week.

Applied AI / ML Engineer

Full-time · Remote-hybrid (US / EU overlap)

Why we need this

Models are rarely the whole product. We need people who can pair retrieval, evaluation, and guardrails with honest latency and cost budgets.

With customers (expected)

Explain model limits, data needs, and failure modes to non-ML stakeholders before they commit in a meeting.
Join sprint reviews; capture client feedback on false positives/negatives and turn it into backlog, not defensiveness.
Co-write the “what we measured and what we won’t claim” section of readouts so trust scales.

Responsibilities

Design and ship ML features inside end-to-end slices—not notebooks that stop at accuracy.
Own eval harnesses, regression tests, and failure modes for production-ish loads.
Collaborate with integration engineers on APIs, batch vs stream, and human-in-the-loop flows.

You might be a fit if

You reach for baselines before transformers.
You’ve shipped something users actually hit, not only Kaggle-shaped data.
You write the doc you wish you’d had six months ago—and you’re willing to read it aloud to a client.

Nice to have

· Industrial or regulated-domain experience
· Edge inference experience
· Open-source contributions

Apply for this role

Full-Stack & Integration Engineer (Nexus)

Full-time · Remote-hybrid

Why we need this

Most “AI projects” die in queues, webhooks, and idempotency. Nexus is where stacks become one system.

With customers (expected)

Facilitate integration workshops with client IT and vendors; end with a written API/ownership matrix.
Translate “the system is slow” into concrete traces and next steps the customer can verify.
Send same-day recaps after working sessions so ops teams aren’t guessing what changed.

Responsibilities

Build services, events, and APIs that connect data, models, and UIs reliably.
Own contract design with partners—versioning, retries, dead-letter handling.
Profile paths that cross cloud, on-prem, and occasional mainframe-shaped systems.

You might be a fit if

You’ve debugged a bug that only happened under production concurrency.
You like making the boring parts—logging, tracing, config—first-class.
You stay calm when a client says production is down and you need both empathy and a checklist.

Nice to have

· Kafka / event-driven patterns
· Web3 or attestation flows where relevant
· Terraform or similar

Apply for this role

Edge & IoT Engineer (Sense)

Full-time or contract

Why we need this

The floor has signal. We need engineers who respect firmware, time sync, and certificate rotation as much as cloud dashboards.

With customers (expected)

Spend time on-site or in live calls with maintenance and OT leads—earn credibility before pushing changes.
Explain certificate rotations and failover in language that doesn’t scare the floor.
Document field procedures with screenshots and checklists the customer’s team will actually run.

Responsibilities

Prototype and harden gateways, MQTT/OPC-UA paths, and edge buffering strategies.
Partner with vendors and client IT on OT/IT boundaries without waving hands.
Ship observability that works when the network is hostile.

You might be a fit if

You’ve touched real hardware in anger and kindness.
You document pinouts and topic schemas like your future self is on call.
You treat operators as experts in their environment, not obstacles to your design.

Nice to have

· Rust or embedded C
· Time-series stores
· Field deployment experience

Apply for this role

Simulation & Digital Twin Engineer (Sim)

Full-time · Remote-hybrid

Why we need this

Twins only matter if decisions change. We build scenarios operators and execs can replay—not vanity meshes.

With customers (expected)

Run scenario sessions with mixed audiences—execs and operators—and keep one shared vocabulary.
Solicit blunt feedback when a twin “doesn’t feel real”; prioritize legibility over dazzle.
Package demo narratives so customer champions can rerun them without you in the room.

Responsibilities

Integrate 3D/state pipelines with scenario controls and metrics.
Work with domain experts to define fidelity “good enough” for a capex or ops decision.
Ship paths from twin back to Nexus/Core for alerts and workflows.

You might be a fit if

You balance visual clarity with performance on real GPUs and browsers.
You’ve shipped something someone rehearsed a decision on—not only a viewer.
You enjoy teaching 3D navigation without making anyone feel stupid.

Nice to have

· Unity/Unreal or web 3D
· GIS or CAD interchange
· Physics or logistics modeling

Apply for this role

Platform & DevOps (Forge)

Full-time

Why we need this

Demos ship nowhere without environments someone else can run. Forge is delivery, security baselines, and repeatability.

With customers (expected)

Walk client platform teams through release and rollback in plain steps; avoid “just kubectl” moments.
Align on naming, tagging, and access patterns so their audit questions have answers.
Join go-live windows with clear comms: who does what, when, and how we declare success.

Responsibilities

Own CI/CD, environments, secrets, and release checklists for client handoff.
Harden containers and IaC patterns; pair with security reviews early.
Build templates that make “clone and run” true for the next team.

You might be a fit if

You treat prod-like staging as a feature, not a luxury.
You automate toil and leave runbooks for humans when automation can’t.
You can say “no” to unsafe shortcuts while offering a safer path the customer accepts.

Nice to have

· Kubernetes depth
· SOC2-style control familiarity
· Cost observability

Apply for this role

Product Strategist / Engagement Lead

Full-time

Why we need this

Someone has to hold the why, the scope line, and the stakeholder map while engineers execute. That’s this seat.

With customers (expected)

Own weekly rhythm: agendas, recaps, and escalation paths—you’re the default trusted voice in the thread.
Mediate when sponsors and operators disagree; make tradeoffs visible and priced.
Practice radical clarity in SOWs and change requests so invoices match reality.

Responsibilities

Frame problems, success metrics, and sprint boundaries with clients.
Translate operator language into backlog slices the team can ship.
Run demos that surface decisions, not vanity.

You might be a fit if

You’ve sat in both boardrooms and stand-ups without drowning either in jargon.
You write scopes people sign because they’re honest.
You’d rather lose a deal than promise a lie—and you know how to say that kindly.

Nice to have

· B2B or industrial sales engineering background
· Pricing intuition for sprints

Apply for this role

Product Designer (Complex systems)

Full-time or contract

Why we need this

Our UIs sit next to alarms, compliance, and 3D space. We need systems thinkers who still sweat microcopy.

With customers (expected)

Run structured interviews and usability passes with real operators; synthesize findings for the team same week.
Present design options with tradeoffs labeled—speed vs safety vs training burden—so clients choose knowingly.
Partner with customer comms on rollout copy; tone matters when alarms fire at 2 a.m.

Responsibilities

Design flows for expert users under stress—dense data, few mistakes allowed.
Prototype with engineers; ship accessible, keyboard-friendly interfaces.
Partner on spatial and mobile patterns where Sim and Sense meet.

You might be a fit if

Your portfolio shows restraint and clarity, not only brand decks.
You’re comfortable with technical constraints as creative input.
You invite harsh feedback on flows and thank people for it.

Nice to have

· AR/VR UX
· Design systems in code
· Industrial HMI familiarity

Apply for this role

Security & Compliance Engineer

Full-time

Why we need this

We sell to enterprises and regulated stacks. Security is a differentiator, not a gate at the end.

With customers (expected)

Join legal and risk reviews; translate controls into language that doesn’t freeze the build.
Help clients explain our architecture to their auditors—diagrams plus narrative they can reuse.
Practice proportionate urgency: not every finding is a fire drill; every finding gets a paper trail.

Responsibilities

Threat-model slices with the team; turn findings into concrete backlog items.
Advise on IAM, encryption, retention, and audit evidence for handoff.
Stay current on AI-specific risks—prompt injection, data leakage, supply chain.

You might be a fit if

You’d rather prevent an incident than write a postmortem.
You can explain tradeoffs to legal without talking down or hand-waving.
You build trust by being specific, not by being scary.

Nice to have

· Cloud provider security certs
· Experience with HIPAA/SOC2-shaped programs

Apply for this role

Process

How hiring works here

We’re listening for how you explain messy work to someone smart who’s tired—not how many LeetCode problems you’ve memorized.

Intro & voice

We hear how you explain past work to a non-expert and how you’d run a tense scope conversation. Communication judgment shows up immediately.

Show the work

Walk us through something real—code, architecture, or a scope doc—and practice teaching it as you would to a client lead.

Customer-shaped exercise

Short scenario: ambiguous ask, conflicting stakeholders, or a demo gone sideways. We look for clarity, empathy, and concrete next steps—not bluster.

References & alignment

We ask former colleagues how you showed up in client rooms and written threads. We share how we operate and where the role sits in the Matrix.

Offer & onboarding

Ramp includes shadowing customer calls, our recap template, and a first “solo recap” with feedback from a lead.

Perks & ways of working

The practical stuff

Pay we can defend to our own CFO; equity on some roles; contractor rates we don’t have to hide.
Actual coaching on running calls and writing recaps—useful in client work, not HR checkbox training.
Buy the monitor, buy the IDE license. Petty cash fights are a waste of life.
Core overlap hours, otherwise judge the output. Nobody here cares if you did laundry at 2 p.m.
Learning budget when you can explain what you’ll do with it.
Health where we can legally; cash stipend where we can’t.
Calendar blocks so you’re not in seventeen hours of meetings pretending to listen.
You can ping leads without six layers of approval.
Long-tenure folks: real breaks after brutal deliveries. Burned-out heroes help nobody.

FAQ

Quick answers

I’m strong technically but quiet with customers. Is that okay?
If you write clearly and can take feedback on tone, we’ll stretch you. If you want zero client contact ever, pass—we’re too small to hide you in a basement.
How much time is customer-facing?
Depends on the week. Recaps, demos, workshops, Slack. Everyone answers a hard question from a client sometimes; leads carry more of the facilitation weight.
Do you hire outside the US and EU?
Yes when time zones and contracts work. English for written recaps needs to be solid.
Internships?
Sometimes, when someone senior has real bandwidth. Show us you’ve talked to users—even campus club stuff counts.
What if I’m between two roles?
One email is fine; say you’re a hybrid. We’ve hired Nexus+ML and Sim+Forge shapes before.

See how we show up with clients before you apply: About us and Customers.

Email careers