Software Engineer - Junior, Mid, Senior (.NET / Angular)
Pioneering Evolution, LLC · Arlington, VA · 2 days ago
On-siteEngineeringVolunteer
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content.
The posting includes: Position description (intro), "WHAT YOU WILL WORK WITH:" list of technologies (maybe Skills). "KEY RESPONSIBILITIES:" list. "QUALIFICATIONS BY LEVEL:" with sub-levels. "EDUCATION:" line. "PROGRAM REQUIREMENTS:" (onsite, citizenship, security clearance). "WHO WE ARE AND WHAT WE OFFER:" benefits list.
We need to map to headings: About the role (intro description). Responsibilities (KEY RESPONSIBILITIES). Requirements (maybe PROGRAM REQUIREMENTS? Or maybe "Requirements" includes education, citizenship, etc). Qualifications (QUALIFICATIONS BY LEVEL). Skills (WHAT YOU WILL WORK WITH). Benefits (WHO WE ARE AND WHAT WE OFFER). Pay and Schedule: not present (no pay or schedule specifics). So we should NOT include Pay or Schedule sections.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive info, not invent or summarize away detail. Use
- for any list of duties/requirements/benefits, and
for prose. We need to decide what goes where. About the role: The initial paragraph(s) describing the role: "POSITION DESCRIPTION: Pioneering Evolution is seeking Software Engineers at the Junior, Mid-Level, and Senior levels to develop secure, modern enterprise software for the SyncPoint program. Our engineering team builds distributed web applications using modern .NET, Angular, PostgreSQL, REST APIs, Entity Framework, RabbitMQ, and related technologies. We are interested in candidates across a range of experience levels—from talented new graduates entering professional software development to experienced Senior Engineers capable of owning complex application components and mentoring other developers. Candidates are not expected to match every technology in our stack. We place greater value on strong software-engineering fundamentals, demonstrated depth appropriate to the candidate’s experience level, the ability to solve problems systematically, and the ability to learn and operate effectively within an established engineering environment. Backend engineering is particularly important to the team. Mid-Level and Senior candidates should demonstrate meaningful proficiency developing modern .NET backend applications and APIs. Senior candidates should also bring broader experience with enterprise application development, distributed systems, relational data, and technical mentorship. Final position level will be based on demonstrated experience, technical depth, scope of prior responsibility, and interview performance." That is prose; we can put in
. Responsibilities: list from KEY RESPONSIBILITIES. Should be
- .
Requirements: maybe combine PROGRAM REQUIREMENTS (onsite work, US citizenship, security clearance) and EDUCATION? The heading "Requirements" could contain both education and program requirements. We'll list as
- .
Qualifications: QUALIFICATIONS BY LEVEL (Junior, Mid-Level, Senior). This is detailed; we can keep as
- with subheadings? But we cannot add extra headings inside? We could keep as nested lists or just bullet points with level labels. Probably we can keep as
- with each level as a paragraph? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Qualifications is a list (by level). So we can make
- each containing the level description (maybe with for level). That's okay.
Skills: WHAT YOU WILL WORK WITH: list of technologies grouped categories. Could be
- .
Benefits: WHO WE ARE AND WHAT WE OFFER: list of benefits. Use
- .
We must not include Pay or Schedule.
We must not include boilerplate like EEO etc. There's none.
We must output only HTML fragment.
Let's craft.
Structure:
About the role
... (the intro paragraph(s) maybe combined into one or multiple
). We'll keep as one
with the whole text.
Responsibilities
- Design, develop, test, and maintain modern enterprise software using .NET and Angular.
- Develop REST APIs, backend services, application business logic, and user-interface components.
- Implement application persistence using Entity Framework and PostgreSQL.
- Build reliable integrations with internal and external systems.
- Develop asynchronous and event-driven functionality using RabbitMQ and related patterns.
- Write automated unit, integration, and other appropriate tests.
- Troubleshoot application defects and performance problems.
- Participate in peer code reviews.
- Collaborate with software engineers, the Tech Lead, Chief Engineer, Data Engineer, Test Engineer, DevOps Engineer, and product personnel.
- Participate in Agile planning, refinement, sprint execution, reviews, and retrospectives.
- Develop secure, maintainable software consistent with established architectural and engineering standards.
- Document significant implementation details, interfaces, and technical decisions.
- Contribute to continuous improvement of software-development practices.
- More experienced engineers will additionally:
- for any list. For sub-items we could nest
- . That's okay.
But we need to preserve the "More experienced engineers will additionally:" as a heading? Could be a
- with text then nested
- . Let's do:
- More experienced engineers will additionally:
- Own increasingly complex features and software components.
- Lead feature- and component-level implementation design.
- Identify technical risks and cross-component dependencies.
- Conduct deeper code and design reviews.
- Resolve difficult application and integration problems.
- Mentor less-experienced engineers.
- Contribute reusable patterns and shared software capabilities.
Then continue with rest: "System architecture and engineering standards are owned by the Chief Engineer, while day-to-day technical execution, decomposition, and team coordination are owned by the Tech Lead. Senior Software Engineers provide technical leadership primarily through hands-on implementation, feature design, troubleshooting, code review, and mentorship."
That's prose; could be a - ? It's not a duty but description. We'll put as a
after the
- .
But we need to keep within Responsibilities section; we can have multiple
- Bachelor's degree in Computer Science, Software Engineering, Information Systems, or a related technical discipline, or equivalent professional experience where permitted by the applicable contract or labor category.
- Must be available to satisfy the program’s established onsite work requirements in the Washington, D.C. metro area.
- U.S. Citizenship is required.
- Applicable security-clearance requirements apply based on the position and program labor category.
- Junior Software Engineer – Typically 0–3 years of professional experience. Candidates should demonstrate:
- Software-development fundamentals and working knowledge of object-oriented programming.
- Experience with C# or another strongly typed programming language.
- Familiarity with relational databases and SQL.
- Familiarity with web applications, HTTP, and APIs.
- Exposure to JavaScript or TypeScript.
- Familiarity with Git.
- Strong problem-solving ability and willingness to learn.
- Professional experience is not required for otherwise strong candidates. Internship, co-op, academic, military, open-source, or substantial personal-project experience may demonstrate the necessary capability.
- Prior experience with .NET, Angular, PostgreSQL, Entity Framework, RabbitMQ, or Azure is beneficial but not required.
- Mid-Level Software Engineer – Typically 3+ years of professional software-development experience. Candidates should demonstrate:
- Strong professional experience with C# and modern .NET / ASP.NET Core.
- Ability to independently develop REST APIs, backend services, and application business logic.
- Experience with Entity Framework Core or comparable ORM technology.
- Strong relational-database fundamentals.
- Experience writing and troubleshooting SQL.
- Experience developing automated unit and integration tests.
- Working experience with JavaScript/TypeScript and modern web applications.
- Ability to independently deliver complete production-ready features.
- Backend .NET depth is more important than an exact full-stack technology match at this level.
- Experience with PostgreSQL, Angular, RabbitMQ, Docker, Azure, distributed systems, or microservices is strongly preferred.
- Senior Software Engineer – Typically 7+ years of professional software-development experience. Candidates should demonstrate:
- Advanced C# and modern .NET / ASP.NET Core experience.
- Strong enterprise backend and REST API development.
- Strong relational-data and ORM experience.
- Experience with Angular or comparable modern enterprise frontend development.
- Experience with asynchronous messaging and event-driven systems.
- Experience with distributed or microservice-based applications.
- Strong automated-testing and diagnostic skills.
- Ability to independently own complex features or application components.
- Experience conducting technical code reviews.
- Experience mentoring other developers.
- Ability to resolve difficult cross-component technical problems.
- Strong alignment with our current .NET / Entity Framework / PostgreSQL / Angular / RabbitMQ stack is highly valued at the Senior level.
- Experience with micro-frontends is a significant plus.
- Backend: C#, .NET 8+, ASP.NET Core
- Data Access: Entity Framework / Entity Framework Core
- Database: PostgreSQL
- Front-End: Angular, TypeScript, HTML, CSS
- Integration: REST APIs, JSON
- Messaging: RabbitMQ and event-driven application patterns
- Architecture: Modular applications, distributed services, microservices
- Cloud: Microsoft Azure / Azure Government
- DevOps: Git, Docker, CI/CD, Azure DevOps
- Process: Agile/Scrum, Jira, Confluence
- Security: Secure coding practices, RBAC, CUI/IL4 controls
- Experience with micro-frontend architectures is especially valuable.
- Competitive salaries
- Opportunities for professional development and advancement
- Comprehensive range of benefits (evaluated continually)
- Paid time off
- 10 paid holidays
- Medical insurance
- Dental insurance
- Vision insurance
- Legal assistance
- Company-paid life insurance and AD&D
- Company-paid long term and short-term disability insurance
- Tuition reimbursement
- 401(k) plan with company contribution
- Continuing Education Opportunities
and
- . That's fine.
Now Requirements:
Requirements
Qualifications
Skills
Benefits
after the list or as a
- More experienced engineers will additionally:
- with text then nested
- ??? Actually we need to keep list flat? The instruction: Use
- .
We must not include Pay or Schedule.
We must not include boilerplate like EEO etc. There's none.
We must output only HTML fragment.
Let's craft.
Structure:
- .
Benefits: WHO WE ARE AND WHAT WE OFFER: list of benefits. Use
- each containing the level description (maybe with for level). That's okay.
Skills: WHAT YOU WILL WORK WITH: list of technologies grouped categories. Could be
- for any list of duties/requirements/benefits, and
- with each level as a paragraph? The instruction: Use
- with subheadings? But we cannot add extra headings inside? We could keep as nested lists or just bullet points with level labels. Probably we can keep as
- .
Qualifications: QUALIFICATIONS BY LEVEL (Junior, Mid-Level, Senior). This is detailed; we can keep as
- .
Requirements: maybe combine PROGRAM REQUIREMENTS (onsite work, US citizenship, security clearance) and EDUCATION? The heading "Requirements" could contain both education and program requirements. We'll list as