Software Engineer T2

Duration: 12 Months <\/b><\/p>

Location: Herndon, VA <\/span><\/b>
<\/p>

Description: <\/span><\/b>
<\/p>

• Citizenship: U.S. citizens <\/span><\/b>
<\/p>

• Hybrid Office: Must be in office at least 4 days per week (Herndon, VA) with the expectation that there maybe weeks where 5 days are required. <\/span><\/b>
<\/p>

• Conversion Status: Must be willing to convert to FTE in October 2026<\/span><\/b>
<\/p>

Process Automation Engineer: <\/span><\/b> <\/span>(Years of Experience: 3\-5)<\/span>
<\/p>

Analytical & Process\-Oriented Skills: <\/span><\/b>
<\/p>

Process Mapping and Analysis: <\/span><\/b> The ability to observe a manual task and deconstruct it into its fundamental steps is crucial. This involves using techniques like Value Stream Mapping (VSM), Business Process Model and Notation (BPMN), and creating detailed flowcharts to visualize the current state. <\/span>
<\/p>

Root Cause Analysis: <\/span><\/b> Engineers must go beyond documenting what is done to understand why it's done. They use methods like the 5 Whys or Fishbone Diagrams to identify the underlying reasons for each step, which helps in distinguishing value\-added activities from waste that shouldn't be automated. <\/span>
<\/p>

Requirements Engineering: <\/span><\/b> This is the core skill of translating observations into clear, measurable, and unambiguous requirements for the automation team. It involves writing detailed user stories, defining acceptance criteria, and specifying functional and non\-functional requirements. <\/span>
<\/p>

Data\-Driven Decision Making: <\/span><\/b> They need to be proficient in collecting and analyzing process data (e.g., cycle times, error rates, volumes) to build a business case for automation and to establish a baseline for measuring success. <\/span>
<\/p>

Technical Skills: <\/span><\/b>
<\/p>

Understanding of Automation Technologies: <\/span><\/b> While they don't need to be expert coders, they must have a solid grasp of what's possible with automation technologies. This includes knowing the capabilities and limitations of Robotic Process Automation (RPA), APIs, scripts, and other workflow automation tools. <\/span>
<\/p>

Systems Thinking: <\/span><\/b> The ability to see how the manual process interacts with upstream and downstream systems is vital. They need to understand the data inputs, outputs, and how a new automated solution will fit into the existing IT ecosystem. <\/span>
<\/p>

Basic Database and API Knowledge: <\/span><\/b> A foundational understanding of how data is stored (SQL) and how systems communicate (APIs) is extremely helpful for defining data\-related requirements accurately. <\/span>
<\/p>