CoreHRx Jobs

Apply in one click, save jobs and take free mock tests.

Register free Log in
Hiring? Post jobs with CoreHRx
My account
user

View & update profile

Backend Developer

Not disclosed

Full time On-site
Experience
3–5 years
Location
Ahmedabad
Work mode
On-site
Posted 15 days ago

Free · takes a minute · your resume fills your profile

CoreHRx never asks candidates for money. If anyone does, .

Role at a glance

You will
  • TechAppForce (TAF) is a developer-first, metadata-driven low-code platform that helps businesses build enterprise-grade B2B applications…
  • The platform handles the heavy infrastructure — authentication, multi-tenancy, workflows, CRUD APIs, permission controls, audit trails — so…
  • TAF is built on .NET Core with a metadata-driven architecture that auto-generates REST APIs, powers a visual workflow engine (ELSA), and…
Experience
3–5 years
Must-have skills
.NET CoreMicroservicesMicrosoft SQL ServerPostgreSQLREST API DevelopmentSQL
Work mode
On-site

How well do your skills match this job?

Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.

Job description

TECH EXTENSOR Backend Developer .NET Core | CQRS | Microservices | Metadata-Driven Platform Engineering Experience 3–5 Years Location Ahmedabad (Onsite) Employment Type Full-Time Team Product — TechAppForce (TAF) Platform
About the Role
TechAppForce (TAF) is a developer-first, metadata-driven low-code platform that helps businesses build enterprise-grade B2B applications significantly faster than traditional development. The platform handles the heavy infrastructure — authentication, multi-tenancy, workflows, CRUD APIs, permission controls, audit trails — so that developers building on top of it can stay focused on business logic. TAF is built on .NET Core with a metadata-driven architecture that auto-generates REST APIs, powers a visual workflow engine (ELSA), and supports dual database structures across SQL Server and PostgreSQL. This is a genuinely complex, generic-thinking backend challenge — not a typical CRUD application. The platform is at a critical juncture, moving from internal-use to external customer adoption. We need a backend developer who can take ownership of platform modules, extend the metadata engine, and help make TAF faster, more reliable, and more extensible. This is not a ticket-execution role — we need someone who thinks platform-first, not feature-first.
What You'll Own Platform Backend Development Build and extend core TAF platform modules — metadata engine, API auto-generation layer, permission and role management, multi-tenancy infrastructure Design and implement features generically — if a solution only works for one use case, it does not belong in the platform Write clean, maintainable .NET Core code following CQRS patterns, separation of concerns, and domain-driven design principles Extend and maintain REST API auto-generation capabilities — new entity types, field types, and relationship patterns
CQRS, Microservices & Architecture Implement CQRS command/query separation across platform modules — as a structural discipline, not a buzzword Build and maintain microservice boundaries within TAF — owning service contracts, message patterns, and inter-service communication Apply event-driven patterns where appropriate — understanding when events improve decoupling vs. when they add unnecessary complexity Actively participate in architecture decisions with opinions grounded in platform-level thinking
Database & Data Layer Write optimised SQL for SQL Server and PostgreSQL — complex queries, stored procedures, index strategy, query execution plan analysis Design database schemas that support metadata-driven flexibility — structures that represent arbitrary entity configurations without schema changes Own data migration scripts, schema versioning, and backward-compatible database changes Implement EF Core patterns appropriate for a platform context — including knowing when raw SQL is the right call
Workflow & Integration Engine Work with and extend the ELSA workflow engine — building new activity types, workflow triggers, and integration connectors Build and maintain external API integration capabilities — webhook handling, OAuth flows, third-party connector patterns Ensure workflow execution is reliable, idempotent, and recoverable — distributed systems failure modes are a real concern
Quality & Delivery Write unit and integration tests as part of how you know your code is correct — not as an afterthought Meet sprint commitments — if a commitment is at risk, raise it early, not on the due date Participate actively in sprint planning, standups, and code reviews Use AI coding tools actively (GitHub Copilot, Claude, Cursor) for code generation, test writing, and documentation — while owning everything that ships
Must-Have Skills
We will test these in the technical round. If you cannot demonstrate them with real examples, this role is not the right fit right now. 3–5 years of backend development experience, primarily in .NET Core or .NET 6/7/8 Solid understanding and practical implementation of CQRS — can explain the pattern and the problems it solves, not just name it Microservices experience — has built or maintained services with clear boundaries, not just modular monoliths Strong SQL skills across SQL Server and/or PostgreSQL — complex queries, schema design, performance thinking REST API design and implementation — clean, versioned, documented APIs Ability to think generically — can identify the reusable, configurable solution rather than defaulting to hardcoded fixes Genuine ownership mindset — takes a feature from requirement to production without constant hand-holding
Good to Have
Low-code or platform engineering experience — has built infrastructure that other developers use Metadata-driven architecture — systems where behaviour is configuration-driven rather than code-driven ELSA workflow engine or any workflow/BPM engine integration Entity Framework Core — advanced usage beyond basic code-first migrations Multi-tenant SaaS architecture patterns — data isolation, tenant configuration, shared infrastructure Event-driven architecture — message queues, event sourcing, Kafka or RabbitMQ Docker / containerisation basics for local development and deployment Tech Extensor | Ahmedabad, Gujarat | techextensor.com | techappforce.com

Key skills

Required

.NET CoreMicroservicesMicrosoft SQL ServerPostgreSQLREST API DevelopmentSQL

Preferred

DockerEvent-Driven ArchitectureKafkaMessage QueuesRabbitMQ

Soft skills

Ownership

Job market insights

194active .NET Core jobs in India
6active Microservices jobs in Ahmedabad
15active Microsoft SQL Server jobs in Ahmedabad
192 more open jobs at Not disclosed

Most IT Jobs posts in Ahmedabad ask for 3–6 years of experience (41% of 106 that say).

Hiring most for IT Jobs in Ahmedabad

  • AECOM11 open jobs
  • Tech Holding7 open jobs
  • Techblocks5 open jobs

Jobs asking for .NET Core in India also ask for

  • C#78%
  • Microsoft Azure61%
  • Microsoft SQL Server51%
  • CI/CD50%
  • Microservices44%

From live job posts on CoreHRx, updated 21 Nov 2026. Skill figures count posts that list their skills; salary figures only posts that show a salary.

Questions about this job

How much experience does this job need?

The post asks for 3–5 Yrs experience.

Where is this job based?

In Ahmedabad (on-site).

What kind of job is this?

It is a full time job.

This guide is for C# and .NET developers in India preparing for interviews, from freshers applying for a first role at a Pune IT services firm or a Bengaluru product company to engineers with several years of experience moving into senior positions. It has 60 questions in three levels: language basics such as types, OOP and collections; then everyday topics like LINQ, async and await, ASP.NET Core middleware, dependency injection and Entity Framework Core; and finally senior topics such as the thread pool, garbage collection, performance and design. Each answer is written the way a strong candidate would say it, with C# code where it helps. The answers are based on C# 12 and .NET 8, and most of them apply to later versions too. Try answering each question aloud before you read the answer, then take the mock test.

Questions you may be asked

  1. What is the difference between C#, .NET and the CLR?
  2. What is the difference between value types and reference types in C#?
  3. What are boxing and unboxing, and why should you avoid them in hot code?
  4. Why are strings immutable in C#, and when should you use StringBuilder?

Get IT jobs in Ahmedabad by email

Create a free profile and we email you new IT jobs in Ahmedabad, at most once a week.

Similar jobs

Free · takes a minute · your resume fills your profile