Note: The job is a remote job and is open to candidates in USA. Vinmar International is the parent company of Vailent, which provides AI infrastructure for the materials industry. The AI Systems Engineer will be responsible for owning the entire platform, integrating multiple applications, and ensuring the effective orchestration of AI agents.
Responsibilities
- Own the platform end to end. Multiple applications plus shared SDKs on a single cloud backbone —
- React/TypeScript front ends, FastAPI/Python services, the Terraform/IAM/ECS infrastructure underneath, and a
- Shared design system
- Stand up infrastructure and environments from scratch. New services, cloud accounts, tenants, connectors
- Data syncs, migrations (including cross-region) — provisioned and proven, never just stood up and assumed
- Direct fleets of coding agents. Decompose a cross-repo change into disjoint tasks, fan them out to parallel
- Agents in isolated worktrees, run adversarial multi-reviewer passes, then reconcile the results
- Integrate with enterprise systems at depth. SAP/ERP integration via RFC/BAPI — reading and where
- Necessary authoring ABAP, reverse-engineering business rules, handling sales-order and customer-master flows
- Currency/unit/sales-area mapping, and idempotent event sync
- Architect multi-tenant data. Postgres row-level security as the tenant-isolation core, JSONB-backed
- Tenant-extensible capability platforms (custom fields, validation, masking), careful migrations, and a graph
- Database where it fits
- Ship at volume without losing coherence. Multiple PRs across multiple repos in a working session, CI green
- Deployed and verified — while keeping the design clean
- Author the thinking, not just the code. Specs, design docs, discovery-question sets, and runbooks that let work
- Be understood and resumed by others
- Build the tooling that makes AI effective here. Per-codebase navigation maps, documentation indexes, guard
- Hooks, and custom skills — invest in making agents good at this codebase, then reap it on every task after
- Automate yourself forward. Treat every repeated task as a bug to be fixed. When a workflow recurs, capture it as
- A reusable Claude skill, hook, or slash command so the next run — yours or a teammate's — is one step instead
- Of ten
- Review like an adversary, deploy like a surgeon. Catch the regression the happy path missed, separate “it
- Renders” from “the data is correct,” refute false blockers, and touch shared state only with a reason and a green
- Light
Skills
- Fluent AI orchestration. You already run agents in parallel, isolate their work in worktrees, and verify their output adversarially — not 'I've used Copilot.'
- Genuine full-stack + infra range. Comfortable going from a React component to a Postgres RLS policy to a Terraform module in the same day
- Systems debugging instinct. You chase root cause across service boundaries — auth, pagination, dependency conflicts, integration mismatches — and don't stop at the first plausible story
- The evidence reflex. You distrust green badges, demand real fixtures, and prove things with a working screenshot, a read-back record, or a live payload
- Self-correction. You can describe a time you reversed your own confident conclusion because the evidence said so
- An automation reflex. You instinctively turn recurring work into reusable Claude skills, hooks, and commands — raising your own efficiency floor instead of re-doing toil
- Operating discipline. Read-only until authorized, copy proven patterns, enhance-in-place, precise language, clean handoffs
- Thick skin & plain speech. You take blunt, fast feedback well and explain your reasoning simply
- Enterprise ERP / SAP depth. RFC/BAPI, ABAP, customer & order master data — or the nerve to reverse-engineer a customer's system to that depth
- Tooling-builder streak. You've built the scaffolding that makes other agents and engineers effective: nav maps, indexes, skills, guard hooks, templates
- Architectural taste under constraint. You reach for the boundary that keeps future cost flat, and can name why a rewrite or a scatter is the wrong move
- Multi-tenant / B2B context. Tenancy isolation, per-tenant configuration, and the failure modes they bring
- Compliance fluency. GDPR / SOC 2 / ISO 27001 — comfortable with ROPA, control mappings, and runbooks
- Design-system literacy. Tokens over hardcoded values; able to run a UX and a UI pass on your own work
Company Overview
Company H1B Sponsorship