Performance Test Engineer

ILAB LLC•Indianapolis, IN

4d•Remote

About The Position

The Performance Test Engineer is a technical leader in the Advanced Services organization and a strategic participant in customer engagements. The role helps establish performance testing direction with customers, develop performance testing standards and procedures within iLAB, and lead performance test strategy and test environment design. It owns the full performance testing lifecycle for assigned engagements, from planning and scripting through execution, analysis, and reporting. The engineer also contributes to the design, enhancement, and future growth of iLAB’s performance testing architecture and framework. The position leads customer and engagement activities, including managing multiple projects, serving as the primary contact for non-functional testing initiatives, scoping and estimating engagements, contributing to proposals and statements of work, and advising customers on performant and scalable software solutions. It defines test objectives and workload models, develops scripts and scenarios, prepares test data, configures environments and monitoring, executes tests, analyzes results, communicates findings and recommendations, and maintains transition-ready engagement documentation. The role provides technical leadership in performance engineering processes and helps maintain industry standards and cloud best practices across the organization. The position is full-time and remote, with the listed job location of Indianapolis, Indiana.

Requirements

At least 8 years of proven experience in performance test planning and hands-on execution across multiple projects.
Advanced knowledge of performance testing with LoadRunner, including VuGen, Controller or LoadRunner Enterprise, and Analysis, and with NeoLoad.
Proficiency in designing scripts and executing tests, including correlation, parameterization, and test data management for large virtual user populations.
Experience building performance workload models from business requirements and usage data.
Proficiency and experience performance testing cloud-based applications and identifying performance bottlenecks.
Experience with Application Performance Management tools such as Datadog, AppDynamics, Splunk, or Dynatrace, and capturing metrics such as response times, throughput, hits per second, CPU, garbage collection, memory utilization, and memory leaks.
Technical understanding of application ecosystems, including integrations, data flow, and access control.
Strong analytical, problem-solving, debugging, and troubleshooting skills.
Experience working in an agile engineering environment and with Continuous Integration/Continuous Delivery (CI/CD).
Proficiency in program, quality, and issue management.
Strong written and verbal communication skills, including the ability to produce customer-ready test plans, findings reports, and executive summaries.

Nice To Haves

Experience with Apache JMeter or similar performance testing tools.
ISTQB certification (Foundation Level, Performance Testing specialist, or equivalent).
Experience with state or federal government customers and their documentation and approval processes.
Experience testing applications hosted in Microsoft Azure or similar cloud platforms, including autoscaling behavior.
Experience training or mentoring performance testers.

Responsibilities

Manage multiple projects and serve as the primary point of contact for non-functional testing initiatives with customer project managers, business analysts, and application teams.
Help define scope and estimate effort for customer engagements; contribute to statements of work, proposals, and RFP/RFQ responses.
Lead customer discussions to understand end-to-end business processes across applications, platforms, and connected system interfaces.
Communicate risks and findings clearly, apply appropriate risk mitigation strategies, and engage stakeholders at all levels.
Advise customers on designing and constructing performant, scalable software solutions.
Identify non-functional requirements and define performance testing objectives, scope, and success criteria for each engagement.
Design performance test plans, strategies, and workload models, including concurrent users, pacing, think time, transaction rates, and SLA traceability.
Assess application interfaces and potential performance risks between systems and platforms, and propose testing strategies to test and mitigate those risks.
Recommend performance testing and monitoring tools, and participate in their evaluation, integration, and adoption.
Develop performance test scripts and scenarios in LoadRunner and NeoLoad, including correlation, parameterization, response verification, and complex authentication and session flows.
Configure and manage performance test environments, load generators, and monitoring; identify parameters for each test run.
Prepare and load test data to support virtual user populations required by workload models.
Review and maintain performance testing scripts, plans, data, and results for accuracy and completeness in accordance with iLAB coding and documentation standards.
Execute and report on baseline, load, peak, stress, and soak tests as required, confirming that results are repeatable before reporting them.
Confirm system stability and test repeatability against agreed variances.
Apply consistent monitoring metrics across runs, including response times, throughput, hits per second, error rates, CPU, memory, and garbage collection.
Analyze test results and conduct cloud, front-end, and back-end troubleshooting to locate performance obstructions and determine root causes.
Present performance test results, findings, and recommendations to customer leadership and application teams.
Translate findings into targeted improvements to strengthen system availability, reliability, and consistent software performance.
Provide technical leadership in developing and implementing performance engineering processes and maintaining performance industry standards and cloud best practices.
Maintain transition-ready engagement documentation so another iLAB engineer can take over an engagement.