Agent
Jobs
Applied
Tracker
Profile
    1. Jobs for you
    2. Job

    Job · 19520043

    JAIPUR · FULLTIME

    Senior Backend Engineer / Technical Lead - Node.js & Rust

    Lucid Growth Media logo

    Lucid Growth Media

    Jaipur · onsite · Posted 23d ago

    Sourced fromNaukri
    ₹7.0L - ₹10.0L PA4–6 yrsfulltimeJaipur

    About a minute. You'll make an account on the way through.

    agent · working

    • Read this posting0.5s
    • Found the form on Naukri · 7 questions to answer1.5s
    • Decided the answers for all of them3.1s
    • Tailor your résumé to this role
    • Waiting for you

    Section · 01

    About this role

    Company: Lucid Growth Media
    Website: https://lucidgrowthmedia.com/
    Department: Engineering
    Employment type: Full-time
    Work mode: On-site
    Job location: Shyamnagar, Jaipur, Rajasthan
    Minimum experience: 4 years of professional experience
    Maximum experience: 6 years of professional experience
    Prior on-site development-team experience: At least 2 years
    Monthly take-home salary: 60,000–80,000 — up to 80,000, based on demonstrated capability and relevant experience. The offer will include a salary breakdown.
    Working schedule: Monday to Saturday; second and fourth Saturdays off. Sundays off.
    Shift timing: 9:00 AM–6:00 PM (9-hour shift)
    Application deadline: 30 September 2026

    Skills: Node.js, TypeScript, Rust, asynchronous processing, REST APIs, database design, performance debugging, Git review and application security.

    Job description

    Join a small engineering team improving existing software and building new capabilities. You will own backend reliability, data correctness and asynchronous processing, and guide technical decisions across application and automation engineers.

    This is a hands-on position involving production debugging, measured performance improvements, safe changes to existing code and release ownership. Company-provided AI coding tools support the work; you remain responsible for understanding and verifying what ships.

    Responsibilities

    - Develop and improve TypeScript/Node.js APIs and Rust services, including concurrency, failure handling and durable processing.
    - Diagnose slow queries and API paths; improve schemas, indexes, caching and background jobs based on evidence.
    - Define reliable service contracts, event identities, retries and reconciliation across connected components.
    - Protect data access, credentials and permissions; plan migrations, staged releases and recovery.
    - Review changes, document decisions and help engineers resolve technical blockers.
    - Break work into tracked tasks with acceptance criteria, obtain the required approval and provide test/release evidence at completion.

    Required skills and experience

    - Substantial production Node.js/TypeScript experience and Rust experience you can explain through systems you personally changed or operated.
    - Practical asynchronous Rust, ownership/error handling, network integration, persistence and debugging skills.
    - Strong database fundamentals, including query analysis, transactions or consistency trade-offs, and safe migration practices.
    - Experience with API authentication, automated tests, Git review, logging and controlled deployment.
    - Clear written English for task plans, technical decisions, incident notes and constructive review discussions.
    - Evidence of taking responsibility for a problem, responding to feedback and verifying the corrected result.

    Experience with MCP/tool integrations, containerised services or performance profiling is useful. Depth in the core responsibilities matters more than a long list of frameworks.

    How we work and hire

    Work follows documented tasks, approval, implementation, review and verification. We value early escalation of blockers and honest reporting of results.

    Selection includes a short AI-assisted initial interview, an approximately 60–90-minute practical using synthetic material, and an on-site technical discussion. Final hiring decisions include human review.

    Screening questions — full wording

    Please answer every part of the corresponding mandatory screening fields. Related questions are grouped into 10 answer fields.

    1. How many years of professional software development or code-based automation experience do you have, excluding training courses?

    2. How many years have you worked as part of an on-site development team?

    3. Can you work full-time on-site in Shyamnagar, Jaipur, Rajasthan, from 9:00 AM to 6:00 PM, Monday to Saturday, with second/fourth Saturdays and Sundays off?

    4. Is the published monthly take-home range of 60,000–80,000, up to 80,000, acceptable to you?

    5. What is your notice period and earliest available joining date?

    6. How many years of hands-on production Node.js/TypeScript development experience do you have?

    7. How many years of hands-on production Rust development experience do you have?

    8. In 80–120 words, describe a production Rust or backend reliability problem you personally diagnosed. What did you change, how did you verify it, and what was your role in the release?

    9. Where are you currently based? enter your current city, state and country.

    10. If selected, can you start full-time on-site within seven calendar days of receiving a written offer, after completing any required release from your current role?

    11. What is your plan for attending the Shyamnagar office daily from your joining date? State whether you will commute from your current location or relocate, and when the arrangement will be ready.

    12. What are your three most important priorities in your next role? Rank three from technical ownership, learning and mentorship, compensation, job stability, predictable working arrangements, and team culture, or name another work-related priority. Briefly explain how this vacancy fits those priorities.

    13. Describe a recent work commitment that was at risk of being missed. When did you flag the risk, what action did you personally take, and what was the final outcome?

    14. Describe a time you received review feedback that you initially disagreed with. How did you evaluate it, what did you change or clarify, and how was the outcome checked?

    15. You are working on an approved task when an urgent verbal request arrives. What would you do before changing the work, and how would you record the priority decision, approval and completion evidence?

    Sourced from naukri

    Section · 02

    Skills

    Git reviewAsynchronous ProcessingRustDatabase DesignPerformance DebuggingNode.JsTypescriptApplication SecurityREST APISystem Design

    Senior Backend Engineer / Technical Lead - Node.js & Rust · waiting for your command