Senior Software Engineer (.NET/Angular)

• Typically 7+ years of professional software development experience.
• Advanced C# and modern .NET / ASP.NET Core.
• Strong enterprise backend and REST API development at scale.
• Deep relational data and ORM experience, including design and performance work.
• Angular or comparable modern enterprise frontend experience.
• Experience with asynchronous messaging and event-driven systems - sagas, eventual consistency, idempotency, the failure modes that only show up in production.
• Experience with distributed or microservice-based applications.
• Strong automated testing and diagnostic instincts.
• The ability to independently own complex features or entire application components.
• Real experience conducting technical code reviews and mentoring other engineers. This is not a bonus line item. It is a substantial part of the job.

Strong alignment with our current .NET / Entity Framework / PostgreSQL / Angular / RabbitMQ stack is genuinely valued at this level - at senior, the specifics do start to matter more.

How the leadership actually works here, so there is no surprise on day one: system architecture and engineering standards are owned by the Chief Engineer. The Tech Lead owns day-to-day technical execution, decomposition, and team coordination. Senior Software Engineers lead through hands-on implementation, feature design, troubleshooting, code review, and mentorship. This is a hands-on-keyboard senior role, not a title on the way out of the IDE. That requires a small team with high standards, strong engineering judgment, and very little tolerance for “good enough.”

We move fast, and we are trying to create something genuinely special - a platform architecture that outlasts the contract that funded it. That is not a thing a slow company or a mediocre team gets to do.

Ours is a small, dynamic team of people who are excellent at this work and who want to be surrounded by others who are. If you have spent a few years as the only engineer on a team who cared about the hard parts, you will find better company here. You will be building alongside talent worth building alongside, and your standards will raise the team’s rather than being sanded down by it.

Clearance, citizenship, and location:

• U.S. citizenship is required. No exceptions.
• An active clearance is not required to apply. Active Secret is welcome. Otherwise, interim Secret eligibility is required and PE sponsors - we will walk you through it.
• Hybrid, a few days a week at our Arlington HQ, 2550 S. Clark Street.

What we offer:

$132,000 - $165,000 based on demonstrated depth, scope of prior ownership, and interview performance. Plus paid time off, 10 paid holidays, medical, dental, and vision, company-paid life and AD&D, company-paid short- and long-term disability, 401(k) with company contribution, legal assistance, tuition reimbursement, and continuing education opportunities.

The honest pitch for a senior engineer: we are a small, fast-growing team building something architecturally ambitious for a customer whose mission actually matters. There is no committee between you and a design decision. There is no legacy monolith you are forbidden to touch. There is a real platform, a real roadmap, and a team that will be measurably better because you joined it.

We are willing to challenge the status quo, embrace unconventional approaches, and blaze a trail for others to follow. Bring a compass.

Innovate. Accelerate. Evolve.

Pioneering Evolution is an equal opportunity employer.

Every platform has a few problems that everyone quietly hopes someone else will pick up. The saga that half-completes. The tenant boundary that leaks under one specific permission configuration. The schema version that three modules depend on and nobody wants to touch.

We are looking for the engineer who picks those up.

Pioneering Evolution has spent over 15 years building the software that federal acquisition and financial management actually runs on. Our name is not decorative - we exist to push boundaries, explore new possibilities, and catalyze change in a domain that does not hand out change easily. Our Pioneers are at the forefront of something new, taking risks and venturing into uncharted territory.

We are building a federated enterprise platform for complex federal mission environments, and we need senior engineers who can own complex components.

The architecture, honestly:

At Pioneering Evolution, we are building a Mission Operating System (Mission OS) called SyncCore , designed to connect data, systems, workflows, and decisions across complex mission environments. SyncCore provides the secure, event-driven digital backbone for identity, integration, canonical data, governance, auditability, and interoperability-creating a trusted foundation on which mission capabilities can rapidly evolve. It is the foundation everything else stands on.

Built on SyncCore, SyncPoint is a modular application ecosystem composed of independently deployable modules that address specific operational needs, including requirements management, budgeting, task planning, resource allocation, execution, and decision support. Real programs. Real money. Real decisions.

We are not looking for a Senior Software Engineer simply to take the hardest tickets in the backlog. We are looking for an engineer who wants to help build the architecture, engineering culture, and technical foundation of a platform we expect to evolve for years.

You will take ownership of significant capabilities across SyncCore or SyncPoint-from architecture and domain modeling through APIs, event-driven workflows, data persistence, user experience, testing, deployment, and production performance. You will decide how services communicate, where boundaries belong, how data moves through the system, and how we build software that stays secure, observable, maintainable, and extensible as the platform grows.

You will also help raise the engineering capability of the people around you. That means thoughtful code reviews, mentoring junior and mid-level engineers, challenging architectural assumptions, establishing patterns where they are useful, and knowing when not to introduce complexity just because the technology makes it possible.

You may work on the SyncCore platform itself-identity, integration, eventing, canonical data, shared services, governance, auditability, and platform APIs-or lead the engineering of a SyncPoint mission module that turns complicated operational processes into intuitive software.

Either way, you will be close to the problem, close to the architecture, and close to the people making the decisions. No layers of bureaucracy separate you from the impact of what you build.

Current stack: C#, .NET 8+, ASP.NET Core, MediatR-based CQRS-lite command pipeline, PostgreSQL with Entity Framework Core, Cosmos DB for saga audit, RabbitMQ with Wolverine for messaging, Hangfire for scheduled work, YARP for gateway routing, Angular 19 and TypeScript, Docker, Bitbucket Pipelines, xUnit, and Azure / Azure Government with CUI and IL4 controls throughout.

The architecture is modern, but the technology isn’t the point. The point is using it to solve difficult problems exceptionally well.

SyncCore and SyncPoint are being built now-not inherited from another team and not already set in stone. If you want your fingerprints on a new platform’s architecture rather than simply maintaining someone else’s, this is that opportunity.

We currently use a micro-frontend architecture. If you have done it, we want to hear about it.