Backend Lead

Job Requirements

• 3+ years of professional backend development experience with Python, and working knowledge

of TypeScript.

• Solid understanding of Python frameworks (e.g., FastAPI, Django, Flask) and TypeScript-based

backend frameworks (e.g., Node.js, NestJS, Express)

• Hands-on experience using Temporal to design and orchestrate workflows.

• Proven expertise in data extraction, normalization, and deduplication.

• Strong experience implementing proxy solutions and navigating bot-detection mechanisms (e.g.,

Cloudflare).

• Experience with Docker, containerized deployments, and cloud platforms such as GCP or Azure.

• Proficiency with database technologies including MongoDB and Elasticsearch.

• Demonstrated experience designing and maintaining scalable, high-performance APIs.

• Working knowledge of software testing methodologies (unit, integration, and end-to-end).

• Familiarity with CI/CD pipelines and version control systems like Git.

• Strong problem-solving abilities, attention to detail, and comfort working in agile, fast-paced

environments.

• Excellent communication skills with the ability to operate effectively in ambiguous or loosely

defined problem spaces.

Ctruh is looking for a deeply technical, hands-on Senior Backend Engineer - someone who can architect systems in the morning, write production-grade code in the afternoon, and scale infrastructure to power millions of 3D and XR experiences.

You will own the entire backend ecosystem: architecture, APIs, databases, infrastructure, performance, and reliability. This is not an oversight or management-only position - it is a builder’s role where you design, code, deploy, and optimize mission-critical systems.

You will make foundational decisions, build distributed systems that handle massive 3D processing workloads, and lead backend engineering direction as the platform scales globally.

What You’ll Build

1. System Architecture & Design

• Architect highly scalable backend systems from the ground up
• Define technology choices: frameworks, databases, queues, caching layers
• Evaluate microservices vs monoliths based on product stage
• Design REST, GraphQL, and real-time WebSocket APIs
• Build event-driven systems for asynchronous processing
• Architect multi-tenant systems with strict data isolation
• Maintain architectural documentation and technical specifications

2. Core Backend Services

• Build high-performance APIs for 3D content, XR experiences, analytics, and user interactions
• Create 3D asset processing pipelines for uploads, conversions, and optimization
• Develop distributed job workers for CPU/GPU-intensive tasks
• Build authentication and authorization systems (RBAC)
• Implement billing, subscription, and usage metering
• Build secure webhook systems and third-party integration APIs
• Create real-time collaboration features via WebSockets or SSE

3. Data Architecture & Databases

• Design scalable schemas for 3D metadata, XR sessions, and analytics
• Model complex product catalogs with variants and hierarchies
• Implement Redis-based caching strategies
• Build search and indexing systems (Elasticsearch, Algolia)
• Architect ETL pipelines and data warehouses
• Implement sharding, partitioning, and replication strategies
• Design backup, restore, and disaster recovery workflows

4. Scalability & Performance

• Build systems designed for 10x–100x traffic growth
• Implement load balancing, autoscaling, and distributed processing
• Optimize API response times and database performance
• Implement global CDN delivery for heavy 3D assets
• Build rate limiting, throttling, and backpressure mechanisms
• Optimize storage and retrieval of large 3D files
• Profile and improve CPU, memory, and network performance

5. Infrastructure & DevOps

• Architect AWS infrastructure (EC2, S3, Lambda, RDS, ElastiCache)
• Build CI/CD pipelines for automated deployments and rollbacks
• Use Infrastructure-as-Code tools (Terraform, CloudFormation)
• Set up monitoring, logging, and alerting systems
• Use Docker and Kubernetes for container orchestration
• Implement security best practices for data, networks, and secrets
• Define disaster recovery and business continuity plans

6. Integration & APIs

• Build integrations with Shopify, WooCommerce, Magento
• Design webhook systems for real-time events
• Build SDKs, client libraries, and developer tools
• Integrate payment gateways (Stripe, Razorpay)
• Implement SSO and OAuth for enterprise customers
• Define API versioning and lifecycle/deprecation strategies

7. Data Processing & Analytics

• Build analytics pipelines for engagement, conversions, and XR performance
• Process high-volume event streams at scale
• Build data warehouses for BI and reporting
• Develop real-time dashboards and insights systems
• Implement analytics export pipelines and integrations
• Enable A/B testing and experimentation frameworks
• Build personalization and recommendation systems

Technical Stack

Backend Languages & Frameworks

• Primary: Node.js (Express, NestJS), Python (FastAPI, Django)
• Secondary: Go, Java/Kotlin (Spring)
• APIs: REST, GraphQL, gRPC

Databases & Storage

• SQL: PostgreSQL, MySQL
• NoSQL: MongoDB, DynamoDB
• Caching: Redis, Memcached
• Search: Elasticsearch, Algolia
• Storage/CDN: AWS S3, CloudFront
• Queues: Kafka, RabbitMQ, AWS SQS

Cloud & Infrastructure

• Cloud: AWS (primary), GCP/Azure (nice to have)
• Compute: EC2, Lambda, ECS, EKS
• Infrastructure: Terraform, CloudFormation
• CI/CD: GitHub Actions, Jenkins, CircleCI
• Containers: Docker, Kubernetes

Monitoring & Operations

• Monitoring: Datadog, New Relic, CloudWatch
• Logging: ELK Stack, CloudWatch Logs
• Error Tracking: Sentry, Rollbar
• APM tools

Security & Authentication

• Authentication: JWT, OAuth 2.0, SAML
• Secrets Management: AWS Secrets Manager, Vault
• Security: Encryption at rest and in transit, TLS/SSL, IAM

What We’re Looking For

Must-Haves

• 5+ years of backend engineering experience with strong system design expertise
• Experience building scalable systems from scratch
• Expert-level proficiency in at least one backend stack (Node, Python, Go, or Java)
• Deep understanding of distributed systems and microservices
• Strong SQL and NoSQL design skills with performance optimization
• Hands-on AWS cloud experience
• Ability to write high-quality production code daily
• Experience building and scaling RESTful APIs
• Strong understanding of caching, sharding, and horizontal scaling
• Solid security and best-practice implementation experience
• Proven leadership and mentoring capability

Highly Desirable

• Experience with large file processing such as 3D, video, or images
• Background in SaaS, multi-tenancy, or e-commerce
• Experience with real-time systems such as WebSockets or streams
• Knowledge of ML or AI infrastructure
• Experience with high-availability systems and disaster recovery planning
• Familiarity with GraphQL, gRPC, and event-driven architectures
• DevOps or infrastructure engineering background
• Experience with XR, AR, or VR backend systems
• Open-source contributions or technical writing
• Prior senior technical leadership experience

Technical Challenges You’ll Solve

• Designing large-scale 3D asset processing pipelines
• Serving XR content globally with ultra-low latency
• Scaling from thousands to millions of daily requests
• Efficiently handling CPU/GPU-heavy workloads
• Architecting multi-tenancy with complete data isolation
• Managing billions of analytics events at scale
• Building future-proof APIs with backward compatibility

Why Ctruh

• Architectural Ownership: Build foundational systems from scratch
• Deep Technical Work: Solve distributed systems and scaling challenges
• Hands-On Impact: Design and code mission-critical infrastructure
• Diverse Problems: APIs, infrastructure, data, ML, XR, asset processing
• Massive Scale Opportunity: Build systems for exponential growth
• Modern stack and best practices
• Product Impact: Your architecture directly powers millions of users
• Leadership Opportunity: Shape engineering culture and direction
• Learning Environment: Stay at the forefront of backend engineering
• Backed by AWS, Microsoft, and Google

Location & Work Culture

• Location: Bengaluru
• Schedule: 6 days a week (5 days in office, Saturdays WFH)
• Culture: Builder mindset, strong ownership, technical excellence
• Team: Small, highly skilled backend and infrastructure team
• Resources: AWS credits, latest tooling, learning budget

The Ideal Candidate

• You are a backend engineer first and architect second - someone who still enjoys writing code, debugging complex issues, and solving scaling problems hands-on.
• You have built systems from the ground up and experienced the challenges that come with scaling them. You think in systems, evaluate trade-offs clearly, and design architectures that are practical, resilient, and future-proof.
• You are comfortable discussing microservices vs monoliths, choosing the right database for a use case, designing APIs, and introducing caching or queues when appropriate. You have made architectural decisions, optimized them later, and learned from the process.
• You stay close to the code. You pair program, review pull requests, jump into production incidents, and ship features alongside your team. You enjoy designing high-level architecture and then implementing the most critical components yourself.
• You balance ambition with pragmatism. You know when to use managed services, when to build custom solutions, and how to ship iteratively while maintaining system stability.
• Most importantly, you are a builder - someone excited to architect the backend foundations of a fast-growing XR platform, optimize performance for massive 3D workloads, and design infrastructure that supports global, real-time immersive experiences.

Responsibilities

§Implement assigned user stories within project schedule.

§Execute unit testing using automated unit test frameworks.

§Collaborate with team to identify and fix technical issue.

Job Description

§Experience in Java/J2EE, web framework (Spring, Hibernate) and web services.

§Hands-on with core Java and Spring MVC.

§Hands-on experience to implement and manage REST and Micro services.

§Familiar with DevOps pipelines.

§Experience in Agile development methodology like Scrum and test-driven Development.

§Good communication skill.

• BackEnd Technologies:

• Technical knowledge:

• It is important to adapt to changing requirements
• Have the ability to integrate external systems

How many hours are they expected to work? 

• - Full time position ( 40+ hours a week) 
•  

What hours should they work?

•  - Prefer 9-5 EST but there is wiggle room
•  

Will there be nights and weekends? 

• - Nights and weekends are not scheduled, however we are looking for someone that takes pride in their work and will lean in to hit a deadline or to fix a bug if it has a significant impact on the platform.
•  

Should they be expected to lead?

• - Yes, you should be expected to lead and to communicate/ cooperate with other devs as a team. Some coding might be alone but the hope of the app is that it all works seamlessly together and to ensure that there needs to be communication among all devs front end and back end. 
•  

Who will they report to?

• - They will report to Product OwnerRob and Product ManagerJulietta daily for standups and well as pushing tasks through the appropriate structure of review, QA, and production. 
• They will also report and check in with Client SuccessCourtney as we look to make the app have a seamless customer experience and customer value. The goal of Attribute should be to try and give as much value as quickly and easily as possible.

Will they work alone or in a team?

• In some spots they might be expected to work alone and on a separate sprint from others, however, everything needs to tie in and work together, because of that the developer must be team oriented in both development and problem solving.
• Additionally, there will be times that they should expect to work with people who are not particularly tech savvy ( ie. sales, marketing, customer success etc.) to collaborate on a specific feature to produce the best thing for the product.

Accountability

• The developer is both accountable for their code and the code of the team. They should take care and responsibility in the work that is done and if there are problems with the code in QA or production work as diligently as possible to fix that problem ( whether it is their code directly or not).
• As part of this all code will be attached from Github to Jira for developers to constantly upload their commits to Jira tasks
• A mistake is completely fine and expected, bugs are to be expected. What is asked is that you report it as soon as possible and are honest about it so that we can move forward in resolving it as soon as possible.

Customer, Usability, and Value Focused

• The end user of our product will be marketing professionals/head of marketing. At all times the developers need to take this into account and spend time thinking of the ease and the use cases that people will utilize their code or features in real life versus what is a way to make something work but in a vacuum. 

Quality focused

• Pushing out code is awesome, but if the code has a ton of bugs and does not do the required action that is practical for the user then it does not matter. We want a developer who is Quality focused and also hold their other developers accountable.

Focused on the whole 

• When producing a feature it is easy to sometime get sucked into how that features works in a vacuum. The developers need to be able to work together and understand the software architecture as a whole in order to make whatever feature they are working on be able to work with the other features that are built within the app ( and will be built or are on the roadmap for the future).

Creativity and Experimentation

• Developers are expected to work within structures, however, they are always encouraged to take time to think of creative solutions and to collaborate on new features or ways of making the product better.

Unfeathered, Honest, Respectful Communication

• Every developer should feel free to speak their mind in a respectful manner to other developers as well as anyone else in the entirety of the company. Any opinion, thought, or perspective will be listened to and valued. 

Next Man or Woman Up Mentality

• Never should anyone on the team defer a problem and say “ thats not my fault or problem”. We are one unit and one company. One problem is everyone's problem and should lean in to the “next man up philosophy” if you have the time and can help to fix the problem and bring it to a solution you should be willing to.

Upward Mobility and Vesting Opportunity

• This position will allow for upward mobility, increased responsibility, and for people who constantly go above and beyond an opportunity to vest into and own equity in the company