Full-Stack .NET/Angular/AWS Developer
TriCom Technical Services · Kansas City, MO · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes a summary paragraph (maybe "About the role")? The first paragraph: "Full-Stack .NET/Angular/AWS Developer Summary Our client is seeking a Developer to design and build full-stack enterprise Web applications from an on-premises engineering center, delivered to AWS Cloud. This developer will own features end-to-end - from database schema and C# service layer through Angular UI and drive AI-assisted engineering practices (GitHub Copilot, Copilot Chat, prompt-driven development), incorporating SOLID design, clean architecture, and secure, scalable Cloud-native systems." That's about the role. So we can have
.
Requirements: after "Requirements". We'll list bullet points.
Qualifications: Not separate; maybe "Preferred" could be considered Qualifications? But we have a "Preferred" block after Requirements. The instructions say use headings for Qualifications if there is content. The posting includes "Preferred" with items like AWS certification, Docker+Kubernetes, etc. That could be Qualifications or Skills. We could treat "Preferred" as Qualifications. Also there is a mention of "This is a 12-month Contract position (possibly longer). Benefits available with TriCom during the contract period include low cost Medical/Dental, Paid time off, Paid Holidays, and 401(k) (with immediately-vested company match). H1-B Visa sponsorship is not available for this position. No third-parties, please." That includes Benefits and maybe Pay/Schedule not given. Benefits: we have specific benefits: low cost Medical/Dental, Paid time off, Paid Holidays, 401(k) with immediate vest company match. Also mention contract length 12-month possibly longer. That's not pay or schedule. So we can include Benefits section.
Pay: not specified, so omit.
Schedule: not specified, omit.
Skills: maybe we could have a Skills section but we already have Responsibilities and Requirements covering skills. The instruction says prefer few substantive sections over many thin ones. We could combine Skills into Requirements or Qualifications. But we have a separate "Preferred" block which could be Qualifications. Let's create sections: About the role, Responsibilities, Requirements, Qualifications (Preferred), Benefits.
We must not repeat job title as heading. No Job ID.
We must not include boilerplate like EEO etc. Not present.
We must output only HTML fragment.
Let's craft.
We need to preserve all substantive information. Ensure we don't lose any detail.
Let's extract About the role paragraph exactly: "Full-Stack .NET/Angular/AWS Developer Summary Our client is seeking a Developer to design and build full-stack enterprise Web applications from an on-premises engineering center, delivered to AWS Cloud. This developer will own features end-to-end - from database schema and C# service layer through Angular UI and drive AI-assisted engineering practices (GitHub Copilot, Copilot Chat, prompt-driven development), incorporating SOLID design, clean architecture, and secure, scalable Cloud-native systems."
We might want to keep as is.
Responsibilities bullet list: Let's list each line after "Responsibilities". The text:
"Design and build production-grade full-stack Web applications using C#/.NET 8+, ASP.NET Core Web API, Entity Framework Core, and Angular 17+.
Model, tune, and evolve relational schemas in SQL Server/PostgreSQL and integrate with Aurora/RDS in AWS.
Architect for AWS deployment including API Gateway, Lambda, ECS/EKS on Fargate, S3, SQS/SNS, EventBridge, Secrets Manager, CloudWatch, and KMS.
Apply SOLID, Clean Architecture, and Domain-Driven Design principles; enforce them through code reviews and pair programming.
Drive AI-assisted development across the team including GitHub Copilot/Copilot Chat, prompt libraries, code-generation guardrails, secure prompt patterns, and test generation.
Integrate LLM-powered capabilities into applications (chat, summarization, classification, RAG) via Azure OpenAI/AWS Bedrock; wire PII/PCI/PHI guardrails at the prompt boundary.
Write and maintain unit, integration, and contract tests (xUnit.net/NUnit, Jasmine/Karma, Playwright) while targeting 80%+ coverage on core services.
Own CI/CD in Azure DevOps or GitHub Actions with Build -> Test -> Security Scan -> Deploy to AWS via CDK or Terraform.
Instrument with OpenTelemetry; publish metrics/traces to CloudWatch + Managed Grafana.
Partner with architects, product owners, and QA to break epics into deliverable sprint work; mentor 2-4 mid-level engineers.
Participate in on-call rotation for owned services (business-hours primary, off-hours secondary)."
We'll put each as .
Requirements bullet list: after "Requirements". Let's extract:
"8+ years professional software engineering; 5+ years on C#/.NET production applications.
Strong ASP.NET Core Web API and Entity Framework Core skills including async/await, dependency injection, minimal APIs, and middleware pipeline.
Angular 15+ production experience including components, RxJS, NgRx or signals, standalone components, reactive forms, lazy-loaded modules, and unit testing.
Deep relational database skills including schema design, indexing, query tuning, execution plans, stored procedures, migrations.
Experience in SQL Server and PostgreSQL or MySQL.
Practical AWS Cloud experience deploying real workloads including IAM, VPC, API Gateway, Lambda or ECS/EKS, RDS/Aurora, S3, SQS/SNS, CloudWatch, Secrets Manager, KMS.
Demonstrable command of SOLID principles, design patterns (Repository, CQRS, Mediator, Strategy, Factory), and Clean Architecture Layering.
Fluency in AI-assisted development using GitHub Copilot/Copilot Chat daily as a productivity tool including writing effective prompts, evaluating suggestions critically, generating tests, refactoring, and documenting via AI; ability to coach others in the same.
Experience integrating with LLM APIs (Azure OpenAI, AWS Bedrock, or OpenAI) and applying safety patterns (input validation, PII redaction, output filtering, prompt-injection defenses).
Strong Git workflow, code review discipline, and comfort with trunk-based or GitFlow branching.
Excellent written and verbal communication; ability to write design docs, ADRs, and runbooks."
We'll list each as .
Qualifications (Preferred): after "Preferred". Let's extract:
"AWS certification (Developer Associate, Solutions Architect Associate, or higher).
Hands-on experience with Docker + Kubernetes (EKS, Helm).
Experience with the following: IaC with AWS CDK (TypeScript/C#) or Terraform;
Event-driven architecture (EventBridge, Kafka/MSK, Kinesis);
Micro-front-end or module federation;
Vector databases (pgvector, OpenSearch, Pinecone) and RAG pipelines.
Regulated-industry background (banking, healthcare, insurance) with awareness of SOC 2, PCI-DSS, HIPAA constraints.
Contributions to open-source .NET or Angular projects."
Also note "This is a 12-month Contract position (possibly longer)." That's not a preference but could be included in About the role or maybe a separate section? Could be part of About the role. We'll incorporate that into About the role maybe after the summary. But we already have About the role paragraph; we could add a sentence about contract length. Let's add after the summary: "This is a 12-month contract position (possibly longer)." That is substantive.
Benefits: "Benefits available with TriCom during the contract period include low cost Medical/Dental, Paid time off, Paid Holidays, and 401(k) (with immediately-vested company match). H1-B Visa sponsorship is not available for this position. No third-parties, please."
We should keep the benefits details: low cost Medical/Dental, Paid time off, Paid Holidays, 401(k) with immediately-vested company match. Also note H1-B visa sponsorship not available and no third-parties. Those are not benefits but maybe we can include them in Benefits section as notes. The instruction: include Benefits section only if posting actually states them. It does state benefits. We'll include the benefits list. The H1-B note and third-parties note could be included as part of Benefits or maybe as a separate note but we can include them in Benefits as additional info.
We'll not include Pay or Schedule.
Now construct HTML:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes a summary paragraph (maybe "About the role")? The first paragraph: "Full-Stack .NET/Angular/AWS Developer Summary Our client is seeking a Developer to design and build full-stack enterprise Web applications from an on-premises engineering center, delivered to AWS Cloud. This developer will own features end-to-end - from database schema and C# service layer through Angular UI and drive AI-assisted engineering practices (GitHub Copilot, Copilot Chat, prompt-driven development), incorporating SOLID design, clean architecture, and secure, scalable Cloud-native systems." That's about the role. So we can have About the role
with that paragraph.
Responsibilities: list of bullet points after "Responsibilities". We'll extract each line after "Responsibilities". The bullet points start with "Design and build production-grade full-stack Web applications using ..." etc. We'll put each as
About the role
Full-Stack .NET/Angular/AWS Developer Summary Our client is seeking a Developer to design and build full-stack enterprise Web applications from an on-premises engineering center, delivered to AWS Cloud. This developer will own features end-to-end - from database schema and C# service layer through Angular UI and drive AI-assisted engineering practices (GitHub Copilot, Copilot Chat, prompt-driven development), incorporating SOLID design, clean architecture, and secure, scalable Cloud-native systems. This is a 12-month contract position (possibly longer).
Responsibilities
- Design and build production-grade full-stack Web applications using C#/.NET 8+, ASP.NET Core Web API, Entity Framework Core, and Angular 17+.
- Model, tune, and evolve relational schemas in SQL Server/PostgreSQL and integrate with Aurora/RDS in AWS.
- Architect for AWS deployment including API Gateway, Lambda, ECS/EKS on Fargate, S3, SQS/SNS, EventBridge, Secrets Manager, CloudWatch, and KMS.
- Apply SOLID, Clean Architecture, and Domain-Driven Design principles; enforce them through code reviews and pair programming.
- Drive AI-assisted development across the team including GitHub Copilot/Copilot Chat, prompt libraries, code-generation guardrails, secure prompt patterns, and test generation.
- Integrate LLM-powered capabilities into applications (chat, summarization, classification, RAG) via Azure OpenAI/AWS Bedrock; wire PII/PCI/PHI guardrails at the prompt boundary.
- Write and maintain unit, integration, and contract tests (xUnit.net/NUnit, Jasmine/Karma, Playwright) while targeting 80%+ coverage on core services.
- Own CI/CD in Azure DevOps or GitHub Actions with Build -> Test -> Security Scan -> Deploy to AWS via CDK or Terraform.
- Instrument with OpenTelemetry; publish metrics/traces to CloudWatch + Managed Grafana.
- Partner with architects, product owners, and QA to break epics into deliverable sprint work; mentor 2-4 mid-level engineers.
- Participate in on-call rotation for owned services (business-hours primary, off-hours secondary).
Requirements
- 8+ years professional software engineering; 5+ years on C#/.NET production applications.
- Strong ASP.NET Core Web API and Entity Framework Core skills including async/await, dependency injection, minimal APIs, and middleware pipeline.
- Angular 15+ production experience including components, RxJS, NgRx or signals, standalone components, reactive forms, lazy-loaded modules, and unit testing.
- Deep relational database skills including schema design, indexing, query tuning, execution plans, stored procedures, migrations.
- Experience in SQL Server and PostgreSQL or MySQL.
- Practical AWS Cloud experience deploying real workloads including IAM, VPC, API Gateway, Lambda or ECS/EKS, RDS/Aurora, S3, SQS/SNS, CloudWatch, Secrets