Design Technologist

About the role

Design and engineering converge to turn high-fidelity design intent into production-quality interfaces for aviation, defense, energy, and critical infrastructure.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Interfaces are crafted from design specs to prioritize performance, reusability, and scalability for critical workflows. High-fidelity design intent is implemented in high-density data contexts, preserving design intent while bridging design and engineering. Tooling and automation are created to accelerate the design-to-development workflow and remove manual steps. Implementations are refined using user feedback, operational requirements, and performance insights to ensure fitness for mission use.

Requirements

Strong front-end engineering skills, such as TypeScript, React, and modern CSS, are paired with a designer's eye, demonstrated by a portfolio of shipped interfaces or interactive prototypes. Building and maintaining design systems in code is required, including design tokens, component libraries, and tooling that stays consistent with Figma or similar sources of truth. Translating high-fidelity designs into pixel-accurate, performant implementations is necessary, especially for dense, operationally critical environments. A strong sense of visual hierarchy, typography, and layout is required, with the engineering chops to realize it faithfully in the browser. Comfort with data-rich web applications and rendering performance using canvas, SVG, WebGL, or mapping/geospatial libraries is required. Collaborating with cross-functional teams, including designers, engineers, product managers, and end users, is required to align implementation with real-world operational needs. Working comfortably in iterative processes is required, incorporating feedback, research, and performance data to refine and evolve work over time. Consistency and scalability are driven by an eye for detail, with a focus on maintaining a unified design language in code across multiple products and use cases. Understanding responsive design and accessibility best practices is required to ensure interfaces work across devices and for all users. Passion for mission-driven work in domains that demand precision, clarity, and real-world impact is required.

Practical notes

Government data, including on contracts that may require U.S. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Design Technologists combine design sensibility with strong front-end engineering to deliver interfaces used in high-stakes environments. The role relies on modern JavaScript frameworks, design systems, and data visualization techniques to manage complexity and performance. Mission-driven domains such as aviation, defense, and energy demand precision, clarity, and reliable real-time decision support. Iterative refinement driven by user feedback and performance data is common, requiring adaptability and rigorous quality standards.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.