> Markdown version of [/jobs/ext/4195458-forward-deployed-engineer-i](https://www.wearedevelopers.com/jobs/ext/4195458-forward-deployed-engineer-i). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Forward Deployed Engineer I - **Company:** SAYARI LLC - **Location:** United States (Remote available) - **Experience:** Experienced - **Salary:** $160,000.0 - $180,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Airflow, Amazon Web Services, Big Data, BigQuery, System Configuration, Data Validation, Data Integration, Data Systems, Cursor, Query Languages, Python (Programming Language), SQL Databases, Systems Integration, Tableau (Software), Parquet, Data Processing, Large Language Models, Snowflake, Apache Spark, Pandas, Integration Tests, Kubernetes, Claude, Entity Resolution, Restful APIs, Looker Analytics, Data Pipelines, Docker, Web Api - **Published:** October 26, 2026 - **Apply:** https://www.builtincolorado.com/job/forward-deployed-engineer-i-remote-us/11851964?handler=ApplyRedirect ## About the Role Required * 3 to 5 years in a client-facing technical role (forward deployed engineering, sales engineering, technical delivery, or technical consulting). * Production Python, including the data manipulation ecosystem (Pandas). * Deep SQL: writing and optimizing complex queries. * Hands-on experience integrating, testing, and supporting REST APIs. * Large-scale data processing with Spark, BigQuery, or Snowflake, and pipeline orchestration with Airflow or similar. * Working knowledge of AWS or GCP. * AI-assisted coding tools (Cursor, Claude, or similar) as a daily part of how you work. * Strong written and verbal communication. You explain technical work clearly to engineers, analysts, and senior stakeholders. * Problem solving in ambiguity, and fast uptake of new technologies and tools. * Bachelor's or Master's degree in a technical field. Desired * Building with LLM APIs for analytical or automation tasks. * Containers (Docker, Kubernetes) and cloud deployment patterns. * BI and dashboarding tools (Looker, Tableau, Metabase). * Graph data technologies and their query languages. * Exposure to ML, NLP, or entity resolution. * Experience in high-stakes domains: AML and financial crime, supply chain risk, or national security. How You Work You are self-directed. You do not need someone to define every step. You spot gaps, ask the right questions, flag tradeoffs, and execute. You hold a high bar on output quality because the work you hand off represents Sayari to the customer. You take full accountability for what you deliver. ## Description Sayari's customers run risk screening, graph analytics and investigation workflows, and data integrations (APIs and feeds) on the Commercial World Model. Those deployments have to work on day one and keep working. As a Forward Deployed Engineer I, you own that outcome. You scope the problem with the customer, prove it technically, ship it, and keep the account healthy after go-live. The same engineer scopes the work and delivers it. This is not a ticket queue. You receive direction, not a script. You work across a portfolio of accounts rather than embedding in one, so the role rewards engineers who move fast, document as they go, and leave every deployment in a state another engineer can pick up. Opportunity to contribute to Sayari's agentic platform. What You'll Do * Scope and prove: run technical scoping and evaluation with customer teams, and confirm Sayari fits the workflow before delivery starts. * Implement: deploy risk screening, graph analytics and investigation workflows, and data integrations (APIs and feeds). Write production Python and SQL to do it. * Deliver data: execute bulk data cuts and formatted data products (Parquet, CSV), set up and support API endpoints, and onboard customer pipelines: environment setup, data validation, integration testing. * Keep deployments healthy: monitor usage and pipeline status, build dashboards that give customers and internal teams clear visibility, and resolve issues before they become churn risk. * Build the playbook: follow and improve delivery playbooks and SOPs. Document your work clearly enough that another engineer can pick it up without a handoff call. * Feed the product: bring recurring customer needs and field findings back to core engineering.