Technical Analyst Location: Vienna, VA (Hybrid) Pay Rate: Open to Both C2C and W2 options Position Type: Contract
Description:
This entry to mid-level Technical Analyst position is targeted specifically to contractors with 8 or more years of relevant information technology experience to support the Digital team in developing industry leading web, mobile, chat and voice solutions to meet our Members’ evolving financial needs. The role involves collaboration with business analysts, solution architects, developers, and testers to assess needs and define the technical system requirements for solutions.
Job Description:
Assume leadership of collaboration with product ownership to translate business need into the technical system requirements of the product Proactively identify requirement gaps and issue to product ownership Ensure non-happy path scenarios are considered and handled Advocate for solutions that consider ease of maintenance and component reuse opportunities Leverage available documentation and exercises test versions of applications and APIs to understand existing functionality to inform enhancement opportunities and creation of new capabilities Investigate enterprise and vendor APIs to determine whether necessary data is available to support intended system capabilities Map data between interfacing systems Assist lead analysts in developing and prioritizing features and epics to ensure work focuses on requirements with maximum value and are aligned with product delivery strategy Participate in project planning, sprint and release planning, daily stand-up meetings (scrums), demos/reviews, retrospectives, backlog refinement meetings, and other Scrum-related meetings. Perform application and services tests/validations Responsible for creating system requirement documentation for applications and services, including interface specifications Provide demos to internal project team, as well as to business stakeholders. Works closely with Business, Quality Assurance team and developers on projects and to address production issues Demonstrate ability to excel in a fast-paced environment with aggressive timelines that require managing multiple priorities concurrently Utilize system documentation, database information, application logs and scenario testing to determine root cause of system issues.
Have general understanding or working knowledge of the following:
Services-oriented architecture / microservices Multi-tier applications (presentation tier/services-processing tier/data management tier) Enterprise and vendor API integration Managing system behavior through configurable variables Error handling XML and JSON data structures
Qualifications/Experience:
Ability to write SQL queries Problem solving skill – Works well under pressure and challenges, team-player, good listener, analytical, creative, approachable, etc. Excellent verbal and written communication skills with the ability to partner with various levels of leadership within the organization Conducting complex technical analysis across multiple products Work in Agile methodology Writing requirements for a system Writing front end mobile and/or web application requirements is a plus Writing back end service requirements is a plus Experience using tools such as Postman or SoapUI to exercise APIs is a plus Digital Technical Analysis Contractor Role Clarifications 2026-11-13 Front-End Analysis Experience Analysts must do more than describe front-end behavior, such as display and navigation results from user actions. They must also define the technical orchestration those actions trigger: service calls (specific endpoints), error and partial-success handling, dynamic content, analytics tagging, and conditional display. Back-End Analysis Experience Analysts must do more than test and validate API requests and responses in a tool such as Postman. They must also define the requirements for service behavior: data retrieval, interactions with other services, business logic and rules, data transformations, response object mapping, and logging or events generated from the outcome. Analysts should be able to independently research enterprise and vendor APIs to find data sources for new functionality, or to document the changes existing APIs need to support it. Architectural Understanding Analysts should understand the differences between the presentation tier, middle service tier, and data tier, and how best to distribute functionality across them, especially in a multi-channel application. Not required, but helpful: If analysts know the difference between native mobile apps and responsive websites that adapt to mobile screens. Analysts should have an intuitive sense of when to check whether existing reusable components could be used, so new functionality isn't built redundantly. Documentation Technical User Stories: Analysts should be able to understand and write Gherkin acceptance criteria that include technical details, such as service behavior and endpoints and any other relevant technical details. Living Technical Specifications: Analysts should be able to maintain documentation for each capability and update it continuously as functionality changes. Collaborative Knowledge Management: Analysts should have experience documenting in a wiki format with a tool such as Azure DevOps or Confluence.
+ Must Have's:
Experience capturing technical requirements for information systems/applications Experience working with APIs Familiarity with multi-tier applications (application layer, services layer, data layer)
+ Nice to Have's:
Experience using tools such as Postman or SoapUI to exercise APIs Experience in the financial industry Experience working on requirements for native mobile applications
Ref: #851-Rockville-S1