Lead Software Engineer

Virtusa

Hyderabad, Telangana, India

Must have

8+ years backend engineering, with production experience building authentication or session-management

components — not solely integrating an identity provider SDK.

Demonstrable understanding of session lifecycle, token binding and replay conditions, and the ability to

explain design decisions to a security reviewer.

Practical familiarity with NIST SP 800-63B, including its position on out-of-band authenticators.
Experience working inside an existing production application under change control, rather than building

from scratch.

Ability to work in the client's application stack (.NET or Java — confirm at screening).
Written communication strong enough to produce a specification that survives formal security review.

Nice to have

Insurance, payments or other regulated financial-services delivery.
PCI DSS exposure, particularly around changes upstream of an embedded payment gateway.
Experience with transactional email delivery and deliverability (SPF, DKIM, DMARC, bounce handling).

Languages

C# 10+, .NET 8 (or .NET Framework 4.8 if legacy)

ASP.NET Core MVC / Razor Pages, or ASP.NET MVC 5 / WebForms if legacy

ASP.NET Core Identity, Data Protection API, custom middleware pipeline

Entity Framework Core, Dapper, ADO.NET

IDistributedCache over Redis or SQL Server

ASP.NET Core Rate Limiting middleware (.NET 7+), AspNetCoreRateLimit

Razor, Handlebars.NET

Serilog or NLog with destructuring policies and redaction

IIS / Kestrel

xUnit or NUnit, RestSharp, SpecFlow

SQL (T-SQL, PL/SQL or DB2)

Git; branching and pull-request workflow on a shared repository under enterprise change control

Azure DevOps Boards or Jira; RAID, decision and dependency tracking

Cryptography

CSPRNG APIs — RandomNumberGenerator (.NET) or SecureRandom (Java)

Hashing for at-rest passcode storage — SHA-256/HMAC-SHA256, bcrypt, Argon2id or PBKDF2

Constant-time comparison — CryptographicOperations.FixedTimeEquals or MessageDigest.isEqual

TLS 1.2/1.3 configuration and certificate handling

Languages

C# / .NET ; SQL (T-SQL, PL/SQL or DB2)

Preferred

Python or Go for tooling and proof-of-concept work; PowerShell or Bash