arQuon
arQuon

Forward-Deployed Engineer

Chicago, ILOn-siteSeniorFull-time

Posted 2 days ago

The role in short

Embed with enterprise customers to build and deploy production AI integrations, data pipelines, and agents within their sovereign environments.

Build sovereign AI. Shape the future. Accelerate your career.

arQuon builds sovereign enterprise AI that runs inside the customer's own environment, keeping their data, models, and intelligence entirely under their control. arQuon Inc. is headquartered in Chicago, with subsidiaries in Luxembourg, the UK, and India and spun out of QBA Worldwide, with 15+ years of enterprise delivery behind it.

Join arQuon Inc and help create enterprise AI that keeps organizations and their intelligence in control. Let’s build the future of trusted AI together.

Join our team as a Forward-Deployed Engineer

The role

This is arQuon’s core delivery role and our largest hiring group in the Americas. You sit inside a customer’s environment, understand the problem properly, and build what solves it: integrations, pipelines, agents and interfaces on our platform. It suits engineers who have found product work too far from the consequences and consulting too far from the code.

What you will own:

  • Hands-on build and deployment work at an American enterprise account
  • Integrations between arQuon’s platform and the customer’s systems
  • Data pipeline and knowledge-graph work for the deployment you are on
  • Customer workshops, enablement and documentation that outlives you on the account
  • Diagnosis and resolution inside environments with limited external access

What success looks like in twelve months

  • Your deployment in production use, with users who would notice if it stopped
  • Reusable components contributed back to the platform
  • Customer feedback that names you

What you'll bring:

  • 4+ years of software engineering with customer-facing exposure
  • Strong Python; comfortable with APIs, containers and cloud infrastructure
  • Experience integrating with enterprise systems and their realities
  • Clear communication with non-technical stakeholders
  • Willingness to travel across the Americas, typically 25–40%, and authorization to work in the United States

Bonus points for:

  • LLM application, RAG or agentic framework experience
  • Front-end skills (React or similar)
  • Manufacturing, logistics, defense or financial-services domain exposure

Why join us

  • Competitive rewards: Market-aligned base pay, performance bonus and meaningful equity—so you share in the value you help create
  • Comprehensive benefits: Medical, dental and vision coverage, along with a 401(k) plan
  • Real ownership from day one: In a fast-growing company like ours, your ideas matter and your work can reach customers in weeks, not quarters
  • Global collaboration: Work with talented colleagues across Chicago, Luxembourg and Kolkata through a genuine follow-the-sun operating model
  • Continuous growth: Access dedicated support for professional certifications, industry conferences and ongoing learning
  • Visible impact: Help build enterprise AI that gives customers complete control over their data, models and intelligence

arQuon.ai is committed to creating a diverse environment and is proud to be an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, disability, age, veteran status, or any other protected category under applicable law.

Prep for this interview

5 questions likely to come up at arQuon, each matched to a line in this posting.

  1. 1LLMs, RAG and agents
    They wrote: “LLM application, RAG or agentic framework experience”

    A customer wants a chatbot over their internal documents. How do you build it?

    How to answer

    Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.

    1. Collect and clean the documents; handle permissions per user
    2. Split them into chunks, embed, and store with source links
    3. Retrieve, then answer with citations; say “I don't know” when retrieval is weak
    4. Build a test set of real questions with expected answers before launch

    Tip: Spend more time on the data and on testing than on the model.

  2. 2Discovery and scoping
    They wrote: “Clear communication with non-technical stakeholders”

    A senior executive and the hands-on team want different things. How do you handle it?

    How to answer

    Why they ask: Enterprise deployments have several stakeholders. Senior FDEs are expected to align them, not pick a side quietly.

    1. Meet each side to learn what they need and why
    2. Find the shared goal (usually the business metric the executive owns)
    3. Propose a plan that meets that goal and removes the team's biggest pain
    4. Get a written decision so the project doesn't stall later

    Tip: Show that you get both views on the table early and tie the plan to the goal the executive owns.

  3. 3Integrations and APIs
    They wrote: “Integrations between arQuon’s platform and the customer’s systems”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  4. 4Data and SQL
    They wrote: “Data pipeline and knowledge-graph work for the deployment you are on”

    How would you design a daily pipeline that feeds customer data into our product?

    How to answer

    Why they ask: Tests basic data engineering: scheduling, failures, re-runs and monitoring.

    1. Extract with timestamps or change tracking, not full dumps, when possible
    2. Transform in steps you can re-run without creating duplicates
    3. Validate row counts and key fields before loading
    4. Alert a person on failure, with enough detail to fix it

    Tip: Make re-running safe (same input, same result) and say how you'd know it failed.

  5. 5Coding
    They wrote: “4+ years of software engineering with customer-facing exposure”

    Build a small in-memory cache. Then add expiry. Then a size limit.

    How to answer

    Why they ask: Staged exercises show how your code holds up when requirements change mid-interview, like at a customer.

    1. Start with get and set on a dictionary, plus tests
    2. Store an expiry time with each value and check it on read
    3. Track use order and evict the least recently used entry when full
    4. Say what you'd change for many threads or many machines

    Tip: Keep the first version simple and well tested so the next stage is a small change.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

arQuon

On-site

Apply