Description review
Sr C# Developer/Support
Everest Technologies · United States · back to the listing
HR standards
62/100
needs work
Title ↔ description
79/100
solid
Reads as
Backend Engineer
100% confident
What this role officially is
software developer — ESCO, the EU occupation classification
Software developers implement or program all kinds of software systems based on specifications and designs by using programming languages, tools, and platforms.
Also known as: application developer, application programmer, solutions developer, programmer, software specialist, application software developer
How others title the same work
Large employers
- Software Engineer - OpenStack Canonical
- C, Golang Software Engineer working on dqlite, a Raft extension for SQLite Canonical Ltd.
- Containerization & Virtualisation Engineer Canonical Ltd.
- Go (Golang) Software Engineer, Developer Tooling and Containers Canonical Ltd.
- Golang Engineer Canonical Ltd.
Startups
- Anterior (Sequoia-backed, Series B) | Senior Member of Technical Staff | On-Site (New York, NY) | Full Time | $230,000–$300,000 + equity Anterior (Sequoia-backed, Series B)
- BitPay | Senior Backend Software Developer | Atlanta, GA | REMOTE (US) | BitPay
- Distributed Systems Engineer Beam
- Software Engineer, Platform Beam
- Blaine, WA | CaseLight Systems Inc. (CSI) | Solo Founder | Remote (US Only) | Founding Systems Engineer | FULL EQUITY (30% Stake) Blaine, WA
What the listing never says
- No pay range published. Candidates cannot tell whether applying is worth their time. Pay transparency
The listing, marked up
Nothing in the wording of this listing tripped a check. The scores above still judge how complete and coherent it is.
This is a remote position.
About the role
This is a versatile senior C# pod, not four slots on one project. These developers rotate across multiple Client workstreams, leaning into migration/conversion support when that work surges and picking up other C# projects otherwise. The role rewards people who ramp fast, context-switch cleanly, and are comfortable across different codebases and problem types. Frame it as flexible senior muscle, not bench or generic staff augmentation.
What you will do
• Move across multiple Client C# workstreams as priorities shift.
• Support the Java-to-C# migration effort during peak periods: reviewing and finishing AI-converted code, building out C# services, proving parity.
• Pick up feature development, defect work, and enhancements on other C# projects between migration surges.
• Ramp quickly on unfamiliar codebases and deliver with minimal hand-holding.
Must have
•
Strong C# / .NET:8+ years, .NET Core / .NET 6+, ASP.NET Core, dependency injection, async/await.
•
Adaptability:demonstrated history of working across multiple projects, clients, or codebases; comfortable ramping fast and switching context. This is a stated requirement, not a footnote.
•
Data and API fundamentals:SQL, EF Core or Dapper, REST APIs.
•
Self-direction:delivers independently across changing assignments.
Nice to have (strong pluses)
• Code migration or application modernization experience (including framework upgrades such as .NET version migrations). Directly relevant to migration overflow.
• Java familiarity, enough to help on conversion work when needed. Valued, not gated.
•AI coding tool experience.
• Cloud (Azure or AWS), containerization, CI/CD.
Originally posted on Himalayas
About the role
This is a versatile senior C# pod, not four slots on one project. These developers rotate across multiple Client workstreams, leaning into migration/conversion support when that work surges and picking up other C# projects otherwise. The role rewards people who ramp fast, context-switch cleanly, and are comfortable across different codebases and problem types. Frame it as flexible senior muscle, not bench or generic staff augmentation.
What you will do
• Move across multiple Client C# workstreams as priorities shift.
• Support the Java-to-C# migration effort during peak periods: reviewing and finishing AI-converted code, building out C# services, proving parity.
• Pick up feature development, defect work, and enhancements on other C# projects between migration surges.
• Ramp quickly on unfamiliar codebases and deliver with minimal hand-holding.
Must have
•
Strong C# / .NET:8+ years, .NET Core / .NET 6+, ASP.NET Core, dependency injection, async/await.
•
Adaptability:demonstrated history of working across multiple projects, clients, or codebases; comfortable ramping fast and switching context. This is a stated requirement, not a footnote.
•
Data and API fundamentals:SQL, EF Core or Dapper, REST APIs.
•
Self-direction:delivers independently across changing assignments.
Nice to have (strong pluses)
• Code migration or application modernization experience (including framework upgrades such as .NET version migrations). Directly relevant to migration overflow.
• Java familiarity, enough to help on conversion work when needed. Valued, not gated.
•AI coding tool experience.
• Cloud (Azure or AWS), containerization, CI/CD.
Originally posted on Himalayas