Internship Systems Engineer resume example

• Under supervision, traced interface requirements from system specifications to integration tests; resolved a mismatched timing assumption between subsystems before the acceptance review.
• The team modeled CPU, memory, and storage growth for 22 production clusters; I supported research preparation, validation, and documentation under mentor review. The team kept the service stable through the next period of peak demand; confirmed with my mentor that my contribution was limited to the assigned support and validation work.
• The team automated operating-system patch waves with health checks and staged rollback; I supported research preparation, validation, and documentation under mentor review. The team removed a delivery risk before it blocked the next milestone; confirmed with my mentor that my contribution was limited to the assigned support and validation work.
• Under supervision, owned interface validation using MATLAB models and traceable requirements, resolving timing mismatches between two subsystems before integration testing.
• Under supervision, published system-architecture documentation linking each acceptance test to its requirement, reducing unowned review actions from 17 to 6 at the next baseline review.

• In a mentor-reviewed simulation, translated interface requirements into a system architecture model, allocating timing and failure behavior to subsystems. Maintained traceability from each requirement to its verification procedure.
• As a second supervised exercise, used MATLAB modeling to test sensor noise and delayed inputs against the control assumptions; recorded failed cases and updated interface documentation before the integration review.
• Under supervision, the team consolidated 31 host alerts into 9 symptom-based signals with runbooks; I supported research preparation, validation, and documentation under mentor review
• Built an isolated fixture with normal, malformed and interrupted inputs; recorded the expected response before running the implementation so failures were distinguishable from a changed assumption.
• Packaged the reproduction steps, configuration and regression tests with the project; checked the instructions from a clean environment and documented the unsupported cases instead of claiming production readiness.
• Owned the independent regression fixture using isolated inputs, resolved a failing edge case and released a reproducible test package with expected outputs.

Relevant coursework: Algorithms, operating systems, databases, computer networks

• Published an independent technical note using the project’s before-and-after traces, explaining the failed assumption, regression coverage and cases the implementation does not support.