Scavenger Tech

Executive Summary

You will design, develop, and maintain backend and system-level components aligned with approved enterprise architecture, security standards, and governance frameworks. You’ll deliver features that meet functional and non-functional requirements, follow secure coding practices, and integrate cleanly across our ecosystem: Azure, APIs, databases, and CI/CD pipelines.

You will operate within defined architectural boundaries and collaborate with Architects, Product Owners, QA, DevSecOps, and business stakeholders to ship high-quality, scalable, secure solutions.  You must have a secure-by-design mindset (OWASP Top 10, RBAC, identity integration) for this role.

Role Purpose

Design, build, and maintain backend/system-level components aligned with architectural standards.

About the project 

We’re taking ownership of a large, mission-critical enterprise platform currently operated by an external vendor. The system is live and security-sensitive, and we’re modernizing it over time:

• Primary backend stack: C# / .NET (6+), with most new work on .NET 8 (LTS)
• Legacy areas exist: ASP.NET Framework 4.8 and some WCF
• Cloud: Microsoft Azure
• Data: SQL Server primarily, some MySQL
• Frontend exists (React/Angular), but this role is backend/system-level

• Documentation is mixed due to the transition; part of the work is improving clarity as you go.

   

Core Responsibilities

1) Software Development & Implementation

• Develop backend services, APIs, and system components based on approved backlog items and technical designs.
• Translate user stories and functional requirements into scalable solutions.
• Implement business logic following clean architecture and principles.
• Follow coding standards, architectural guidelines, and agreed design patterns.

2) Code Quality & Maintainability

• Write clean, maintainable, testable, well-documented code.
• Perform peer reviews and address review feedback.
• Refactor legacy code where needed to improve performance and maintainability.
• Maintain strong version control discipline: branching strategy, pull requests, merges.

3) Testing & Quality Assurance

• Develop and maintain unit tests using approved frameworks (xUnit / NUnit / MSTest).
• Use mocking frameworks appropriately (e.g., Moq/NSubstitute equivalents).
• Participate in integration testing and support QA during testing cycles.
• Meet quality gates (coverage/standards) before release.
• Support debugging, root-cause analysis, and defect resolution.

4) Security & Compliance

• Apply secure coding practices aligned with OWASP Top 10.
• Identify and mitigate vulnerabilities; follow DevSecOps quality controls.
• Correctly handle authentication, authorization, encryption, and data protection.
• Implement RBAC and identity-based access patterns (JWT/OAuth2; Entra ID integration where applicable).
• Comply with mandatory SAST scanning gates prior to release.

5) Performance & Reliability

• Optimize database queries and system performance (SQL Server/MySQL).
• Build scalable, resilient services and APIs.
• Implement logging/monitoring/exception handling best practices (e.g., Application Insights, Serilog).
• Use performance profiling techniques when needed to diagnose bottlenecks.

6) DevOps & Deployment Support

• Support CI/CD pipeline integration and delivery workflows (Azure DevOps).
• Assist in staging and production deployments under governance checkpoints.
• Participate in troubleshooting production incidents when required.

7) Cross-Functional Collaboration

• Work closely with Solution Architects, Product Owners, QA, DevSecOps, and UI/UX teams.
• Escalate technical risks and architectural concerns early and clearly.

Authority

• Own implementation decisions within approved architectural boundaries.
• Cannot redefine scope or bypass architecture/security standards.
• Must escalate technical risks, architectural concerns, or scope-impacting issues to the Architect and Product Owner.
• Cannot approve production deployment outside defined governance checkpoints.

Required Qualifications

Education

• Bachelor’s degree in Computer Science / Software Engineering / Information Systems (or similar).
• Master’s degree is a plus.

Experience

• 5+ years backend development experience.
• Proven experience delivering enterprise-grade applications.
• Experience working in Agile/Scrum environments.
• Experience with production-grade Azure-hosted applications.

Required Technical Stack

Core Technologies

• C# / .NET Core / .NET 6+ (most new work on .NET 8 LTS)
• ASP.NET Core Web API
• Entity Framework and/or other ORM tools
• SQL Server (advanced querying and performance tuning mindset)

API & Integration

• RESTful APIs
• Data exchange: JSON / XML
• API auth: JWT, OAuth2, identity integration (Entra ID)

Cloud & DevOps

• Microsoft Azure (App Services, Storage, Functions)
• Azure DevOps (CI/CD pipelines)
• Git

Security

• OWASP Top 10 awareness
• Secure coding best practices
• RBAC implementation patterns

Testing

• xUnit / NUnit / MSTest
• Mocking frameworks
• Unit + integration testing practices

Technical Awareness

• Microservices architecture basics
• Logging/monitoring tools (Application Insights, Serilog, etc.)
• Docker basics (preferred)
• CI/CD best practices
• Performance profiling techniques

Core Competencies

Technical

• Strong problem solving and analytical skills
• Code optimization and debugging expertise
• Understanding of system design principles
• Secure development mindset

Behavioral

• Accountability and ownership
• Structured thinking
• Attention to detail
• Ability to work under pressure
• Clear communication with technical and non-technical stakeholders
• Continuous learning mindset

Maturity / Level Expectations

• Lead technical modules and drive them to completion.
• Mentor less experienced engineers when needed.
• Participate in design discussions and contribute improvements.
• Review critical code changes and uphold engineering standards.

Recommended Certifications (Nice-to-have)

• AZ-204 (Azure Developer Associate)
• AZ-900 (Azure Fundamentals)
• Secure coding / OWASP training
• Microsoft security certifications (optional)

Interview Process

1. 20–30 min intro call
2. Technical interview (system design + deep .NET/API/SQL + security mindset)
3. Final discussion + offer

Executive Summary

You will design, develop, and maintain backend and system-level components aligned with approved enterprise architecture, security standards, and governance frameworks. You’ll deliver features that meet functional and non-functional requirements, follow secure coding practices, and integrate cleanly across our ecosystem: Azure, APIs, databases, and CI/CD pipelines.

You will operate within defined architectural boundaries and collaborate with Architects, Product Owners, QA, DevSecOps, and business stakeholders to ship high-quality, scalable, secure solutions.

Role Purpose

Design, build, and maintain backend/system-level components aligned with architectural standards.

About the project (stealth, but clear)

We’re taking ownership of a large, mission-critical enterprise platform currently operated by an external vendor. The system is live and security-sensitive, and we’re modernizing it over time:

• Primary backend stack: C# / .NET (6+), with most new work on .NET 8 (LTS)
• Legacy areas exist: ASP.NET Framework 4.8 and some WCF
• Cloud: Microsoft Azure
• Data: SQL Server primarily, some MySQL
• Frontend exists (React/Angular), but this role is backend/system-level

• Documentation is mixed due to the transition; part of the work is improving clarity as you go.

   

Core Responsibilities

1) Software Development & Implementation

• Develop backend services, APIs, and system components based on approved backlog items and technical designs.
• Translate user stories and functional requirements into scalable solutions.
• Implement business logic following clean architecture and principles.
• Follow coding standards, architectural guidelines, and agreed design patterns.

2) Code Quality & Maintainability

• Write clean, maintainable, testable, well-documented code.
• Perform peer reviews and address review feedback.
• Refactor legacy code where needed to improve performance and maintainability.
• Maintain strong version control discipline: branching strategy, pull requests, merges.

3) Testing & Quality Assurance

• Develop and maintain unit tests using approved frameworks (xUnit / NUnit / MSTest).
• Use mocking frameworks appropriately (e.g., Moq/NSubstitute equivalents).
• Participate in integration testing and support QA during testing cycles.
• Meet quality gates (coverage/standards) before release.
• Support debugging, root-cause analysis, and defect resolution.

4) Security & Compliance

• Apply secure coding practices aligned with OWASP Top 10.
• Identify and mitigate vulnerabilities; follow DevSecOps quality controls.
• Correctly handle authentication, authorization, encryption, and data protection.
• Implement RBAC and identity-based access patterns (JWT/OAuth2; Entra ID integration where applicable).
• Comply with mandatory SAST scanning gates prior to release.

5) Performance & Reliability

• Optimize database queries and system performance (SQL Server/MySQL).
• Build scalable, resilient services and APIs.
• Implement logging/monitoring/exception handling best practices (e.g., Application Insights, Serilog).
• Use performance profiling techniques when needed to diagnose bottlenecks.

6) DevOps & Deployment Support

• Support CI/CD pipeline integration and delivery workflows (Azure DevOps).
• Assist in staging and production deployments under governance checkpoints.
• Participate in troubleshooting production incidents when required.

7) Cross-Functional Collaboration

• Work closely with Solution Architects, Product Owners, QA, DevSecOps, and UI/UX teams.
• Escalate technical risks and architectural concerns early and clearly.

Authority

• Own implementation decisions within approved architectural boundaries.
• Cannot redefine scope or bypass architecture/security standards.
• Must escalate technical risks, architectural concerns, or scope-impacting issues to the Architect and Product Owner.
• Cannot approve production deployment outside defined governance checkpoints.

Required Qualifications

Education

• Bachelor’s degree in Computer Science / Software Engineering / Information Systems (or similar).
• Master’s degree is a plus.

Experience

• 5+ years backend development experience.
• Proven experience delivering enterprise-grade applications.
• Experience working in Agile/Scrum environments.
• Experience with production-grade Azure-hosted applications.

Required Technical Stack

Core Technologies

• C# / .NET Core / .NET 6+ (most new work on .NET 8 LTS)
• ASP.NET Core Web API
• Entity Framework and/or other ORM tools
• SQL Server (advanced querying and performance tuning mindset)

API & Integration

• RESTful APIs
• Data exchange: JSON / XML
• API auth: JWT, OAuth2, identity integration (Entra ID)

Cloud & DevOps

• Microsoft Azure (App Services, Storage, Functions)
• Azure DevOps (CI/CD pipelines)
• Git

Security

• OWASP Top 10 awareness
• Secure coding best practices
• RBAC implementation patterns

Testing

• xUnit / NUnit / MSTest
• Mocking frameworks
• Unit + integration testing practices

Technical Awareness

• Microservices architecture basics
• Logging/monitoring tools (Application Insights, Serilog, etc.)
• Docker basics (preferred)
• CI/CD best practices
• Performance profiling techniques

Core Competencies

Technical

• Strong problem solving and analytical skills
• Code optimization and debugging expertise
• Understanding of system design principles
• Secure development mindset

Behavioral

• Accountability and ownership
• Structured thinking
• Attention to detail
• Ability to work under pressure
• Clear communication with technical and non-technical stakeholders
• Continuous learning mindset

Maturity / Level Expectations

• Lead technical modules and drive them to completion.
• Mentor less experienced engineers when needed.
• Participate in design discussions and contribute improvements.
• Review critical code changes and uphold engineering standards.

Recommended Certifications (Nice-to-have)

• AZ-204 (Azure Developer Associate)
• AZ-900 (Azure Fundamentals)
• Secure coding / OWASP training
• Microsoft security certifications (optional)

Interview Process

1. 20–30 min intro call
2. Technical interview (system design + deep .NET/API/SQL + security mindset)
3. Final discussion + offer

The role

We’re building an internal engineering team to take ownership of a large, mission-critical public sector / enterprise platform currently operated by an external vendor. The system is live and has real operational constraints: reliability, auditability, controlled releases, and security gates are part of day-to-day work.

Technically, it’s a hybrid:

• Legacy areas: ASP.NET Framework 4.8 / WCF
  
   
• Modern services: .NET 8 (LTS)
  
   
• Releases: still partly manual today (with approvals), moving toward CI/CD
  
   

We’re also transitioning to a CIS-based team, so documentation isn’t perfect everywhere. We’re looking for developers who can still move fast safely: read code, trace behavior, validate assumptions, and leave clear notes for the next person.

This role is for a developer first—but someone who also cares about how software ships and runs.

What you’ll do

• Build and maintain backend services in C# / .NET 8 (LTS).
  
   
• Work in legacy code where needed (ASP.NET 4.8 / WCF) and help carve out cleaner services over time.
  
   
• Contribute to safer delivery:
  
   
  • help replace manual release steps with repeatable CI/CD
    
     
  • improve deployment traceability (logs, approvals, rollbacks)
    
     
  • tighten “definition of done” around testing and release readiness
    
     
• Build or integrate with supporting services (some are in Python) and internal tooling/scripts.
  
   
• Work with modern UI codebases (React and/or Angular)—you don’t have to be a UI specialist, but you should be comfortable contributing when needed.
  
   
• Write and tune queries across SQL Server and MySQL.
  
   
• Operate in a strict SDLC:
  
   
  • PR-based workflow, branch protection
    
     
  • peer reviews
    
     
  • mandatory security scanning (SAST) before release
    
     

What we’re looking for

• 3–6 years of professional software engineering experience (or equivalent impact).
  
   
• Strong C# / .NET fundamentals and comfort working in large codebases.
  
   
• Experience in enterprise or government-style environments: regulated systems, high-availability, “no surprises” releases, audit trails, change control, etc.
  
   
• Practical exposure to CI/CD and environments (you’ve worked with pipelines, not necessarily built everything from scratch).
  
   
• Comfort working across a broader stack:
  
   
  • Python (reading/writing scripts, small services, integrations)
    
     
  • React/Angular (basic-to-solid contributions)
    
     
• Strong debugging instincts: you can investigate issues without perfect documentation and still deliver clean fixes.
  
   

Nice to have

• Azure experience (any of: App Services, AKS, Functions, Key Vault, networking basics).
  
   
• Observability experience (App Insights, ELK, Grafana/Prometheus, etc.).
  
   
• Experience modernizing legacy systems (WCF → APIs, monolith → services, etc.).
  
   
• Security-minded habits (secrets handling, least privilege, thinking in blast radius).
  
   

The honest part

• Some documentation is incomplete due to the vendor → internal transition and CIS team migration.
  
   
• You’ll see legacy code.
  
   
• The upside: you’ll be part of the group that improves the system’s clarity, delivery quality, and long-term maintainability.
  
   

Apply with: 2–3 bullets on (1) enterprise/public sector systems you worked on, (2) what you shipped in .NET, and (3) one example where you improved delivery (pipeline, release process, monitoring, or operational stability).

What we’re building

We’re creating a small, elite engineering hub in CIS to take ownership of a large, mission-critical enterprise platform currently operated by an external vendor. The system is live, security-sensitive, and mid-modernization: legacy parts exist (ASP.NET 4.8/WCF), newer services are already on .NET 8, and delivery is moving toward fully automated CI/CD with strict quality/security gates.

We already have:

• CTO / Exec sponsor driving strategy and stakeholder alignment
  
   
• Lead Architect driving target architecture and modernization design
  
   

Now we need the person who makes it all actually happen day-to-day.

The role

You’re the execution + people leader for the CIS hub. You’ll hire and run the team, translate executive priorities into a sane delivery plan, and keep engineering moving without burning people out. You’re technical enough that engineers can’t hand-wave you — but your core job is leadership, delivery, and building a team that ships.

What you’ll do

• Build the hub: hire and grow a team of .NET and Full Stack engineers (and a DevOps profile as needed). Own the pipeline from sourcing → screening → offer.
  
   
• Run delivery: planning, prioritization, sprint/kanban execution, dependency management, and unblocking. Keep scope honest and outcomes measurable.
  
   
• Bridge stakeholders and engineers: turn business goals into clear engineering work; communicate tradeoffs, timelines, and risk in plain English.
  
   
• Protect quality and security: enforce PR culture, branch protection, definition of done, and security scanning gates (SAST) as part of release readiness.
  
   
• Operationalize engineering: improve how work moves through the system (docs, runbooks, incident follow-ups, handover from vendor knowledge).
  
   
• Keep a technical pulse: you won’t code every day, but you can run code-level interviews, review designs at a high level, and spot risky shortcuts early.
  
   

What “good” looks like in the first 3–6 months

• Team hired and onboarded (initial 5–8, scaling toward 10–15) with consistent engineering standards
  
   
• Delivery rhythm established (predictable planning, clean backlog, fewer surprises)
  
   
• Clear ownership boundaries and handover plan from the vendor
  
   
• CI/CD adoption progressing (more services/releases under pipeline, fewer manual steps)
  
   
• Documentation and runbooks improving as part of normal delivery (not a separate “later” project)
  
   

What we’re looking for

• 8+ years in software engineering, with 3+ years managing teams (EM / Delivery Director / Head of Engineering type roles)
  
   
• Strong background in C# / .NET (you can interview seniors and judge tradeoffs)
  
   
• Proven experience hiring and leading remote teams in CEE
  
   
• Comfortable operating in enterprise environments: gated releases, auditability, security requirements
  
   
• Strong written/spoken English and calm executive communication
  
   

Nice to have

• Azure delivery experience (not architecture-heavy, but real-world shipping)
  
   
• Experience with modernization programs (legacy → modern, vendor takeover, platform re-platforming)
  
   
• Familiarity with React/Angular and/or Python (integration context)

The role

We’re taking over core development of a large, real-time public safety / mobility platform. It’s a hybrid system: you’ll work in a mix of legacy and modern code while we move the center of gravity toward .NET 8 and a clean CI/CD delivery model.

We’re also transitioning to a CIS-based team, and the truth is: the documentation isn’t perfect everywhere. You don’t need everything spelled out if you know how to read a system, ask smart questions, and improve things as you go.

If you like big systems, real production constraints, and modernization work that actually matters—this will feel interesting.

What you’ll do

• Build backend services in C# / .NET 8 (LTS).
  
   
• Maintain/refactor legacy areas (ASP.NET 4.8 / WCF) safely as we modernize.
  
   
• Build front-end features in React and/or Angular (TypeScript) for operational dashboards.
  
   
• Write and optimize queries across SQL Server and MySQL.
  
   
• Work in a strict SDLC:
  
   
  • PR-based workflow
    
     
  • branch protection (no pushing to main)
    
     
  • peer reviews
    
     
  • mandatory SAST scans before release
    
     
• Help move releases from “manual steps” toward CI/CD with logging, traceability, and rollback.
  
   
• Integrate with adjacent services (some Python) and mobile clients.
  
   

What we’re looking for

• 5+ years in production software engineering (enterprise or high-availability systems).
  
   
• Strong C# / .NET skills; comfortable touching ASP.NET 4.8 while writing most new work in .NET 8.
  
   
• Solid experience with React and/or Angular.
  
   
• Strong relational DB fundamentals (SQL Server, MySQL).
  
   
• You can handle imperfect docs and still deliver: you investigate, validate, and improve the system.
  
   

Nice to have

• Python integration work, mobile-facing APIs, or experience with real-time dashboards.
  
   
• Observability/performance tuning experience.
  
   
• Prior modernization experience (monolith → services, legacy cleanup, etc.).
  
   

A quick honesty section

• You’ll see messy parts. We’re not hiding that.
  
   
• You’ll also be part of the team that fixes them—steadily and safely.
  
   

Apply with: 2–3 bullets on systems you’ve worked on (scale, tech stack, what you shipped).