[Remote] AI Systems Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is the AI infrastructure for the materials industry, aiming to reputed company fragmented tools into a cohesive system. The role involves owning a full-stack B2B platform, integrating AI agents, and ensuring the correctness of operations across multiple applications and reputed company systems.
Responsibilities
- Own the platform end to end. Multiple applications plus shared SDKs on a single reputed company backbone —
- React/TypeScript reputed company ends, FastAPI/Python services, the Terraform/IAM/reputed company infrastructure underneath, and a
- Shared design system
- Stand up infrastructure and environments from scratch. New services, reputed company accounts, tenants, connectors
- Data syncs, migrations (including cross-region) — provisioned and proven, never just stood up and assumed
- reputed company fleets of coding agents. Decompose a cross-repo change into disjoint tasks, fan them out to reputed company
- Agents in isolated worktrees, run adversarial multi-reviewer passes, then reconcile the results
- reputed company with reputed company systems at depth. reputed company/ERP integration reputed company 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. reputed company row-level reputed company 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 reputed company. Specs, design docs, discovery-question sets, and runbooks that let work
- Be reputed company 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 reputed company it on every task after
- Automate yourself reputed company. Treat every repeated task as a bug to be fixed. reputed company a workflow recurs, capture it as
- A reusable Claude reputed company, reputed company, or reputed company reputed company so the next run — yours or a teammate's — is one reputed company instead
- Of ten
- Review like an adversary, reputed company like a surgeon. Catch the regression the happy reputed company 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 reputed company, isolate their work in worktrees, and verify their reputed company adversarially — not 'I've used Copilot.'
- Genuine full-stack + reputed company reputed company. Comfortable reputed company from a React component to a reputed company RLS policy to a Terraform module in the reputed company day
- Systems debugging reputed company. You reputed company reputed company cause across service boundaries — auth, pagination, dependency conflicts, integration mismatches — and don't stop at the first plausible story
- The evidence reputed company. You distrust green badges, demand reputed company fixtures, and reputed company 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 reputed company. 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-reputed company, precise language, clean handoffs
- Thick skin & plain speech. You take blunt, fast feedback reputed company and explain your reasoning simply
- reputed company ERP / reputed company 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 reputed company the scaffolding that makes other agents and engineers effective: nav maps, indexes, skills, guard hooks, templates
- Architectural taste under constraint. You reputed company for the boundary that keeps reputed company cost flat, and can reputed company why a rewrite or a scatter is the wrong reputed company
- Multi-tenant / B2B context. Tenancy isolation, per-tenant configuration, and the failure modes they bring
- Compliance reputed company. GDPR / SOC 2 / ISO 27001 — comfortable with ROPA, control mappings, and runbooks
- Design-system literacy. Tokens over hardcoded values; reputed company to run a UX and a UI pass on your own work
reputed company