Backend Engineer Job DescriptionRole: Backend Systems Engineer (Python / Distributed Systems)1. Role Overview

We are hiring a Backend Systems Engineer to build and scale the core infrastructure powering real-time AI interactions and secure data systems.

This is not a CRUD backend role. You will design and implement high-integrity, concurrent, data-heavy systems that must remain stable under real-world load and evolving product complexity.

You will own the backend foundation that future products depend on.

2. Key ResponsibilitiesA. Phase 1 (AI + Data Systems)

· Build chat backend with streaming responses (SSE/WebSockets)

· Design and implement retrieval pipelines (embeddings, vector search)

· Build indexing and search systems (full-text + fallback strategies)

· Handle async processing (background jobs, non-blocking tasks)

· Ensure low-latency response pipelines under load

· Design robust error handling and fallback mechanisms

B. Phase 2 (Secure Data + Identity Systems)

· Build secure data vault services (documents, records, structured data)

· Design selective access and sharing APIs

· Implement consent logging and audit trails

· Build verification flows (time-bound access, tokens, permissions)

· Ensure strong data isolation and access control

· Design systems for long-term data integrity and traceability

3. Required Technical SkillsCore Backend (Must Have)

· Python (strong, production-level)

· FastAPI (or equivalent async frameworks)

· Async programming (async/await, event loops)

Concurrency & Data Integrity (Critical)

· Strong understanding of:

o race conditions

o locks and transactions

o concurrent request handling

· Experience with:

o database locking (e.g., SELECT FOR UPDATE)

o idempotency

o sequence/order guarantees

Database Expertise (Non-Negotiable)

· PostgreSQL (deep understanding)

· Indexing strategies:

o GIN indexes

o composite indexes

· Query optimization

· Full-text search (FTS) + fallback approaches

Must be comfortable working without relying only on ORM abstractions.

API Design

· REST API design

· Authentication & authorization flows

· Proper status handling (400 vs 404 vs 500)

· Input validation and defensive programming

System Design

· Modular service architecture

· Clean separation of concerns

· Scalable data models

4. AI / Data Pipeline Skills (Required)

· Understanding of:

o embeddings

o vector search

o retrieval pipelines

· Experience with:

o vector databases (Qdrant / pgvector or similar)

o chunking and indexing strategies

Must be able to reason about: - latency vs accuracy tradeoffs - retrieval quality - system performance under scale

5. Performance & Reliability

· Background processing (non-blocking tasks)

· Request timeouts and cancellation handling

· Connection reuse and resource management

· Logging and observability

Must be able to: - identify bottlenecks - optimize slow queries - reduce unnecessary blocking operations

6. Security Awareness (Important)

· Access control (user-level ownership checks)

· Token handling (secure storage and validation)

· Data exposure prevention

· Basic encryption concepts

You are not expected to be a cryptography expert, but you must think defensively.

7. Product Thinking Requirements

You must be able to:

· Build systems that handle real-world edge cases

· Design APIs that frontend teams can reliably use

· Balance speed vs correctness vs scalability

· Anticipate failure scenarios

This role requires system thinking, not just implementation.

8. What You Will Work With

· Real-time streaming systems

· Retrieval pipelines and search systems

· Structured and unstructured data storage

· High-concurrency APIs

· Secure data access systems (Phase 2)

9. What We Are NOT Looking For

· CRUD-only backend developers

· Developers who rely entirely on ORMs

· People with no async/concurrency experience

· Developers who cannot reason about data integrity

10. Success Criteria

You will be successful in this role if you can:

· Build stable backend systems under concurrent load

· Prevent data corruption and race conditions

· Deliver performant and scalable APIs

· Design systems that can evolve across multiple products

11. Interview Evaluation Criteria

Candidates will be evaluated on:

1. Understanding of concurrency and race conditions

2. Database design and optimization

3. API design quality

4. System design thinking

5. Debugging and problem-solving ability

12. Sample Screening Questions

1. “Explain a race condition and how you would fix it in a production system.”

2. “How would you design a system that handles concurrent writes safely?”

3. “How would you optimize a slow search query in PostgreSQL?”

13. Role Type

· Full-time

· High ownership role

· Core engineering position

14. Final Note

This is a foundational engineering role.

The backend engineer defines the stability, scalability, and correctness of the entire system. Weak backend = system failure, regardless of frontend or AI quality.

We are looking for engineers who can grow across systems without needing replacement.

Pay: ₹350,000.00 - ₹800,000.00 per year

Work Location: In person