$grouped = $top3 | Group-Object Department Calculates sum, average, min, max.
$data | Select-Object *, @N="SalaryInt";E=[int]$_.Salary | Sort-Object SalaryInt -Desc Better yet, cast during filtering: powershell 3 cmdlets hackerrank solution
$data | Where-Object $_.YearsOfExperience -ge 2 Sorts by one or more properties. $grouped = $top3 | Group-Object Department Calculates sum,
If you have landed on the "PowerShell 3 Cmdlets" challenge on HackerRank, you are likely staring at a problem that demands more than just scripting intuition. It requires a specific understanding of how PowerShell v3 (and later) handles pipelines, object manipulation, and filtering. It requires a specific understanding of how PowerShell
Many candidates struggle not because they don't know PowerShell, but because they try to solve the challenge using traditional text parsing ( awk , sed , or regex -heavy approaches) rather than embracing .
Department AverageSalary ---------- ------------- Finance 100000 IT 85000 The challenge will silently test you on: Case 1: Fewer than 3 eligible employees If only 2 employees have >=2 years experience, your Select-Object -First 3 will return just 2, and Group-Object still works fine. Case 2: One department with multiple top earners If all top 3 are from IT, grouping will show only one row for IT with average salary of those 3. Case 3: Empty dataset If no employee has >=2 years experience, Where-Object outputs $null , and the rest of the pipeline should fail gracefully. HackerRank expects:
# Add defensive check $data = Import-Csv .\employees.csv | Where-Object $_.YearsOfExperience -ge 2 if (-not $data) Write-Host "No eligible employees"; exit # then continue... But if they disallow if , use Select-Object with -Skip trickery or rely on Format-Table to output nothing. CSV imports all values as strings. Convert to int before sorting: