DSA With AI
Week 12 ยท Bit Manipulation

Sum of Two Integers

Solve Sum of Two Integers by recognizing the Bit Manipulation pattern and turning the prompt into a small invariant before coding.

Medium Bit Manipulation Week 12 Practice runner

Frame the problem

  • Implement get_sum with the exact signature used by the interactive runner.
  • Use the visible tests to confirm the input and output shape before reading the final solution.
  • Treat challenge tests as edge-case pressure: empty inputs, repeated values, boundary shapes, or impossible states.
  • State the invariant before code, then dry-run one passing case and one failing-looking case.
1. Reveal example inputs and outputs

Example 1

Input:

get_sum(1, 2)

Output:

3
2. Brute force first

What direct brute force would be correct for a tiny input? Name the exact repeated work that the target pattern removes.

3. Reveal the insight ladder
  1. Map the prompt to the Bit Manipulation pattern instead of starting from syntax.
  2. XOR adds without carries; AND shifted left computes carries.
  3. Use a fixed-width mask to simulate two's-complement behavior in Python.
  4. Only reveal the final code after you can explain why each state update is safe.
4. Dry run before code
  1. sum-positive: input [1,2] should produce 3. Hint to check your state: XOR adds without carries; AND shifted left computes carries.
  2. sum-negative: input [-2,3] should produce 1. Hint to check your state: Use a fixed-width mask to simulate two's-complement behavior in Python.
5. Reveal final Python solution 
def get_sum(a: int, b: int) -> int:
    mask = 0xFFFFFFFF
    max_int = 0x7FFFFFFF
    while b & mask:
        a, b = (a ^ b) & mask, ((a & b) << 1) & mask
    return a if a <= max_int else ~(a ^ mask)

Complexity: Derive the exact bounds from get_sum: count how often each input item is visited and the maximum size of the main state structure.

Interview narration

  • I will first describe the invariant in plain language.
  • Then I will explain what data structure carries that invariant across the traversal, loop, recursion, or DP transition.
  • Finally I will walk one edge case before writing the optimized version.

Common traps

  • Solving only the visible example instead of the invariant.
  • Forgetting empty input, singleton input, duplicate values, or impossible-state cases.
  • Revealing the solution before doing a dry run from the starter signature.

Follow-up drills

1. How do you turn this into a timed interview answer?

Start with the invariant, give the brute force in one sentence, name the optimized state, code the core loop or recursion, and run one visible test aloud before mentioning complexity.

2. How do you scale the same pattern to a larger input?

Track which state grows with the input: hash maps and sets grow with distinct values, queues grow with frontier width, recursion grows with depth, heaps grow with active candidates, and DP tables grow with state count.

3. What should you practice from blank tomorrow?

Rewrite get_sum without looking at the solution, then compare only the invariant and state updates before checking syntax.

Interactive runner

Write the required Python function. Your code runs locally in this browser. Hints reveal one failing case at a time.