{"schemaVersion":"jobsearcher.job.v1","id":"6003a175c470ecc379ddfe2e","url":"https://jobsearcher.com/jobs/6003a175c470ecc379ddfe2e","canonicalUrl":"https://jobsearcher.com/jobs/6003a175c470ecc379ddfe2e","title":"Technical Analyst","description":"Technical Analyst\nLocation: Vienna, VA (Hybrid)\nPay Rate: Open to Both C2C and W2 options\nPosition Type: Contract\n\nDescription:\nThis 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.\n\nJob Description:\nAssume leadership of collaboration with product ownership to translate business need into the technical system requirements of the product\nProactively identify requirement gaps and issue to product ownership\nEnsure non-happy path scenarios are considered and handled\nAdvocate for solutions that consider ease of maintenance and component reuse opportunities\nLeverage available documentation and exercises test versions of applications and APIs to understand existing functionality to inform enhancement opportunities and creation of new capabilities\nInvestigate enterprise and vendor APIs to determine whether necessary data is available to support intended system capabilities\nMap data between interfacing systems\nAssist 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\nParticipate in project planning, sprint and release planning, daily stand-up meetings (scrums), demos/reviews, retrospectives, backlog refinement meetings, and other Scrum-related meetings.\nPerform application and services tests/validations\nResponsible for creating system requirement documentation for applications and services, including interface specifications\nProvide demos to internal project team, as well as to business stakeholders.\nWorks closely with Business, Quality Assurance team and developers on projects and to address production issues\nDemonstrate ability to excel in a fast-paced environment with aggressive timelines that require managing multiple priorities concurrently\nUtilize system documentation, database information, application logs and scenario testing to determine root cause of system issues.\n\nHave general understanding or working knowledge of the following:\nServices-oriented architecture / microservices\nMulti-tier applications (presentation tier/services-processing tier/data management tier)\nEnterprise and vendor API integration\nManaging system behavior through configurable variables\nError handling\nXML and JSON data structures\n\nQualifications/Experience:\nAbility to write SQL queries\nProblem solving skill – Works well under pressure and challenges, team-player, good listener, analytical, creative, approachable, etc.\nExcellent verbal and written communication skills with the ability to partner with various levels of leadership within the organization\nConducting complex technical analysis across multiple products\nWork in Agile methodology\nWriting requirements for a system\nWriting front end mobile and/or web application requirements is a plus\nWriting back end service requirements is a plus\nExperience using tools such as Postman or SoapUI to exercise APIs is a plus\nDigital Technical Analysis Contractor Role Clarifications 2026-11-13\nFront-End Analysis Experience\nAnalysts 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.\nBack-End Analysis Experience\nAnalysts 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.\nAnalysts 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.\nArchitectural Understanding\nAnalysts 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.\nNot required, but helpful: If analysts know the difference between native mobile apps and responsive websites that adapt to mobile screens.\nAnalysts should have an intuitive sense of when to check whether existing reusable components could be used, so new functionality isn't built redundantly.\nDocumentation\nTechnical 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.\nLiving Technical Specifications: Analysts should be able to maintain documentation for each capability and update it continuously as functionality changes.\nCollaborative Knowledge Management: Analysts should have experience documenting in a wiki format with a tool such as Azure DevOps or Confluence.\n\n+ Must Have's:\nExperience capturing technical requirements for information systems/applications\nExperience working with APIs\nFamiliarity with multi-tier applications (application layer, services layer, data layer)\n\n+ Nice to Have's:\nExperience using tools such as Postman or SoapUI to exercise APIs\nExperience in the financial industry\nExperience working on requirements for native mobile applications\n\nRef: #851-Rockville-S1","company":"Systemone","rawCompany":"systemone","city":"Fairfax","state":"VA","isRemote":false,"isActive":false,"createdAt":"2026-10-08T13:45:40.366Z","occupations":[{"code":"15-1212.00","title":"Information Security Analysts","slug":"information-security-analysts"},{"code":"15-1211.00","title":"Computer Systems Analysts","slug":"computer-systems-analysts"},{"code":"15-1299.05","title":"Information Security Engineers","slug":"information-security-engineers"}],"industries":[{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541690","title":"Other Scientific and Technical Consulting Services","slug":"other-scientific-and-technical-consulting-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Technical Analyst","description":"Technical Analyst\nLocation: Vienna, VA (Hybrid)\nPay Rate: Open to Both C2C and W2 options\nPosition Type: Contract\n\nDescription:\nThis 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.\n\nJob Description:\nAssume leadership of collaboration with product ownership to translate business need into the technical system requirements of the product\nProactively identify requirement gaps and issue to product ownership\nEnsure non-happy path scenarios are considered and handled\nAdvocate for solutions that consider ease of maintenance and component reuse opportunities\nLeverage available documentation and exercises test versions of applications and APIs to understand existing functionality to inform enhancement opportunities and creation of new capabilities\nInvestigate enterprise and vendor APIs to determine whether necessary data is available to support intended system capabilities\nMap data between interfacing systems\nAssist 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\nParticipate in project planning, sprint and release planning, daily stand-up meetings (scrums), demos/reviews, retrospectives, backlog refinement meetings, and other Scrum-related meetings.\nPerform application and services tests/validations\nResponsible for creating system requirement documentation for applications and services, including interface specifications\nProvide demos to internal project team, as well as to business stakeholders.\nWorks closely with Business, Quality Assurance team and developers on projects and to address production issues\nDemonstrate ability to excel in a fast-paced environment with aggressive timelines that require managing multiple priorities concurrently\nUtilize system documentation, database information, application logs and scenario testing to determine root cause of system issues.\n\nHave general understanding or working knowledge of the following:\nServices-oriented architecture / microservices\nMulti-tier applications (presentation tier/services-processing tier/data management tier)\nEnterprise and vendor API integration\nManaging system behavior through configurable variables\nError handling\nXML and JSON data structures\n\nQualifications/Experience:\nAbility to write SQL queries\nProblem solving skill – Works well under pressure and challenges, team-player, good listener, analytical, creative, approachable, etc.\nExcellent verbal and written communication skills with the ability to partner with various levels of leadership within the organization\nConducting complex technical analysis across multiple products\nWork in Agile methodology\nWriting requirements for a system\nWriting front end mobile and/or web application requirements is a plus\nWriting back end service requirements is a plus\nExperience using tools such as Postman or SoapUI to exercise APIs is a plus\nDigital Technical Analysis Contractor Role Clarifications 2026-11-13\nFront-End Analysis Experience\nAnalysts 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.\nBack-End Analysis Experience\nAnalysts 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.\nAnalysts 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.\nArchitectural Understanding\nAnalysts 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.\nNot required, but helpful: If analysts know the difference between native mobile apps and responsive websites that adapt to mobile screens.\nAnalysts should have an intuitive sense of when to check whether existing reusable components could be used, so new functionality isn't built redundantly.\nDocumentation\nTechnical 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.\nLiving Technical Specifications: Analysts should be able to maintain documentation for each capability and update it continuously as functionality changes.\nCollaborative Knowledge Management: Analysts should have experience documenting in a wiki format with a tool such as Azure DevOps or Confluence.\n\n+ Must Have's:\nExperience capturing technical requirements for information systems/applications\nExperience working with APIs\nFamiliarity with multi-tier applications (application layer, services layer, data layer)\n\n+ Nice to Have's:\nExperience using tools such as Postman or SoapUI to exercise APIs\nExperience in the financial industry\nExperience working on requirements for native mobile applications\n\nRef: #851-Rockville-S1","datePosted":"2026-10-08T13:45:40.366Z","dateModified":"2026-10-08T13:45:40.366Z","hiringOrganization":{"@type":"Organization","name":"Systemone","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Fairfax","addressRegion":"VA","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"6003a175c470ecc379ddfe2e"},"url":"https://jobsearcher.com/jobs/6003a175c470ecc379ddfe2e"}}