"Compiled network performance reports for weekly review." That bullet tells a hiring manager you made a spreadsheet. It doesn't say whether uptime improved, whether you caught a BGP misconfiguration, or whether anyone acted on the data. "Compiled" is the verb you use when you haven't figured out what you actually accomplished yet.
Five rewrites that actually say something
Weak: Compiled VLAN configurations across 12 campus switches for documentation.
Strong: Consolidated VLAN schemas across 12 campus switches, eliminating 47 orphaned VLANs and reducing broadcast storm incidents by 31%.
Why it works: "Consolidated" implies you made decisions and removed waste. The original bullet stops at gathering; the rewrite shows you cleaned up the network.
Weak: Compiled packet-loss data from monitoring tools to identify network issues.
Strong: Diagnosed intermittent packet loss on three WAN links by correlating SNMP trap data with carrier-provided SLA reports, cutting mean time to resolution from 9 hours to 2.4 hours.
Why it works: "Diagnosed" is the engineering work. "Compiled" hides it. The rewrite names the tools (SNMP, SLA reports) and quantifies the outcome (MTTR drop). Hiring managers in big-law salary scale firms care about uptime—show the fix, not the prep.
Weak: Compiled BGP routing tables to document peering relationships.
Strong: Mapped BGP peering topology across four Tier-1 carriers, identifying two redundant paths and renegotiating transit costs down 18% ($43K annual savings).
Why it works: "Mapped" suggests spatial reasoning and discovery. The bullet doesn't stop at documentation—it lands on cost savings. The original version reads like busywork; the rewrite reads like infrastructure strategy.
Weak: Compiled firewall rule sets from three legacy appliances for migration planning.
Strong: Audited 1,847 firewall rules across three Cisco ASA appliances, decommissioned 612 obsolete entries, and migrated the clean ruleset to a Palo Alto PA-5250 with zero unplanned downtime.
Why it works: "Audited" implies judgment and cleanup. The numbers (1,847 rules, 612 obsolete) show scale. "Zero unplanned downtime" is the kicker—migration risk is what keeps directors awake.
Weak: Compiled switch port utilization metrics to support capacity planning.
Strong: Built automated switch-port utilization dashboards in Grafana polling 240 Juniper switches via SNMP, surfacing four congested uplinks and triggering a 10G-to-40G upgrade that dropped peak latency from 87ms to 11ms.
Why it works: "Built" signals you created tooling, not a one-time report. Naming Grafana, Juniper, and SNMP proves you know the stack. The latency drop (87ms → 11ms) is a performance win recruiters can picture.
The full list — 15 synonyms
| Synonym | What it implies | Example bullet |
|---|---|---|
| Aggregated | Combined data from multiple sources into one view | Aggregated syslog streams from 180 routers into Splunk, reducing alert noise by 64% |
| Consolidated | Merged and simplified scattered systems or configs | Consolidated three overlapping OSPF areas into a single backbone, cutting reconvergence time from 14s to 3s |
| Synthesized | Distilled complex inputs into a coherent output | Synthesized MTBF data from five vendors into a unified hardware refresh roadmap, deferring $210K in purchases |
| Assembled | Put discrete components together into a whole | Assembled 40Gbps backbone between two datacenters using DWDM optics and Arista 7500R switches |
| Engineered | Designed and built something technical | Engineered MPLS Layer-3 VPN for 19 branch sites, replacing DMVPN and improving jitter stability by 22% |
| Architected | Designed the structure and relationships | Architected multi-region SD-WAN topology with Cisco Viptela, reducing WAN OpEx 29% year-over-year |
| Integrated | Connected separate systems so they work together | Integrated NetBox IPAM with Ansible Tower, automating VLAN provisioning and cutting deployment errors by 91% |
| Developed | Created a new process, tool, or config from scratch | Developed Python script to parse BGP route tables and flag prefix-limit violations, preventing two outages |
| Curated | Selected and organized with judgment and taste | Curated baseline switch configs for edge, distribution, and core tiers, enforcing RADIUS and TACACS+ standards |
| Mapped | Charted relationships or topology | Mapped spanning-tree topology across six distribution blocks, eliminating four bridge loops |
| Audited | Reviewed for compliance, correctness, or waste | Audited 320 firewall ACLs, removing 89 unused entries and closing three open-to-any rules flagged in pen-test |
| Centralized | Brought distributed pieces into one authoritative place | Centralized DNS and DHCP onto Infoblox appliances, cutting IP conflicts from 12/month to zero |
| Cataloged | Created a structured inventory | Cataloged fiber paths and wavelengths in DWDM metro ring, preventing three accidental circuit cuts during work |
| Merged | Combined two or more into a unified whole | Merged acquired company's 10.0.0.0/8 IP space into corporate 172.16.0.0/12 schema with zero routing conflicts |
| Formulated | Designed a plan or policy with clear rationale | Formulated QoS policy marking voice traffic DSCP EF and video AF41, reducing packet loss on voice VLANs to 0.02% |
When 'compiled' is the right word
Sometimes gathering is the deliverable. If you're preparing documentation for an audit and the output is a compliance report, "compiled" is honest. If you assembled vendor SLA data into a single dashboard that executives review weekly and no further action is expected, "compiled" fits. If you created a runbook by collecting tribal knowledge from five engineers and the goal was just to write it down, "compiled" works. The test: if your value-add was organizing information—not acting on it—then the verb is fine. But if you built, fixed, or decided something after compiling, lead with that verb instead.
Verb rhythm and the four-bullet sameness problem
Open any network-engineer resume and you'll see the tell: four bullets in a row starting with "Configured." Then three starting with "Managed." Recruiters parse this as template work—like you wrote one bullet and found-and-replaced the noun. The fix isn't random variety for variety's sake; it's choosing verbs that match what you actually did. If you configured a switch, audited ACLs, diagnosed a routing loop, and architected a new VLAN schema, those are four different actions—use four different verbs. The rhythm problem surfaces when you flatten distinct work into one repeated verb. Vary on the syllable level too: "Configured" (3), "Built" (1), "Architected" (4), "Cut" (1). The staccato mix signals you're writing bullets, not filling a template. If you catch yourself copy-pasting a verb, stop and ask what the work actually was. The right verb is almost never the same as the line above it.
AI applies for you, you swipe. 40 free a day.
For more: classified synonym, communicated synonym, composed synonym, conceptualized synonym, converted synonym
Frequently Asked Questions
- What's a stronger word than 'compiled' for network engineering resumes?
- Use verbs like 'aggregated', 'consolidated', or 'synthesized' when you're merging data sources. Use 'engineered', 'architected', or 'built' when you created something new from parts. The verb should match whether you gathered or created.
- When is 'compiled' actually the right word on a resume?
- 'Compiled' works when the act of gathering itself was the deliverable—like compiling a compliance report from vendor sources or compiling network inventory for an audit. If you did something with the data afterward, use that action instead.
- Why do recruiters skip bullets that start with 'compiled'?
- 'Compiled' reads passive—it describes prep work, not outcomes. Recruiters scan for impact verbs tied to numbers. If your bullet says what you built or reduced after compiling, lead with that verb instead.