Lead Technical Systems Analyst with .NET Exp (In-Person Interview)

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, duplicated lines, application instructions. Must not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting does not mention pay, schedule, benefits. So we should not include those sections. We need to include sections for About the role (maybe description), Responsibilities, Requirements, Qualifications, Skills. Let's parse. The posting includes: - Greeting etc (boilerplate) ignore. - Title, location, duration, client, job ID, respond by: ignore. - Description: Candidate will work on existing and new initiatives including but not limited to Assessment Management System, Telecommunication Company Information, Pipeline Audit System (PAS), Document and Matter Management (DMM), and 753 Enforcement support, enhancements, and developments efforts. Then Duties (list of duties). Then Requirements (list of mandatory requirements). Then "Requirements This is an 100% Onsite." (maybe part of requirements). Then a long list of experience requirements (months). Then "Masters Degree in a computer or technology related field." Then "R sum Copy of Candidate Identification (i.e., Driver s License/Green Card/Visa and Passport if applicable) Any documents referenced in the above Requested Qualifications (i.e., professional certifications, degrees, etc.)" We need to preserve all substantive info. So we need to extract duties, requirements, qualifications, skills. Duties: bullet list under "Duties Requirements Gathering & Stakeholder Communication:" etc. Actually the text after "Duties" includes a heading "Duties Requirements Gathering & Stakeholder Communication:" then paragraphs. Let's extract each duty: - Collaborate with Department of Public Service (DPS) program staff, business stakeholders, and external entities to gather, analyze, and document business requirements for key initiatives (including Assessment Management, Pipeline Audit, and 753 Enforcement). - Lead business process reengineering sessions and deliver presentations on ""As-Is"" and ""To-Be"" system states. - Perform end-to-end technical analysis and design for complex enterprise systems. - Author highly detailed technical specifications, system architecture maps, and advanced system models including Unified Modeling Language (UML) diagrams, Data Flow Diagrams (DFDs), and Entity-Relationship Diagrams (ERDs). - Reverse-engineer legacy MS Access databases by analyzing tables, relationships, queries, forms, macros, and VBA modules. - Identify data integrity issues and design normalized (up to 3NF) relational database schemas for target platforms like SQL Server and Oracle. - Act as a technical liaison between business stakeholders, software vendors, and application developers. - Translate complex business rules, compliance logic, and workflows into precise technical requirements, pseudocode, database constraints, and system logic for .NET/C# application developers and DBAs. - Analyze, design, and support system integration points, web services, and APIs to facilitate secure data exchange. - Coordinate integrations with enterprise Document Management Systems (such as IBM FileNet) and external agency databases. - Develop comprehensive data migration strategies, data mapping matrices, and Extract, Transform, Load (ETL) specifications to ensure the seamless and secure transfer of legacy data into modernized target systems. - Write and execute complex SQL queries (including multi-table joins, subqueries, and analytical functions) to perform data validation, verify database migration accuracy, conduct system integration testing (SIT), and troubleshoot backend technical issues. That's duties. Requirements: The "Mandatory Requirements Experience (12+ Years)" then a paragraph describing role. Then "Requirements This is an 100% Onsite." Then a list of experience months: - 84 months experience with internal and external stakeholder communications and outreach, including the development of presentations and other materials that promote the rethinking of core business processes and envisioning of a reengineered environment. - 84 months of experience as a Lead Systems Analyst or Systems Architect directing the end-to-end technical analysis, design, and optimization of complex enterprise systems. - Proven expertise utilizing advanced systems modeling methodologies including Unified Modeling Language (UML), Data Flow Diagrams (DFDs), and entity-relationship modeling to conduct comprehensive As-Is/To-Be system state evaluations, perform technical gap analyses, and architect scalable, high-performance system workflows and technical specifications. - 84 months experience working on Business Requirements Project, as lead Analyst, which involved the application of strategies to gather and document business process requirements of new applications, with logical and physical data modeling, including data normalization (up to 3NF) to transform flat-file or legacy structures into enterprise relational database schemas (e.g., SQL Server, Oracle). - 60 Months of experience reverse-engineering legacy databases (specifically MS Access), including analyzing existing tables, relationships, queries, forms, macros, and VBA modules to identify structural anomalies, and writing complex SQL queries (including multi-table joins, subqueries, and analytical functions) to perform data validation, data profiling, and backend troubleshooting. - 60 Months of experience acting as a technical liaison between business stakeholders, software vendors, and application developers to translate business requirements into highly technical system design artifacts, including Entity-Relationship Diagrams (ERDs), Data Flow Diagrams (DFDs), and detailed data mapping/ETL specifications. - 48 Months of experience analyzing, designing, or supporting systems integrated with enterprise Document Management Systems (such as IBM FileNet) or enterprise relational databases (such as Oracle). - 36 months experience as a developer developing and implementing multi-tier .Net Framework and .Net Core web applications using C# code leveraging ASP.Net patterns: Web Forms and Model-View-Controller (MVC); and designing and implementing system integration points, web services, or APIs to facilitate data exchange. - Masters Degree in a computer or technology related field. - R sum Copy of Candidate Identification (i.e., Driver s License/Green Card/Visa and Passport if applicable) - Any documents referenced in the above Requested Qualifications (i.e., professional certifications, degrees, etc.) We need to separate into sections: About the role (maybe description), Responsibilities (duties), Requirements (mandatory experience), Qualifications (education, certifications), Skills (maybe technical skills like .NET, C#, UML, SQL, etc). However we must not create sections with filler. We have content for each. We need to decide what goes where. About the role: Could be the initial description paragraph: "Candidate will work on existing and new initiatives including but not limited to Assessment Management System, Telecommunication Company Information, Pipeline Audit System (PAS), Document and Matter Management (DMM), and 753 Enforcement support, enhancements, and developments efforts." Responsibilities: The duties list. Requirements: The mandatory experience list (the months etc). Could also include "This is an 100% Onsite." as a requirement. Qualifications: Masters Degree, maybe also certifications? The posting mentions "Requested Qualifications (i.e., professional certifications, degrees, etc.)" but no specific certs listed. So we could include Masters Degree as qualification. Also maybe the copy of ID is not a qualification but a requirement for application; but we should preserve substantive info. Could put under Requirements as well? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include that copy of ID requirement somewhere. It's not a duty, not a responsibility, not a qualification per se, but it's a requirement for application. Could be placed under Requirements as a bullet. Skills: Could extract technical skills: .NET/C#, ASP.NET Web Forms/MVC, SQL, UML, DFD, ERD, ETL, data migration, legacy MS Access reverse engineering, IBM FileNet, etc. Also stakeholder communication, presentations, business process reengineering, etc. But we must not invent; we can list skills that are explicitly mentioned. The posting mentions many skills implicitly in duties and requirements. We can create a Skills section listing: .NET Framework, .NET Core, C#, ASP.NET Web Forms, MVC, SQL (complex queries, joins, subqueries, analytical functions), UML, DFD, ERD, ETL, data migration, legacy MS Access reverse-engineering, IBM FileNet, Oracle, SQL Server, stakeholder communication, presentation development, business process reengineering, technical liaison, system integration, web services/APIs, document management integration. We must ensure we don't create filler like "various". All items should be directly from text. Let's extract explicit skill mentions: From duties: .NET/C# application developers, DBAs, UML diagrams, DFDs, ERDs, web services, APIs, IBM FileNet, SQL queries (multi-table joins, subqueries, analytical functions), data migration strategies, data mapping matrices, ETL specifications, legacy MS Access databases, tables, relationships, queries, forms, macros, VBA modules, normalized up to 3NF, SQL Server, Oracle, system integration points, web services, APIs, Document Management Systems. From requirements: stakeholder communications and outreach, development of presentations, Lead Systems Analyst, Systems Architect, technical analysis, design, optimization, advanced systems modeling methodologies (UML, DFD, entity-relationship), As-Is/To-Be evaluations, technical gap analyses, scalable high-performance system workflows, technical specifications, business requirements gathering, logical and physical data modeling, data normalization up to 3NF, reverse-engineering legacy MS Access databases, analyzing tables, relationships, queries, forms, macros, VBA modules, writing complex SQL queries (multi-table joins, subqueries, analytical functions), data validation, data profiling, backend troubleshooting, technical liaison, translating business requirements into technical system design artifacts (ERDs, DFDs, detailed data mapping/ETL specifications), analyzing, designing, or supporting systems integrated with enterprise Document Management Systems (IBM FileNet) or enterprise relational databases (Oracle), developing multi-tier .NET Framework and .NET Core web applications using C# code leveraging ASP.NET patterns: Web Forms and MVC, designing and implementing system integration points, web services, or APIs to facilitate data exchange. Masters Degree. Thus we can list skills accordingly. Now we need to output HTML fragment with headings

for each section. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which content is prose vs list. About the role: could be a

  containing the description paragraph. Responsibilities: list of duties as

  • . Requirements: list of mandatory experience items as
    • . Also include "This is an 100% Onsite." maybe as a
    • or

      . Since it's a requirement, we can include as

    • . Qualifications: list maybe
      • for Masters Degree, maybe also "Copy of Candidate Identification" etc? But that is more a requirement for application; but we already have it under requirements. Could also include under Qualifications as "Masters Degree in a computer or technology related field." and maybe "Professional certifications (if any)"? Not specified. We'll just include Masters Degree. Skills: list of skills as
        • . We must not include sections with no content. We'll include About the role, Responsibilities, Requirements, Qualifications, Skills. Check for duplication: Ensure we don't repeat same content across sections inadvertently. We'll try to keep each piece in appropriate section. Now produce HTML. We need to ensure no extra markdown fences, just raw HTML. Let's craft. First, About the role:

          Candidate will work on existing and new initiatives including but not limited to Assessment Management System, Telecommunication Company Information, Pipeline Audit System (PAS), Document and Matter Management (DMM), and 753 Enforcement support, enhancements, and developments efforts.

          Responsibilities:

          Responsibilities