1

Nodejs Intern Jobs in New York (NOW HIRING)

Showing results 21-23

Nodejs Intern information

What does a Nodejs intern do?

A Node.js intern assists in developing and maintaining server-side applications using Node.js, a popular JavaScript runtime. Their responsibilities typically include writing backend code, debugging existing applications, integrating APIs, and collaborating with other team members to deliver scalable solutions. Interns often work under the guidance of senior developers, gaining hands-on experience in modern web development practices and tools. This role helps interns build a strong foundation in backend development and prepares them for more advanced software engineering positions.

What kinds of projects and tasks can a Nodejs intern expect to work on during their internship?

As a Node.js Intern, you will typically assist in developing and maintaining server-side applications using Node.js. Your daily tasks may include writing and testing code, fixing bugs, collaborating with senior developers on larger projects, and participating in code reviews. You might also work with databases, RESTful APIs, and integrate third-party services. This role offers a great opportunity to learn best practices in backend development and gain exposure to agile workflows within a supportive team environment.

What are the key skills and qualifications needed to thrive as a Nodejs intern, and why are they important?

To thrive as a Nodejs Intern, you need a solid understanding of JavaScript, basic knowledge of server-side development, and familiarity with Node.js frameworks, typically demonstrated through coursework or personal projects. Experience using version control systems like Git and exposure to databases such as MongoDB or MySQL are common technical requirements. Strong problem-solving abilities, willingness to learn, and effective teamwork set standout candidates apart. These skills are crucial for building reliable backend applications, adapting to evolving project needs, and collaborating with development teams.

What is the difference between Nodejs Intern vs Nodejs Developer?

AspectNodejs InternNodejs Developer
Required CredentialsTypically pursuing or recently completed relevant coursework or degreeProfessional experience, certifications, or proven skills in Node.js
Work EnvironmentEntry-level, supervised, learning-focusedFull-time, independent, project-driven
Employer & Industry UsageInternships in tech companies, startups, or IT departmentsFull-time roles in software development companies, tech firms
Search & Comparison IntentUnderstanding entry-level opportunities, learning pathsCareer progression, skill requirements

In summary, a Nodejs Intern is an entry-level position focused on learning and gaining experience, often requiring minimal prior experience. A Nodejs Developer is a more advanced role that involves actively building and maintaining applications, requiring relevant skills and experience.

What are the most commonly searched types of Nodejs jobs in New York?

The most popular types of Nodejs jobs in New York are:

What cities in New York are hiring for Nodejs Intern jobs?

Cities in New York with the most Nodejs Intern job openings:

Software Engineering Evaluation Specialist

Mindrift

Queens, NY • On-site

$35/hr

Part-time

Posted 3 days ago

New


Job description

Please submit your CV in English and indicate your level of English proficiency.

Mindrift connects specialists with project-based AI opportunities for leading tech companies, focused on testing, evaluating, and improving AI systems. Participation is project-based, not permanent employment.

About the Role

You'll design coding tasks that challenge frontier AI coding agents. Each task is a self-contained Docker environment with a broken piece of software; an AI agent attempts the fix; automated tests verify the outcome. Your deliverable is the full task package: broken code, tests, instructions, and a reference solution proving the task is solvable.

Responsibilities:

  • Invent a realistic developer scenario - a real bug, a broken ETL, a missing feature - not a toy problem.
  • Build a reproducible Docker environment with pinned dependencies.
  • Write a pytest that verifies outcomes, not specific commands - deterministic, non-flaky, and does not leak the fix.
  • Write an instruction.md that reads like a Jira ticket a developer would receive.
  • Write a reference solve.sh proving the task is solvable.
  • Calibrate difficulty so current state-of-the-art agents solve the task 20-60% of the time.
  • Iterate based on feedback from expert QA reviewers.
  • Later: review other authors' tasks as a QA reviewer.

Not in scope

  • Data labeling, prompt engineering.
  • Production code to ship - you design problems and verification for AI agents.
  • Leetcode puzzles - scenarios must look like real developer work.
  • Not every candidate task ships - quality over quantity.

Requirements

  • 3+ years of production software development in one backend stack - Python, Go, Node.js, Java, or Rust. Depth in one stack beats breadth.
  • Python + pytest fluency - required regardless of primary stack. The task harness is pytest-based even when the broken app is in another language. Fixtures, parametrize, monkeypatch, timeouts, conftest.py.
  • Docker authoring - reproducible Dockerfiles, pinned dependencies, multi-stage builds when needed, non-root user.
  • Linux & Bash - comfort debugging inside containers (strace, lsof, journalctl); shell beyond set -euo pipefail.
  • AI coding agent experience - Claude Code, Cursor, Roo Code, or similar, on non-trivial work. You can cite a specific time the AI was confidently wrong and how you caught it.
  • English - B2+ written.

Not a fit

  • Data Science, ML, or Computer Vision engineers without backend-engineering output.
  • Manual QA testers without automation or test authoring.
  • Frontend-only, low-code / no-code, IT Support, or Business Analysts.
  • Engineers who have never written pytest from scratch.
  • Junior, intern, or assistant as the most recent role.

Preferred qualifications

  • Domain depth in Security, System Administration (nginx / systemd / cron), Scientific Computing (NumPy / PyTorch / SciPy), DevOps, or Git internals.
  • Modern Python tooling (uv, poetry, pyproject.toml).
  • Coverage tooling (pytest-cov, coverage.py, gcov, llvm-cov, kcov).
  • Fuzzing or property-based testing (Hypothesis).
  • Prior contribution to agent-evaluation benchmarks or related frameworks.

Process

Apply Pass qualification (90-minute sample-task screen + short behavioral interview) Join a project Complete tasks Get paid.

Time commitment

  • Onboarding: ~10 hours per first task.
  • Steady state: ~5 hours per task, 2-4 parallel tasks per author.
  • Realistic weekly load: 8-20 hours. Higher volume available for top performers.
  • You choose when and how to contribute; tasks must be submitted by the deadline and meet acceptance criteria.

Compensation:

  • Paid contributions, rates up to $35/hour*.
  • Task-based compensation equivalent to hourly rate, depending on performance and volume.
  • Some projects include incentive payments.

*Rates vary based on expertise, skills assessment, location, project needs, and other factors. Higher rates may be provided to highly specialized experts. Lower rates may apply during onboarding or non-core project phases. Payment details are shared per project.

Apply

Submit your CV via the Mindrift platform. Indicate your English level, note this role (Software Engineering Evaluation Specialist - Terminal Bench), and include a GitHub profile link if available.