Applied AI Engineer

Velixo Intelligence is our MCP-based gateway that lets finance teams query their ERP in natural language and perform governed writebacks from Claude, ChatGPT, and Copilot. Reads run through GIQL, our query language. Writes go through the ERP's own screen APIs so that every permission, validation, and audit rule still applies. 

It launched in public preview this year. Usage is growing, the surface area is expanding, and our understanding of the unit economics has not kept pace. That gap is the reason this role exists. 

Evaluation 

• →

  Build and maintain regression suites for GIQL query generation, writeback correctness, and tool selection 

• →

  Define what "good" means for each action type and make it measurable 

• →

  Run structured evaluations before every model upgrade or prompt change, and produce a clear ship or no-ship recommendation 

• →

  Track quality over time so we notice degradation before customers do 

Cost engineering 

• →

  Instrument every Gateway action for tokens, cache behavior, model, latency, and tenant 

• →

  Establish and maintain the cost-per-action baseline that the rest of the company plans against 

• →

  Reduce cost through prompt compression, prompt caching, context pruning, and routing work to smaller models where evaluation shows quality holds 

• →

  Identify the expensive tail: which customers, which query shapes, which failure and retry loops 

Model strategy 

• →

  Track new model releases across providers and evaluate them against our workloads rather than published benchmarks 

• →

  Maintain a current view of the price and performance frontier for what we do 

• →

  Recommend when to migrate, when to wait, and when to run models in parallel 

Partnership with Finance 

• →

  Supply the unit cost data behind our credit pricing and plan allowances 

• →

  Model the margin impact of proposed pricing changes alongside our VP Finance 

• →

  Flag when product decisions will move the cost curve before they ship 

You will not own pricing decisions. You will own the numbers those decisions depend on. 

First 90 days 

• →

  Days 1 to 30: Full instrumentation of the Gateway. A dashboard showing cost per action type, per tenant, and per model that the exec team checks weekly. 

• →

  Days 31 to 60: A working evaluation suite covering our highest-volume action types, with a documented baseline. 

• →

  Days 61 to 90: A prioritized cost reduction roadmap with sized estimates, and at least one shipped optimization with measured before-and-after quality. 

• Substantial experience building on LLM APIs in production, not in demos or notebooks 

• You have built an eval harness before and can explain why the naive version of it misleads you 

• Hands-on with the current tooling landscape: tracing and observability platforms such as Langfuse, eval frameworks such as promptfoo. You have opinions about which of these earn their keep and which add ceremony without adding signal. 

• Comfortable with token accounting, context window management, and caching strategies 

• Strong analytical instincts and fluency with data. You reach for a query or a notebook before you reach for an opinion. 

• Able to write clearly about tradeoffs for a non-technical audience, because your conclusions will land in board decks and pricing meetings 

• Python or TypeScript proficiency 

• Experience with MCP or other tool-calling frameworks 

• Background in ERP, accounting, or financial systems 

• Prior exposure to usage-based or credit-based pricing models 

• Experience at a small company where you set your own priorities 

Most companies bolt a chat box onto their product and hope. We are building governed, auditable write access to financial systems of record, where a wrong answer has real consequences and a hallucinated journal entry is unacceptable. The evaluation problem here is genuinely hard and genuinely matters. 

You will also have unusual visibility. The numbers you produce will directly shape what we charge and what we build.