InterviewDB Experience

Text Rewrite: Replace Words Using a Substitution Dictionary

Interview Experience

Problem

Given a sentence and a dictionary mapping words to their replacements, rewrite the sentence by substituting every occurrence of a dictionary key with its value. Matching is case-insensitive but preserve the original casing pattern (all-caps, title-case, or lowercase) in the output.

python
def text_rewrite(sentence: str, substitutions: dict[str, str]) -> str:
    pass

def apply_case(original: str, replacement: str) -> str:
    """Match the case pattern of original in the replacement string."""
    pass

**Input**:
  sentence = "The Quick BROWN fox jumps"
  substitutions = {"quick": "slow", "brown": "red", "fox": "cat"}

**Output**: "The Slow RED cat jumps"
# "Quick" -> title case -> "Slow"
# "BROWN" -> all caps -> "RED"
# "fox" -> lowercase -> "cat"

Follow-ups

  1. How do you handle substitutions where the replacement is a multi-word phrase and case patterns differ per word?
  2. What if dictionary keys overlap (e.g., "cat" and "catch")? Define a disambiguation rule.
  3. How would you process a file too large to fit in memory?
  4. Extend to support regex-based substitution patterns in the dictionary keys.

Full Details

Problem

Given a sentence and a dictionary mapping words to their replacements, rewrite the sentence by substituting every occurrence of a dictionary key with its value. Matching is case-insensitive but preserve the original casing pattern (all-caps, title-case, or lowercase) in the output.

python
def text_rewrite(sentence: str, substitutions: dict[str, str]) -> str:
    pass

def apply_case(original: str, replacement: str) -> str:
    """Match the case pattern of original in the replacement string."""
    pass

**Input**:
  sentence = "The Quick BROWN fox jumps"
  substitutions = {"quick": "slow", "brown": "red", "fox": "cat"}

**Output**: "The Slow RED cat jumps"
# "Quick" -> title case -> "Slow"
# "BROWN" -> all caps -> "RED"
# "fox" -> lowercase -> "cat"

Follow-ups

  1. How do you handle substitutions where the replacement is a multi-word phrase and case patterns differ per word?
  2. What if dictionary keys overlap (e.g., "cat" and "catch")? Define a disambiguation rule.
  3. How would you process a file too large to fit in memory?
  4. Extend to support regex-based substitution patterns in the dictionary keys.
Free preview — 6 questions shown. Unlock all Moveworks questions →

About This Question

This is a candidate experience report from a moveworks interview during the phone round.

It covers the following topics: Coding, Phone, Onsite, Strings .

About Moveworks Interview Reports

This question was reported by a candidate who interviewed at Moveworks. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Moveworks are the higher-signal extractions to take from this report.

For broader preparation context, the Moveworks interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Moveworks reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Moveworks Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Moveworks reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.