職種・勤務地・キーワードで探す
条件を変える
データエンジニアの求人509件応募資格・募集要項・仕事内容を見る
Data Engineer ー AI-Era Corporate Data Infrastructure
- 給与
- 記載なし
- 勤務地
- フルリモート(国内)
- 休日
- Public holidays: You take the Vietnamese public holidays (Tet, Hung Kings' Festival, 30 April, 1 May, 2 September), not the Japanese calendar
- 雇用形態
- 正社員
どんな仕事かAIによる生成
Design and build data infrastructure for SalesNow's corporate data platform, collecting, integrating, and verifying company data from multiple sources. The role covers data pipelines, data quality, orchestration, and delivery of structured corporate data to products, customer workflows, and AI systems.
この求人に応募
応募資格
必須
- 2+ years of professional data engineering experience, building and maintaining production data pipelines (not academic projects or PoCs that never shipped)
- Strong Python skills: you write clean, testable pipeline code
- Strong SQL skills: complex queries, window functions, and query optimization
- Experience with at least one orchestration tool: Airflow, Dagster, Prefect, or equivalent
- Experience with relational databases at scale. PostgreSQL preferred; MySQL or similar is acceptable if you are ready to learn
- Professional working proficiency in English
歓迎
- Experience with Elasticsearch or OpenSearch at scale
- dbt experience
- Web scraping or large-scale data collection systems
- Experience with data quality frameworks and monitoring
- AWS experience (S3, Lambda, ECS, RDS, etc.)
- RAG pipeline or vector database experience
- Experience processing 1M+ records per day
- Japanese language ability (JLPT N3 or above). Not required, but it lets you work more closely with business teams and widens your career options within the company
求める人物像
- You share SalesNow's mission 「誰もが活躍できる仕組みをつくる。」 (Create systems where everyone can thrive) and our values (AI Native, Kotoshikou (purpose-driven), and Highest Quality), and you are determined to make full use of AI
- You enjoy moving fast. Even as things change, you start from the purpose, find the problem, and see it through to a solution
- You work with your team and customers with integrity and ownership
- You care about data quality and protect it with systems, not manual checks alone
- You verify AI output against evidence before adopting it
- You can explain your design decisions, including their cost, to teammates across languages
応募について
- No Japanese required.
使用ツール
募集要項最終確認 11/17
- 職種
- データエンジニア
- 雇用形態
- Full-time, fully remote. You are employed through our Employer of Record (EOR) partner in Vietnam under a labor contract with full local benefits under Vietnamese law. This is not a contractor arrangement.
- 採用区分
- 【海外人材枠】
- 給与
- 記載なし
- 給与の詳細
- USD 1,000 – 2,500 per month, gross (before personal income tax and mandatory insurance) (25 – 62 million VND per month), based on experience and skillsPerformance-based salary reviews every 6 months.
- 勤務地
- 海外Ho Chi Minh City海外Hanoi海外Da Nanganywhere with a stable internet connection
- 転勤
- Scope of changes to work location: none (就業場所の変更の範囲:無し)
- 働き方
- 100% remote. Work from Ho Chi Minh City, Hanoi, Da Nang, or anywhere with a stable internet connectionWork style: Fully remote
- 勤務時間
- Work hours: 10:00-19:00 Japan time, which is 8:00-17:00 Vietnam time
- 休日・休暇
- Public holidays: You take the Vietnamese public holidays (Tet, Hung Kings' Festival, 30 April, 1 May, 2 September), not the Japanese calendarPaid leave: Per Vietnamese labor law
- 福利厚生
- AI tools: spending averages more than USD 600 per person per month (company-paid)Hardware: MacBook provided
- 業務の変更の範囲
- yes
- 就業場所の変更の範囲
- none
- 経験年数
- 2年以上
- 選考の流れ
- 1. Application review (resume + brief answers to 3 technical questions)2. One-day selection event, completed in a single day: a data pipeline exercise on a realistic scenario (2-3 hours), a technical interview (60 min) covering your past work and system design, and a culture fit conversation with the engineering lead (30 min)3. OfferTimeline: 2-3 weeks from application to offer
- 選考期間
- Timeline: 2-3 weeks from application to offer
- 掲載日
- 2026/06/30 13:22(141日前)
- 最終確認
- 2026/11/17 03:41(1日前)
仕事内容
Why This Role Exists
- The era when revenue grew in proportion to headcount is over. More of the value one person creates now comes from working together with AI, and AI can only support good decisions when it works on accurate data about each company. Building that data is the job.
- A large part of this data never appears on the web at all: it comes from offline collection by tens of thousands of researchers and our own in-house team, and from contributions by users of our own media. Resolving a single company identity out of sources like these, rather than out of a public dataset, is the engineering problem you take on here. SalesNow is approaching Series B, and we have set a goal to grow ARR per employee tenfold in three years, starting from November 2025. That goal only works if the data is right, which puts data engineering at the center of how this company grows. We are hiring data engineers who design how corporate data is collected, integrated, and verified, and who make it usable by both people and AI.
The team in Vietnam
- Three Vietnamese members already work with us, and we plan to hire five to ten more. You join a cross-language workflow that already runs, and you help shape how the Vietnam team works as it grows.
What You Will Build
- Company profiles that combine company overview, job postings, IR, services, technologies and tools in use, advertising, organizations and departments, and contact details, matched down to branch level with our own JC code. You decide how these sources merge so each company ends up with exactly one profile
- Signals that capture company moves, such as hiring increases, funding rounds, new offices, overseas expansion, downward earnings revisions, and paused job postings. Sales teams use these signals to decide which companies to approach and when. You design the validation checks that make those signals reliable enough to act on
- Airflow (MWAA) DAGs for our job-posting sources, where you decide how anomalies are detected, how runs recover, and what "collected correctly" means for each source
- A Databricks and Delta Lake platform in three layers (raw, cleansed, serving), with job definitions in Terraform. Where a record is cleaned, and what is allowed into the serving layer, are your design calls
- Data delivered through the SalesNow web app, Salesforce and HubSpot integrations, the Data API, SalesNow MCP (used directly from AI agents such as Claude and Cursor), and AI implementation projects for customers. A schema decision you make shows up both in a customer's CRM and in the answers an AI agent gives
Data collection and ingestion
- Design and implement large-scale web scraping systems that reliably extract structured data from many heterogeneous sources
- Build API integration pipelines for partner data feeds, with schema validation and anomaly detection
- Architect real-time ingestion pipelines for daily updates with sub-minute latency targets
Data transformation and quality
- Build and maintain dbt models that transform raw data into the unified SalesNow schema
- Define data quality SLAs (accuracy, completeness, freshness) and build monitoring dashboards that alert before customers notice
- Implement entity resolution and deduplication at scale: matching company records across sources with different formats, naming conventions, and identifiers
Infrastructure and orchestration
- Orchestrate complex Airflow DAGs across collection, transformation, enrichment, and delivery
- Optimize PostgreSQL and Elasticsearch / OpenSearch clusters for 8 billion records with millisecond query response
- Design fault-tolerant pipelines that recover automatically from failures, with clear observability at every stage
AI pipeline integration
- Feed structured data into RAG pipelines and AI agent systems via SalesNow MCP
- Build data delivery layers that AI agents query in real time for enterprise customer workflows
- Work with Amazon Bedrock, Claude, and Gemini to improve how AI systems use structured corporate data
Problems we are working on now
- Decide whether a job posting is still open. Closure-detection logic is split across three systems, and behavior differs by source. Some sources do not show closure status on their listing pages, so closing postings by diff can wrongly close them when a crawl misses a page. For each source, you weigh the risk of marking an active posting as closed against the risk of leaving an expired posting open
- Design the process that collects every company's website information and keeps tracking changes, so company overviews and service information stay current
Verifying our own data against evidence
- When we had AI independently verify our logic for inferring the client company behind freelance job postings, only 12 of 100 cases could be identified with confirmed evidence. We revised the logic so that cases without enough evidence are marked "cannot identify." Here you are expected to question the data, including the output of your own pipelines, and when the evidence falls short, you have the authority to change the logic.
Scope of duties
- Scope of changes to the duties you will perform: yes (従事すべき業務の変更の範囲:有り)
How We Work with AI
- Everyone can use Claude and Gemini, and we also use Codex. You choose the model that fits each task
- We ask multiple LLMs to review our work, and people check the evidence and decide what to adopt. For data checks, we use LLM as a Judge with criteria that people set. CodeRabbit runs a first review on pull requests
- Instructions written for AI go through pull request review, the same as code, so prompts and agents are engineered with the same rigor as production pipelines. Deliverables are managed on GitHub
- Once the goal and budget are agreed, the person in charge decides how to proceed, where to use AI, and which tools to use. For data collection, you also own what each record costs to obtain, and every pipeline you design is judged on both accuracy and unit cost
- Every role is expected to redesign its own work with AI. Our leadership team writes code too, so you discuss technical trade-offs with people who build
- Across the company, 2,229 pull requests were merged in the 30 days up to 12 September 2026. At that pace, you judge AI-assisted pipeline changes against real data, failure modes, and operating costs
Tech Stack
- Languages: Python (FastAPI), SQL, Scala
- Data transformation: dbt
- Orchestration: Airflow (MWAA)
- Data processing: Databricks (Spark / Delta Lake), Scrapy
- Infrastructure as code: Terraform
- Databases: PostgreSQL, Elasticsearch, OpenSearch
- Cloud: AWS (primary), Vercel
- AI/ML: Amazon Bedrock, Claude, Gemini
- Development tools: Claude Code, Codex, Cursor, GitHub Copilot, CodeRabbit
- CI/CD: GitHub Actions
- Communication: Slack, GitHub, Notion
Working Across Languages
- No Japanese required. English is the working language for engineering: code, pull requests, technical documents, and standups
- Work comes with a PRD. Both sides agree on the requirements and the deadline before you start, so you spend your time on design and code
- GitHub, Notion, and Slack are translated. Pull requests, documents, and daily discussions all pass through translation, so you follow every discussion without Japanese
- Company-paid AI translation. Members who do not speak Japanese discuss work with Japanese colleagues through AI simultaneous interpretation, and interviews run the same way
この求人は、株式会社SalesNowの採用ページの内容をAIが読み取って整理したものです。応募の前に採用ページの原文を確かめてください。データの集め方企業サイト
募集元の採用ページから応募できます
応募は株式会社SalesNowの採用ページで受け付けています。このページは採用ページの掲載内容をもとに構成しているため、最新の応募条件は募集元でご確認ください。
この求人と近い条件で探す数字はリンク先ページの掲載件数
応募資格の語から探す
- データエンジニア509
- データパイプライン409
- Python6,040
- SQL3,040
- Apache Airflow137
- リレーショナルデータベース725
- PostgreSQL1,399
- MySQL1,613
- 英語19,944
- Elasticsearch403
- OpenSearch145
- dbt298
- AWS7,520
- Amazon S3562
- AWS Lambda616
- Amazon Elastic Container Service652
- Amazon RDS487
- 検索拡張生成(RAG)679
- ベクトルデータベース109
- 日本語9,396
この職種で探す
- データエンジニア509
- テック17,370
- AIエンジニア523
- データサイエンティスト332
- データアナリスト323