Overflow in intermediate arithmetic
Wrong move: Temporary multiplications exceed integer bounds.
Usually fails on: Large inputs wrap around unexpectedly.
Fix: Use wider types, modular arithmetic, or rearranged operations.
Move from brute-force thinking to an efficient approach using math strategy.
You are given two positive integers num and sum.
A positive integer n is good if it satisfies both of the following:
n is exactly num.n is exactly sum.The score of a good integer n is the sum of the squares of digits in n.
Return a string denoting the good integer n that achieves the maximum score. If there are multiple possible integers, return the maximum one. If no such integer exists, return an empty string.
Example 1:
Input: num = 2, sum = 3
Output: "30"
Explanation:
There are 3 good integers: 12, 21, and 30.
12 + 22 = 5.22 + 12 = 5.32 + 02 = 9.The maximum score is 9, which is achieved by the good integer 30. Therefore, the answer is "30".
Example 2:
Input: num = 2, sum = 17
Output: "98"
Explanation:
There are 2 good integers: 89 and 98.
82 + 92 = 145.92 + 82 = 145.The maximum score is 145. The maximum good integer that achieves this score is 98. Therefore, the answer is "98".
Example 3:
Input: num = 1, sum = 10
Output: ""
Explanation:
There are no integers that have exactly 1 digit and whose digits sum to 10. Therefore, the answer is "".
Constraints:
1 <= num <= 2 * 1051 <= sum <= 2 * 106Problem summary: You are given two positive integers num and sum. A positive integer n is good if it satisfies both of the following: The number of digits in n is exactly num. The sum of digits in n is exactly sum. The score of a good integer n is the sum of the squares of digits in n. Return a string denoting the good integer n that achieves the maximum score. If there are multiple possible integers, return the maximum one. If no such integer exists, return an empty string.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Math · Greedy
2 3
2 17
1 10
Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #3723: Maximize Sum of Squares of Digits
class Solution {
public String maxSumOfSquares(int num, int sum) {
if (num * 9 < sum) {
return "";
}
int k = sum / 9;
sum %= 9;
StringBuilder ans = new StringBuilder("9".repeat(k));
if (sum > 0) {
ans.append(sum);
}
ans.append("0".repeat(num - ans.length()));
return ans.toString();
}
}
// Accepted solution for LeetCode #3723: Maximize Sum of Squares of Digits
func maxSumOfSquares(num int, sum int) string {
if num*9 < sum {
return ""
}
k, s := sum/9, sum%9
ans := strings.Repeat("9", k)
if s > 0 {
ans += string('0' + byte(s))
}
if len(ans) < num {
ans += strings.Repeat("0", num-len(ans))
}
return ans
}
# Accepted solution for LeetCode #3723: Maximize Sum of Squares of Digits
class Solution:
def maxSumOfSquares(self, num: int, sum: int) -> str:
if num * 9 < sum:
return ""
k, s = divmod(sum, 9)
ans = "9" * k
if s:
ans += digits[s]
ans += "0" * (num - len(ans))
return ans
// Accepted solution for LeetCode #3723: Maximize Sum of Squares of Digits
// Rust example auto-generated from java reference.
// Replace the signature and local types with the exact LeetCode harness for this problem.
impl Solution {
pub fn rust_example() {
// Port the logic from the reference block below.
}
}
// Reference (java):
// // Accepted solution for LeetCode #3723: Maximize Sum of Squares of Digits
// class Solution {
// public String maxSumOfSquares(int num, int sum) {
// if (num * 9 < sum) {
// return "";
// }
// int k = sum / 9;
// sum %= 9;
// StringBuilder ans = new StringBuilder("9".repeat(k));
// if (sum > 0) {
// ans.append(sum);
// }
// ans.append("0".repeat(num - ans.length()));
// return ans.toString();
// }
// }
// Accepted solution for LeetCode #3723: Maximize Sum of Squares of Digits
function maxSumOfSquares(num: number, sum: number): string {
if (num * 9 < sum) {
return '';
}
const k = Math.floor(sum / 9);
const s = sum % 9;
let ans = '9'.repeat(k);
if (s > 0) {
ans += String.fromCharCode('0'.charCodeAt(0) + s);
}
if (ans.length < num) {
ans += '0'.repeat(num - ans.length);
}
return ans;
}
Use this to step through a reusable interview workflow for this problem.
Try every possible combination of choices. With n items each having two states (include/exclude), the search space is 2ⁿ. Evaluating each combination takes O(n), giving O(n × 2ⁿ). The recursion stack or subset storage uses O(n) space.
Greedy algorithms typically sort the input (O(n log n)) then make a single pass (O(n)). The sort dominates. If the input is already sorted or the greedy choice can be computed without sorting, time drops to O(n). Proving greedy correctness (exchange argument) is harder than the implementation.
Review these before coding to avoid predictable interview regressions.
Wrong move: Temporary multiplications exceed integer bounds.
Usually fails on: Large inputs wrap around unexpectedly.
Fix: Use wider types, modular arithmetic, or rearranged operations.
Wrong move: Locally optimal choices may fail globally.
Usually fails on: Counterexamples appear on crafted input orderings.
Fix: Verify with exchange argument or monotonic objective before committing.