About Emily McCabe

Senior software engineer and systems architect translating ambiguity into working software.

I have 15+ years of experience building production software systems across government, healthcare technology, observability, developer tooling, and early-stage technology companies. I am known for translating complex or ambiguous requirements into clear technical designs and working software.

I am experienced leading full-stack product development, designing system architectures, and collaborating closely with technical teams, founders, clinicians, executives, and non-technical stakeholders.

My strengths include identifying hidden complexity early, simplifying system designs, and maintaining alignment between product vision, technical architecture, and engineering execution. I am comfortable operating across the full software lifecycle, from discovery and requirements through architecture, development, testing, documentation, and production deployment.

My background includes large-scale government data collection systems, multi-tenant healthcare platforms, developer tooling concepts, observability systems, and cloud-native applications built on modern serverless infrastructure.

What I'm looking for

Senior and staff-level roles.

I am especially interested in roles where strong engineering needs to be paired with product judgment, stakeholder communication, workflow discovery, and end-to-end ownership.

01Product engineering
02Full-stack engineering
03Healthtech platforms
04Healthcare workflow software
05Observability and developer tools
06AI-adjacent product systems
07Platform and workflow-heavy software
08Complex business or compliance systems
Strengths

How I work.

01

End-to-end ownership

I move from discovery and ambiguity through requirements, design, architecture, implementation, testing, documentation, and iteration.

02

Product & workflow thinking

I design software around how people actually work, whether the users are therapists, developers, product teams, engineering leaders, or operational stakeholders.

03

Technical communication

I write documentation, product copy, feature explanations, demos, and client-facing materials that make complex systems easier to understand.

04

Full-stack implementation

I contribute directly to frontend, backend, data modeling, integrations, product UI, and application architecture.

05

Analytical reasoning

My background in bioinformatics and mathematics helps me reason through complex systems, edge cases, data-heavy workflows, and AI-adjacent product decisions.

Technical skills

The toolkit.

Languages

TypeScriptJavaScriptPythonPerlSQL

Frontend

ReactNext.jsHTMLCSSTailwind CSSBootstrapjQuery

Backend

Node.jsExpressGraphQLREST APIsDjangoFlaskPerl Catalyst

Cloud & Infrastructure

AWS LambdaAPI GatewayAppSyncDynamoDBS3CDKServerless

Data & Analytics

MySQLPostgreSQLMongoDBNumPyPandasML workflowsOCR pipelines

Other

GitLinux / UNIXDockerAccessibilitySection 508HIPAA-aware design

Domains

Healthcare workflowsObservabilityDeveloper toolsSession replayDistributed tracingFederal data collection
Foundation

Federal systems and technical leadership.

Before JustBard Technologies, I worked continuously with the same federal engineering team from 2010 through 2025, first as a contractor and later as a federal employee and supervisory developer at the U.S. Census Bureau.

My work included production web applications supporting national survey and census data collection, secure full-stack development, accessibility-compliant interfaces, complex data-collection workflows, validation systems, and administrative record integration, along with mentorship, hiring support, onboarding, and performance review processes for long-running systems with strict reliability and compliance requirements.

  • 15 years with one federal engineering team
  • Supervisory developer, U.S. Census Bureau
  • Section 508 accessibility compliance
  • National-scale data collection systems
  • Mentorship, hiring, and onboarding
Resume

Tailored to the role.

Download a resume version aligned to the role. Links are placeholders for now.