Profile / leadership with technical range

Built for consequential work.

I understand the institution, stay credible with the technology, and keep both pointed at the mission.

Mark Gingrass outdoors on a hiking trail

The short version

I translate across the rooms where technology gets decided.

I’m a GS-14 program manager and COR III at the FDA, leading research-system modernization that serves more than 400 regulatory scientists. My work combines product direction, solutions architecture, acquisition, data integration, and the responsible use of AI inside the agency boundary.

That mix matters. Government systems do not fail only because of code. They fail at the seams—between the mission and the requirement, the contract and the product, the architecture and the operating environment. I’ve spent more than 20 years working those seams.

I’m now focused on senior TPM and Solutions Architect roles in GovTech and DefenseTech where federal fluency and technical judgment belong in the same person.

Mission context

Federal and defense experience, including the constraints of acquisition, security review, governance, and long-lived programs.

Program scale

Product strategy and modernization leadership for systems serving 400+ regulatory scientists.

Accountability

COR III experience overseeing contractor performance and translating program outcomes into executable delivery.

Technical range

Federal research systems, information retrieval, AWS serverless architecture, infrastructure as code, TypeScript, and applied AI workflows—enough depth to challenge assumptions at the whiteboard.

Education

Master of Business Administration and Bachelor’s in Computer Science, earned while working full-time.

Technical education

Taught C++ to adult learners at Metro Technology Centers and built successful technical courses for YouTube and Udemy. Clear explanation is part of the architecture role, not a side skill.

01Operating principles

How I approach the work when the stakes are real.

01.A

Make the decision visible

Architecture and program choices should expose the tradeoff, the owner, and what would cause us to revisit them.

01.B

Ship the useful core

A smaller release in users’ hands creates better evidence than a perfect roadmap still waiting for consensus.

01.C

Build for whoever comes next

Federal programs outlast their leaders. Systems and decisions need to be understandable, operable, and defensible after the room changes.

Away from the whiteboard

Outside, preferably with some elevation.

I hike, camp, mountain bike, run, skateboard, and make an annual trip to West Virginia for Class V whitewater. Ollie, my Golden Retriever, handles trail operations whenever conditions permit.

01

Air Force veteran

A foundation in service, discipline, and mission accountability.

02

Community volunteer

Tree planting and trail cleanup in the places I use.

03

Persistent builder

If a useful product does not exist, my instinct is to make the first version.