Technology Consultant: Systems Integration Architecture Save

Overview

Element14 is hiring a Technology Consultant with a focus on systems integration architecture to own the technical side of our data and systems work at a federal civilian health agency. You will own the technical picture end to end, from system documentation and working sessions with system teams through to current-state architecture, gap analysis and the future-state options that shape our recommendations. The role centers on architecture and analysis rather than day-to-day software development, but hands-on engineering experience is a real plus here, and the more technical you are, the more you will bring to the work that follows. We are looking for someone who can sit down with system administrators and security staff, understand how a set of systems really works and connects, and explain it clearly to the people who make decisions. 

What you would work on 

Our client is a large federal civilian health agency. Across its campuses, it runs laboratories, tracks health threats and supports the national response to public health emergencies. Keeping those campuses, and the thousands of people who work on them, safe is part of the mission, and the agency is now assessing its security posture across all hazards. 

Element14 supports the prime contractor on that assessment, bringing the data and systems lens. At any time, leaders need to know quickly who is on campus, where they are, what the access control and camera systems are reporting, and whether an alert reached everyone. Today that information sits in a dozen or so separate systems, each built for its own purpose: identity and badging, access control, visitor management, HR, emergency notification, video, facilities and incident management. Pulling the picture together takes longer than an incident allows. 

Mapping those systems is the starting point, not the goal. The goal is a more interoperable security data and technology function at the agency: systems that share data in real time instead of through batch files and manual extracts, that agree on the same people, places and assets, and that feed a common operating picture leaders can act on. You will help define what that future state looks like, how to get there in practical steps, and which projects should come first. Those recommendations will shape how the agency invests in campus security in the years ahead. 

We are AI-first by default. Modern AI tools are part of the toolkit on every engagement: LLMs for working through long technical documentation, organizing findings and drafting deliverables. We are not chasing AI for its own sake, and we always work within our clients’ rules on what information can be used. We expect the people on this team to be fluent in current tools and to use them to be faster and sharper than the federal consulting median. 

Beyond this engagement, we expect this team to grow with the firm. The assessment is our first project with this agency, and we see it as the start of a longer relationship there. As Element14 wins additional federal and state work, the people we hire now will help shape future engagements and the capabilities we build. 

What you will do 

• Map the systems. Work with the prime team to identify the core systems that hold security and personnel data (identity and badging, access control, visitor management, HR records, emergency notification, video, facilities and incident management) and what each one holds. 

• Read the documentation that matters. ATO packages, system security plans, privacy impact assessments, System of Records Notices, interconnection agreements and data dictionaries. Pull out what each system does, what it connects to and where the risks are. 

• Run technical working sessions with system teams. Hosting and cloud posture, how data actually moves (real-time API, scheduled batch, SFTP or manual extract), latency, downtime and failover, data quality, and the questions each system cannot answer. 

• Document the current state so anyone can use it. Architecture and data-flow diagrams, interface inventories and system profiles that hold up for technical reviewers and make sense to leadership. 

• Find the gaps and shape the options. Interoperability gaps, single points of failure, duplicated or conflicting records. Turn them into future-state concepts and candidate projects with sequencing and rough order-of-magnitude cost, working with the engagement lead who owns the final recommendations. 

• Write and present as part of the team. Draft the technical sections of team deliverables, support workshops and briefings, and work within the prime contractor’s processes and standards. 

• Use modern AI tooling as a standard part of the workflow. LLMs to work through long documentation, organize findings and draft faster, always within the client’s rules on what information can be used. We expect fluency here, not curiosity. 

Who we are looking for 

In addition to the qualities we look for in everyone on the team: 

• Genuine interest in public service. You are excited about helping government agencies operate more effectively and advance their mission. The variety appeals to you: one quarter you might be working on financial integrity for housing programs, the next on agricultural data, the next on health programs. 

• Commitment to technical craft. You stay current. You can point to tools and techniques you have picked up in the last twelve months and explain why they matter. Cloud, data, and AI are central to what we do, and we expect that to be central to how you think too. 

• Strong communication and relationship-building. You build trust with government stakeholders by listening carefully, explaining clearly, and following through. You learn the program, not just the data, deeply enough that clients want you in the room. 

• Drive and ownership. This is not a clock-in, clock-out role. We want people who care, and that shows up in their work: anticipating the next question, fixing what is broken before being asked, and treating the mission as their own. 

• Integration and architecture foundations. Four to six years in systems integration, solution or enterprise architecture, or technical consulting, ideally with federal or other regulated clients. Working knowledge of APIs, messaging, ETL and batch file transfer, and identity and access management. You can turn a messy conversation into a clear architecture or data-flow diagram. 

• Federal systems literacy. Comfortable reading ATO packages, system security plans, privacy impact assessments and interconnection agreements, and working with NIST 800-53 and FISMA concepts. You know what to look for and what to ask. 

• Consultative, not just technical. You can run a productive session with system administrators and cybersecurity staff, then explain what you learned to a non-technical leader in plain language. 

• Clear writing. Your diagrams and documents stand on their own. Your findings are specific, sourced and easy to act on. 

• Applied, not academic. You like real problems with real stakes. You would rather give a client a practical recommendation they can fund than a perfect target-state architecture nobody can build. 

• AI-first. Comfortable using modern LLMs as part of your daily workflow. You have opinions about where they help and where they do not, and you use them to be faster, not flashier. 

• Preferred: evidence of work you have done outside a paid job, such as open-source contributions, side projects, academic research, hackathons, or a portfolio of architecture work you can walk us through. We read these as signals of curiosity and craft. 

• Also a plus: experience with physical security or identity systems (physical access control, PIV credentials and federal identity management, video management, visitor management or mass notification); master data management or entity resolution; federal health agencies; emergency management or security operations; rough order-of-magnitude cost estimating; hands-on development or data engineering experience (for example Python, SQL, API development or cloud infrastructure); working inside a prime–subcontractor team; certifications such as TOGAF, AWS or Azure Solutions Architect, or CompTIA Security+. 

• Required: ability to obtain a U.S. Federal Public Trust clearance. This requires U.S. citizenship or lawful permanent residency and a successful background investigation. 

Salary range: $135,000 – $160,000 annual base. Final offer determined based on experience, depth, and the specific seat. We post ranges because we believe in transparency about pay. 

Location: Remote. Element14 is a remote company, and candidates anywhere in the United States will be considered; Washington, DC metro area preferred. Occasional travel to the DC area to meet with the engagement lead (for candidates outside DC) and to the client site as the project requires. U.S. work authorization required. 

Perks & benefits 

• Competitive salary 

• Medical, dental, and vision insurance 

• Life insurance and short-term / long-term disability 

• 401(k) with employer match 

• Paid time off and federal holidays 

• Hybrid and flexible work arrangements 

• Professional development and certification support 

• Employee Assistance Program