Get a reply from this recruiter
Your resume and cover letter, tailored to exactly what they’re hiring for.
System One, Inc. in Vienna, VA is seeking a Technical Analyst on a contract basis to join the Digital team.
The role focuses on translating business needs into technical requirements for web, mobile, chat, and voice solutions, collaborating with analysts, architects, developers and testers. You will map data between systems, assess APIs, contribute to feature prioritization, and participate in Scrum ceremonies.
Location: Vienna, VA (Hybrid)
Pay Rate: Open to Both C2C and W2 options
Position Type: Contract
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.
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.
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.
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.
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.
Analysts should be able to maintain documentation for each capability and update it continuously as functionality changes.
Analysts should have experience documenting in a wiki format with a tool such as Azure DevOps or Confluence.
Ref: #851-Rockville-S1