Senior Individual Node.js Backend Developer (NO AGENCIES) — Convert Existing Tampermonkey Logic to Node.js Backend + Admin Panel Integration

Project Description

IMPORTANT - READ CAREFULLY BEFORE APPLYING

This is a serious technical project.

We are hiring ONE INDIVIDUAL developer only.

NO agencies, software companies, outsourcing teams, middlemen, project managers, or resellers

You must personally do the work yourself.

If you outsource work, hide behind a team, assign the work to someone else, or act as an intermediary -DO NOT APPLY

This project requires strong technical understanding, debugging ability, backend architecture skills, reliability engineering, and production-quality coding practices.

After successful completion, there is strong potential for long-term/full-time work

---

## PROJECT OVERVIEW

We already have:

* Existing Tampermonkey automation logic/script
* Existing Admin Panel (READY)
* Existing Operator Panel (READY)
* Existing Agent Panel (READY)

**Frontend is already completed.**

### IMPORTANT:

**NO frontend development is required.**

Your job is:

**Convert the existing Tampermonkey automation backend logic into a clean, modular, maintainable Node.js backend and integrate it with the already completed frontend panel.**

This is NOT a greenfield project.

This is NOT “build everything from scratch.”

This is a **logic conversion + backend reconstruction task**.

The goal is to:

> faithfully preserve the existing automation workflow behavior while rebuilding it into a clean, maintainable, scalable Node.js backend architecture.

You must understand how to convert working automation logic into production-quality backend systems **without breaking behavior**.

---

## CORE REQUIREMENT — LOGIC CONVERSION FIDELITY

You will receive an existing automation script.

Your responsibility is to:

### Preserve Existing Workflow Behavior

The converted Node.js backend must preserve:

* Existing flow behavior
* Workflow sequence
* Timing-sensitive execution
* Retry behavior
* Request order
* Logic dependencies
* Stability expectations

This project is NOT about redesigning the logic.

The objective is:

> Convert the existing workflow into maintainable Node.js backend architecture while preserving behavior and improving reliability.

Messy copy-paste code or browser-only hacks are not acceptable.

---

## EXPECTED WORKFLOW LOGIC (MUST UNDERSTAND BEFORE APPLYING)

The current workflow follows a multi-step execution system.

Expected workflow:

1. Login / authentication
2. OTP handling and verification
3. Availability checking
4. Slot reserve/initiate process
5. Booking confirmation flow
6. Payment handoff + verification handling (if applicable)
7. One successful end-to-end test execution using provided credentials

You must understand:

* Multi-step workflow orchestration
* Async execution
* Session management
* State handling
* Reliability under timing-sensitive operations
* Retry handling
* Failure recovery

If you do not understand timing-sensitive multi-step systems, **do not apply**.

---

## EXISTING PANEL INTEGRATION (MANDATORY)

The frontend already exists.

Admin / Operator / Agent panels are completed.

Your responsibility:

* Build backend APIs
* Connect Node.js backend to existing frontend
* Integrate workflow execution
* Support existing frontend functionality
* Ensure backend stability and maintainability

Again:

**No frontend redesign or frontend development is required.**

Backend integration only.

---

## TIMING, RELIABILITY & STABILITY REQUIREMENTS

Special attention must be given to:

* Timing-sensitive workflow execution
* Stable multi-step execution
* Retry mechanisms
* Queue/task execution
* Failure recovery
* Logging and debugging
* Reliability under repeated execution
* State/session consistency

We care about **stability and maintainability**, not fragile scripts.

If your code breaks under repeated execution, the project will not be accepted.

---

## NODE.JS BACKEND REQUIREMENTS

The implementation must include:

* Clean Node.js architecture
* Modular folder structure
* Maintainable code
* Logging system
* Retry logic
* Error handling
* Queue/task execution system
* Session management
* Config-based setup
* Async execution handling
* Debuggable architecture
* API integration for existing frontend

Messy single-file implementations will be rejected.

Low-quality copy-paste backend code will be rejected.

---

## LOCAL EXECUTION & VERIFICATION REQUIREMENT

After successful conversion:

You must:

* Run the Node.js system locally
* Integrate it with the provided frontend
* Verify end-to-end workflow execution
* Debug failures until stable

Final milestone requires:

> successful supervised end-to-end validation using provided verification credentials after local integration/testing.

You must be comfortable debugging and fixing issues until the workflow becomes stable.

---

## REQUIRED TECHNICAL SKILLS

You MUST have strong experience with:

* Node.js backend development
* Complex workflow systems
* Async programming
* Multi-step execution systems
* Session handling
* Logging/debugging
* Retry/failure recovery
* Queue/task systems
* API integration
* Production backend architecture

Bonus:

* React / Next.js integration
* PostgreSQL / MySQL
* Monitoring systems

---

## STRICT RULES — DO NOT APPLY IF

* You are an agency/company
* You outsource work
* You only know Selenium/browser automation
* You only know beginner scraping
* You cannot explain debugging technically
* You cannot explain retries/failure recovery
* You cannot structure maintainable Node.js systems
* You cannot work milestone-based
* You cannot produce clean production-quality code

Generic proposals will be rejected instantly.

Low-effort bidders will be ignored.

---

## REQUIRED QUESTIONS (MUST ANSWER ALL)

1. Confirm you are an **individual developer** and NOT an agency/company.

2. Describe a similar workflow/backend system you personally converted or built.

3. Explain how you would convert an existing automation workflow into a maintainable Node.js backend while preserving behavior.

4. How would you structure the backend architecture?

5. How do you preserve workflow behavior during logic migration?

6. How do you handle retries, failures, logging, debugging, and recovery in timing-sensitive systems?

7. How do you validate that a multi-step workflow is stable instead of fragile?

8. What Node.js architecture would you recommend and why?

9. Provide proof of previous technical work (GitHub, portfolio, code sample, technical writeup, demo, etc.).

10. Explain one difficult technical bug you personally solved.

11. Are you comfortable with milestone-based delivery and technical verification?

---

## MANDATORY SCREENING

To be considered:

You must explain:

* How you would analyze existing automation logic
* How you would rebuild logic into Node.js while preserving behavior
* How you debug timing-sensitive workflow failures
* How you structure maintainable backend systems
* How you ensure reliability and stability

Copy-paste proposals will be rejected.

We are hiring based on technical skill, reliability, communication, debugging ability, maintainability, and ability to deliver clean backend systems.

Strong performance on this project may lead to full-time work. Show More

Attachments

Freelancers Bidding (0)

  • This project has no proposals yet.
    Be the first to place a bid on this project!