Extract companies from noisy text

Quick Overview

This question evaluates named entity recognition, noisy-text preprocessing, entity disambiguation, and hybrid rule- and model-based pipeline design for extracting organization names from unstructured resumes and web snippets.

Extract companies from noisy text

Role: Data Scientist

Category: Machine Learning

Difficulty: hard

Interview Round: Onsite

You receive messy resume text and scraped web snippets; the task is to extract company names. (a) Design a hybrid system combining rule-based patterns (e.g., legal suffixes, context windows) with a machine-learned NER model; discuss handling of casing, Unicode noise, and misspellings. (b) Explain feature choices or embeddings (e.g., subword, contextual) and how to incorporate a company gazetteer with fuzzy matching while avoiding label leakage. (c) Define evaluation metrics (entity-level precision/recall/F1) and error analysis procedures for acronyms and ambiguous tokens (e.g., Apple vs apple).

Overview: This question evaluates named entity recognition, noisy-text preprocessing, entity disambiguation, and hybrid rule- and model-based pipeline design for extracting organization names from unstructured resumes and web snippets.

|Home/Machine Learning
Oct 13, 2025
hardData ScientistOnsiteMachine Learning
4
0

Extracting Company Names from Noisy Resumes and Web Snippets

Context

You receive messy resume text (PDF-to-text/OCR, varying casing) and scraped web snippets (boilerplate, menus, ads). Your goal is to extract company names (organizations) accurately under noise such as Unicode artifacts, misspellings, acronyms, and ambiguous tokens (e.g., Apple vs apple).

Tasks

(a) Design a hybrid system that combines rule-based patterns (e.g., legal suffixes and context windows) with a machine-learned NER model. Describe the end-to-end pipeline and how you will handle casing, Unicode noise, and misspellings.

(b) Explain feature choices or embeddings (e.g., subword, contextual) and how to incorporate a company gazetteer with fuzzy matching while avoiding label leakage.

(c) Define evaluation metrics (entity-level precision, recall, F1) and an error analysis plan, with special attention to acronyms and ambiguous tokens.

Loading comments...