CORA-O ownership
Served as the sole implementer for a release-ready CORA Optimize MVP covering the customer-prioritized 50% of the full requirement under a compressed timeline, with two teammates providing code review.
Professional experience
Growing with the system.
Seven years of continuity across one evolving mission, from junior contributor to technical anchor.
- Years on the DoWIN program
- 7+
- Platform users
- 1,000–1,500
- Cyber assessments supported
- Hundreds
- Minor releases across the program
- 31
Program continuity
One system. Expanding responsibility.
My professional path is tied to one system that kept growing—and gave me room to grow with it. I joined the DoWIN cyber assessment program as a junior engineer in 2019, stayed through a government contract transition, and now serve as a Software Engineer Advisor at Peraton.
That continuity gave me more than familiarity with a codebase. I learned the operational domain, watched requirements evolve, built across the interface and middle tier, and accumulated the context needed to explain not only how the application works, but why many of its decisions were made.
Career progression
The path through the program
Each role added a wider layer of ownership—from exploration and implementation to delivery, requirements, and architectural context.
October 2018–August 2019
Cinteot
Software Engineering Intern
Built a Java NLP prototype while developing the habits needed to take an idea from exploration toward an internal tool.
August 2019–May 2022
Cinteot
Junior Software Engineer
Joined the DoWIN program during my final semester of college and began working primarily across the UI and middle tier.
May 2022–July 2024
Cinteot
Software Engineer
Expanded into end-to-end ownership and helped carry CORA, PKI, and CSSP capabilities as part of a two-engineer team.
July 2024–Present
Peraton
Software Engineer Advisor
Continued on the program after the contract transition with greater feature, requirements, delivery, and architectural responsibility.
Current role
Peraton
Fort Meade, Maryland
Software Engineer Advisor
July 2024–Present
At Peraton, I develop and maintain the full lifecycle of a cyber assessment platform used across U.S. military and government organizations. The work spans planning, assessment execution, PKI, CSSP, and CORA workflows, reports and briefs, closure, and Plans of Action and Milestones.
My role now sits at the intersection of implementation and context: I own features across the stack, turn changing operational needs into buildable requirements, help a small team organize delivery, and preserve the reasoning behind a mature system.
A broader reporting model
Added assessment workflows, new briefs and reports, an interim reporting module, and the data schemas needed to support it.
Security readiness
Worked through Application Development STIG and Web Server SRG requirements during an internal review, implementing feasible remediations in preparation for an ATO assessment.
Requirements and delivery
Translate ambiguous requests into concrete workflows and technical plans while facilitating sprint planning, refinement, retrospectives, requirements discussions, and reporting for a two-to-three-person team.
ReactTypeScriptJavaScriptNode.jsMarkLogicXQueryGradleGitLab CI/CD
Foundation and growth
Cinteot
Chambersburg, Pennsylvania / Fort Meade, Maryland
Software Engineer
May 2022–July 2024
Junior Software Engineer
August 2019–May 2022
Software Engineering Intern
October 2018–August 2019
Cinteot is where I moved from coursework into production engineering. I began with an NLP prototype, joined the DoWIN program as a junior developer, and progressed into a Software Engineer role as the application and my responsibilities expanded.
Because the development team was small, ownership was broad. I concentrated on the user interface and middle tier while sharing responsibility for CORA, PKI, and CSSP with one other engineer who focused more heavily on the database and middle tier.
Starting with NLP
Built the first version of a Java prototype that analyzed government Requests for Information and extracted contract needs. I worked independently for roughly three months before the prototype grew into a three-person collaboration intended for internal use.
First end-to-end feature
Designed and delivered Risk Indicators for CCRI—now CORA—across the interface, middle tier, and data layer.
Versioned approval history
Enabled inspection administrators to modify risk indicators while preserving previously approved objects, keeping historical decisions available as requirements changed.
Report automation
Architected and implemented automated report generation for Command Cyber Readiness Inspections, Public Key Infrastructure Assessments, and Cybersecurity Service Provider Assessments.
Testing and review
Developed test plans and cases from unit through end-to-end testing, led and participated in code reviews, and documented processes and designs using Atlassian tools.
Recognition
DoD CIO 2023 Award Recipient.
Program continuity
Helped evolve the platform from its early development through the July 2024 contract transition, building the domain and architectural knowledge I carry in the current role.
JavaReactTypeScriptJavaScriptNode.jsMarkLogicXQuery
Earlier projects
Freelance
Software Developer
August 2016–August 2019
Alongside college, I worked on freelance software projects spanning community tools, Android development, and games.
Community tooling
Managed a Discord bot supporting a community of a few thousand users, using JavaScript, C#, and Java.
Android and IoT
Collaborated with a small team on an Android app using IoT beacons for businesses. Implemented a CI/CD pipeline to automate test execution, working with Java, C#, and MySQL.
Game development
Designed and developed a Java game using LibGDX.
JavaScriptC#JavaAndroidMySQLLibGDX
How I work
Engineering principles shaped by production
The habits that emerged from building and maintaining the same important system over time.
01
Find the real requirement
Operational requests rarely arrive as implementation-ready specifications. I work backward from the outcome, make assumptions visible, and turn the need into a workflow the team can build.
02
Own the path end to end
The strongest solutions account for the interface, service behavior, data model, delivery constraints, and how the feature will be supported after release.
03
Modernize deliberately
I refactor when a clearer pattern earns its place, while respecting the risk and historical context carried by a mature, regulated production system.
04
Make context transferable
Institutional knowledge is most valuable when it helps teammates understand past decisions, avoid regressions, and make better new ones.
The concise version