Vinmar International

Role Description A customer-facing engineer who lives at the intersection of deployment, integration, and product. You’ll embed directly with our customers — chemicals distributors, polymer producers, elastomer traders — understand their real operational environment, and build the production solutions that make Vailent work inside it. The job isn’t demoing software; it’s owning the outcome. The gravel road, not the superhighway. FDEs build the rough path that proves what’s possible in a specific customer’s environment. Core product engineers then generalize it. That means you need to move fast, ship production-quality code, and bring back what you learn — because the patterns you surface in the field become the features that ship to everyone. Our customers run complex enterprise stacks: SAP/ERP systems, legacy CRMs, bespoke flat-file workflows built over decades. Integrating Vailent into that environment requires engineering depth and customer trust in equal measure. You’ll be the person who earns both. What You’ll Do - Embed with customers and own the outcome. Sit alongside customer teams — in their Slack, their systems, their reality — to understand their workflows, constraints, and data before touching a line of code. Translate what you hear into a concrete technical plan, then execute it. - Run technical discovery before every engagement. Map the customer’s existing stack: SAP configuration, CRM schema, data flows, integration points, and business rules. Ask the questions the customer didn’t know mattered. Define scope before scope defines you. - Build and deploy production solutions, not prototypes. Stand up integrations, data pipelines, custom workflows, and tenant configurations that run in live environments. “It works on my machine” is not a deliverable. - Own the full integration lifecycle. From first API call to stable sync: SAP/ERP data flows, CRM connections, customer-master and order-master mapping, idempotent event handling, and the edge cases that only appear in production with real data. - Be the primary technical relationship. Serve as the customer’s technical point of contact across the engagement — from onboarding through steady state. Run technical calls, explain architectural decisions to non-technical stakeholders, and surface risks before they become incidents. - Support sales in technically complex deals. Join pre-sales conversations to assess feasibility, design proof-of-concept scopes, and give prospective customers the confidence that Vailent can work in their environment. The close and the deployment aren’t separate jobs. - Direct AI agents through customer-specific work. Decompose integration and configuration tasks, fan them out to parallel agents, verify outputs adversarially, and reconcile results — without letting customer data or live-system risk become casualty of throughput. - Close the feedback loop with product and engineering. The patterns, failure modes, and workarounds you discover in the field are the most valuable signal the core team has. Document them, escalate them, and advocate for the generalized fix — not the one-off patch. - Capture and reuse what works. Build deployment runbooks, integration templates, customer onboarding checklists, and Claude skills that make the next engagement faster. Treat every repeated setup task as a bug to be fixed once and inherited forever. - Author the thinking, not just the code. Specs, discovery-question sets, integration design docs, and handoff notes that let the next engineer — or agent — pick up where you left off without a two-hour call. How We Work - Hire for the disposition. The stack is learnable; this isn’t. - Prove it in the real environment. “Done” means demonstrated, not asserted. - Never guess. Verify what’s knowable in the code; ask about what’s a genuine product decision; assume nothing in between. - Diagnose before you touch. “Look into it” means read-only until told to fix — especially on anything live. - Copy what works. If working examples already solve a problem, read the proven pattern and adapt it. - Enhance in place, never fork. Generalize the existing path — add an optional parameter where today is the degenerate case. - Risk isn’t size. Bigger isn’t worse; riskier is. - Build to scale — or name the debt. Ship the agreed slice now, but flag anything that won’t scale as explicit, revisit-able debt. - Own the correction. Verify findings adversarially — a second pass whose job is to refute the first. - Words are a feature. Terminology has precise internal meaning. - Leave a trail. Every engagement ends with a handoff so the next person — human or agent — starts informed. Must have - Customer-facing engineering ownership. You’ve shipped production solutions inside a customer’s environment. - Strong full-stack range. Comfortable moving from a React component to a Postgres integration to a Terraform environment variable. - Enterprise integration instinct. You’ve connected systems that weren’t designed to talk to each other. - Fluent AI orchestration. You already run agents in parallel, isolate their work, and verify outputs adversarially. - Clear, credible communication. You can explain a technical constraint to a commercial director and write a concise integration spec. - Systems debugging instinct. You chase root cause across service boundaries. - The evidence reflex. You distrust green badges and prove things with a working read-back. - Thick skin & plain speech. You take blunt, fast feedback well and give it the same way. Nice to have - Materials industry or adjacent vertical context. Familiarity with how these businesses buy, sell, and move product. - SAP / ERP depth. Confidence to reverse-engineer a customer’s SAP configuration. - Pre-sales or solutions engineering experience. You’ve sat in discovery calls and helped assess feasibility. - Fluency in compliance contexts. You’ve navigated vendor security questionnaires and data access approvals. - Tooling-builder streak. You’ve built deployment runbooks, onboarding checklists, or integration templates. - Multi-tenant / B2B experience. You understand per-tenant configuration and tenancy isolation.

• Embed with customers and own the outcome. Sit alongside customer teams — in their Slack, their systems, their reality — to understand their workflows, constraints, and data before touching a line of code. Translate what you hear into a concrete technical plan, then execute it. • Run technical discovery before every engagement. Map the customer’s existing stack: SAP configuration, CRM schema, data flows, integration points, and business rules. Ask the questions the customer didn’t know mattered. Define scope before scope defines you. • Build and deploy production solutions, not prototypes. Stand up integrations, data pipelines, custom workflows, and tenant configurations that run in live environments. “It works on my machine” is not a deliverable. • Own the full integration lifecycle. From first API call to stable sync: SAP/ERP data flows, CRM connections, customer-master and order-master mapping, idempotent event handling, and the edge cases that only appear in production with real data. • Be the primary technical relationship. Serve as the customer’s technical point of contact across the engagement — from onboarding through steady state. Run technical calls, explain architectural decisions to non-technical stakeholders, and surface risks before they become incidents. • Support sales in technically complex deals. Join pre-sales conversations to assess feasibility, design proof-of-concept scopes, and give prospective customers the confidence that Vailent can work in their environment. The close and the deployment aren’t separate jobs. • Direct AI agents through customer-specific work. Decompose integration and configuration tasks, fan them out to parallel agents, verify outputs adversarially, and reconcile results — without letting customer data or live-system risk become casualty of throughput. • Close the feedback loop with product and engineering. The patterns, failure modes, and workarounds you discover in the field are the most valuable signal the core team has. Document them, escalate them, and advocate for the generalized fix — not the one-off patch. • Capture and reuse what works. Build deployment runbooks, integration templates, customer onboarding checklists, and Claude skills that make the next engagement faster. Treat every repeated setup task as a bug to be fixed once and inherited forever. • Author the thinking, not just the code. Specs, discovery-question sets, integration design docs, and handoff notes that let the next engineer — or agent — pick up where you left off without a two-hour call.

Role Description We are seeking a highly motivated and experienced Senior Sales Manager to drive sales growth, expand our customer base, and strengthen key account relationships within the polymer industry. This individual will play a critical role in executing structured sales strategies, delivering market insights, and supporting customers with value-added solutions. This is a high-impact position requiring strong commercial acumen, deep industry knowledge, and the ability to manage complex customer relationships while delivering consistent sales performance. Qualifications - Bachelor’s degree in Business, Science, or related field (advanced degree preferred) - 5–10+ years of sales experience in the polymer industry (polyolefins, recycled resins, or related materials preferred) - Proven track record of managing a meaningful sales portfolio and delivering revenue growth - Strong experience managing key accounts and building long-term customer relationships - Excellent communication, negotiation, and relationship-building skills - Strong commercial judgment and ability to interpret market trends and data Requirements - Drive revenue growth by expanding existing accounts and developing new customer relationships - Manage the full sales cycle, including ensuring timely payment collection from customers - Develop and implement structured sales and marketing plans to deliver consistent monthly sales performance - Execute account-specific sales programs to ensure stable, predictable product offtake - Build and maintain strong relationships with major customers - Expand customer network to support nationwide sales coverage and long-term growth - Gather real-time market intelligence on pricing, demand, and competitive dynamics - Provide actionable insights to leadership to support pricing and commercial strategy - Maintain up-to-date knowledge of logistics, supply chain conditions, foreign exchange, and banking solutions - Support customers with import planning and commercial decision-making - Track local and pipeline inventory levels - Develop accurate sales forecasts and implement processes to support supply and demand planning - Develop deep understanding of polymer applications and end-use markets - Deliver tailored commercial proposals aligned with customer needs and target segments

• Drive revenue growth by expanding existing accounts and developing new customer relationships • Manage the full sales cycle, including ensuring timely payment collection from customers • Develop and implement structured sales and marketing plans to deliver consistent monthly sales performance • Execute account-specific sales programs to ensure stable, predictable product offtake • Build and maintain strong relationships with major customers • Expand customer network to support nationwide sales coverage and long-term growth • Gather real-time market intelligence on pricing, demand, and competitive dynamics • Provide actionable insights to leadership to support pricing and commercial strategy • Maintain up-to-date knowledge of logistics, supply chain conditions, foreign exchange, and banking solutions • Support customers with import planning and commercial decision-making • Track local and pipeline inventory levels • Develop accurate sales forecasts and implement processes to support supply and demand planning • Develop deep understanding of polymer applications and end-use markets • Deliver tailored commercial proposals aligned with customer needs and target segments

• 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.

Role Description A full-stack platform engineer who can run a multi-app B2B platform end to end — by directing fleets of AI agents and verifying everything in the real environment. You'll own the whole stack: cloud infrastructure, backend, frontend, data, and deep enterprise-ERP integration. The job isn't writing code with AI; it's operating it — decompose, fan out, verify adversarially, ship. One seat doing what's normally three or four. We run a B2B platform spanning roughly ten applications on a shared cloud backbone, with deep integration into customers' enterprise systems (SAP/ERP). This role owns it end to end — from the Terraform and IAM underneath to the React components on top, and the SAP RFC calls in between. The differentiator isn't typing speed. It's the ability to hold an entire platform in your head and conduct AI agents through it without dropping correctness — shipping across many repositories at once while keeping the architecture coherent. AI orchestration here is not a productivity add-on; it's the core multiplier that makes the scope possible. We hire for that fluency, and for the discipline that makes it safe. What You'll Do - 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. How We Work - Hire for the disposition. The stack is learnable; this isn't. - Prove it in the real environment. “Done” means demonstrated, not asserted. - Never guess. Verify what's knowable in the code; ask about what's a genuine product decision; assume nothing in between. - Diagnose before you touch. “Look into it” means read-only until told to fix — especially on anything live. - Copy what works. If working examples already solve a problem, read the proven pattern and adapt it. - Enhance in place, never fork. Generalize the existing path — add an optional parameter where today is the degenerate case. - Risk isn't size. Bigger isn't worse; riskier is. - Build to scale — or name the debt. Ship the agreed slice now, but flag anything that won't scale as explicit, revisit-able debt. - Own the correction. Verify findings adversarially — a second pass whose job is to refute the first. - Words are a feature. Terminology has precise internal meaning. - Leave a trail. Every session ends with a handoff so the next one — human or agent — starts informed. Environment - Frontend — React, TypeScript, Vite, TanStack Query, vitest, a token-based design system, Playwright for verification. - Backend — Python, FastAPI (async), SQLAlchemy, Alembic, Celery, Pydantic; an SNS®SQS event bus with idempotent dedup. - Data — PostgreSQL with row-level security, schema-per-app, JSONB + GIN/GIST, Neo4j (Cypher), pgvector. - Platform / Infra — AWS (ECS Fargate, Aurora, RDS Proxy, Route53, ACM, WAF, CloudFront, IAM/OIDC), Terraform, dual-account, per-branch Docker stacks, gitflow. - Enterprise integration — SAP ECC via RFC/BAPI, ABAP, pyrfc, customer/order master data, additional ERP connectors, M2M auth. - Identity & AI — Auth0 (Organizations, M2M, custom claims), JWT entitlement gating; Claude Code agents, worktrees, skills, hooks, MCP. Must have - Fluent AI orchestration. You already run agents in parallel, isolate their work in worktrees, and verify their output adversarially. - 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. - 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. - 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. Nice to have - Enterprise ERP / SAP depth. RFC/BAPI, ABAP, customer & order master data. - Tooling-builder streak. You've built the scaffolding that makes other agents and engineers effective. - Architectural taste under constraint. You reach for the boundary that keeps future cost flat. - 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.

• Develop and execute a strategic sales plan to grow revenue and profitability across assigned European territories and accounts. • Identify and secure new business opportunities within polymer, rubber, elastomer, and related manufacturing markets. • Manage the full sales cycle from prospecting and qualification through negotiation and contract execution. • Build and maintain relationships with purchasing, technical, R&D, manufacturing, and executive stakeholders. • Promote a portfolio of specialty additives and performance-enhancing solutions for plastics and rubber applications. • Drive growth through both direct sales and distribution channels where applicable. • Manage and expand relationships with existing customers to increase wallet share and long-term retention. • Conduct regular customer visits and business reviews to understand customer needs and uncover new opportunities. • Coordinate commercial activities, forecasts, pricing discussions, and contract renewals. • Resolve customer issues proactively while ensuring a high level of service and responsiveness. • Work closely with suppliers, product managers, and technical specialists to position products effectively. • Support customers with product selection and application discussions. • Monitor market trends, competitive activity, raw material developments, and emerging technologies. • Identify opportunities for new products, market segments, and supplier partnerships. • Develop territory plans, sales forecasts, and opportunity pipelines. • Maintain accurate customer and opportunity records within CRM systems. • Prepare regular reports on sales performance, market intelligence, and business development activities. • Collaborate with leadership to establish pricing strategies and growth initiatives.

• Sales of polymers in the designated territory. • Develop new accounts in accordance with VPA’s growth strategy • Work closely with product management to deliver sales growth and profitability targets. • Track sales activity in VPA’s customer relationship management software. • Drive aggressive sales growth by proactively pursuing new and/or targeted accounts in the assigned region. • Achieve annual sales plan objectives including volume and profitability targets in the assigned region. Initiate actions and pursue contingency plans, as appropriate, to mitigate any expected sales plan short-falls or gaps. • Establish, develop, maintain, and grow relationships with current and prospective customers in the assigned territory to generate new business for VPA’s products. • Make regular telephone calls and in-person visits to existing and prospective customers. Plan and organize both office and travel time to optimize personal time, effectiveness and costs.

• Drive sales growth by proactively pursuing new and/or targeted accounts in the assigned region. • Achieve annual sales plan objectives including volume and MSP profitability targets in the assigned region. Initiate actions and pursue contingency plans, as appropriate, to mitigate any expected sales plan short-falls or gaps. • Establish, develop, maintain, and grow relationships with current and prospective customers in the assigned territory to generate new business for Prime’s sourced products. • Make regular telephone calls and in-person visits to existing and prospective customers. Plan and organize both office and travel time to optimize personal time, effectiveness and costs. • Responsible for accurate company introduction during first visits and prospecting. • Weekly written report - Area Market sentiment, offers-availability, news, requirements, and any other information relevant to our business. • Lead the commercial development within area of responsibility of new products following the growth strategy. • Responsible of Area Forecasting based in sales history. • Performance Polymers monthly forecasting based on project development. • Follow “Claim Management Process” to solve quality and service problems. Make sure AM take ownership and follow up. • Sourcing input by identifying new markets, trends or potential customers. • Work closely with logistics and finance departments to ensure customer expectations are understood and met in the assigned region. • Provide input into developing the annual sales plan and ensure delivery of sales volumes and profitability objectives. • Use tools as provided and work closely with Business Director, Product Manager and Technical Managers to generate sales leads, qualify leads into sales targets, and effectively manage a sales target pipeline that will ensure the company’s sales goals are met and exceeded. • Track and report on competitors’ activities within the assigned region. • Managing his/her territory to maximize inventory turns, minimize freight, finance, storage, demurrage and other logistics costs. • Update job knowledge and skills by participating in technical and business learning opportunities, reading professional publications and maintaining personal networks. • Strict adherence to compliance in accordance with company policies and procedures.

Role Description The Account Manager - Rubber will deliver profitable sales growth and proactively manage, maintain and expand Prime’s rubber and automotive customer base in assigned areas by leading and motivating his/her direct reports to perform. - Drive sales growth by proactively pursuing new and/or targeted accounts in the assigned region. - Achieve annual sales plan objectives including volume and MSP profitability targets in the assigned region. - Initiate actions and pursue contingency plans, as appropriate, to mitigate any expected sales plan short-falls or gaps. - Establish, develop, maintain, and grow relationships with current and prospective customers in the assigned territory to generate new business for Prime’s sourced products. - Make regular telephone calls and in-person visits to existing and prospective customers. - Plan and organize both office and travel time to optimize personal time, effectiveness and costs. - Responsible for accurate company introduction during first visits and prospecting. - Weekly written report - Area Market sentiment, offers-availability, news, requirements, and any other information relevant to our business. - Lead the commercial development within area of responsibility of new products following the growth strategy. - Responsible for Area Forecasting based on sales history. - Performance Polymers monthly forecasting based on project development. - Follow “Claim Management Process” to solve quality and service problems. - Sourcing input by identifying new markets, trends or potential customers. - Work closely with logistics and finance departments to ensure customer expectations are understood and met in the assigned region. - Provide input into developing the annual sales plan and ensure delivery of sales volumes and profitability objectives. - Use tools as provided and work closely with Business Director, Product Manager and Technical Managers to generate sales leads, qualify leads into sales targets, and effectively manage a sales target pipeline that will ensure the company’s sales goals are met and exceeded. - Track and report on competitors’ activities within the assigned region. - Managing his/her territory to maximize inventory turns, minimize freight, finance, storage, demurrage and other logistics costs. - Update job knowledge and skills by participating in technical and business learning opportunities, reading professional publications and maintaining personal networks. - Strict adherence to compliance in accordance with company policies and procedures. Qualifications - Bachelor’s degree, preferably engineering related to rubber. - 10 - 15 years of experience in a similar field. - Fluent in German and English. - Travelling minimum 25% of the time.