Jr. Software Engineer - MX

Neumo; Región Centro; Remoto; MXN 240.000 - 360.000; Tempo pieno

Descrizione del lavoro

Neumo is hiring a junior full stack engineer to contribute to the Platform team. You’ll work across the stack—from React on the front end to Node.js services and PostgreSQL behind them—learning fast with senior engineers as you own well-scoped features.

You’ll join a remote-first team that moves fast, ships reliably, and uses modern tools (including AI) to accelerate development while upholding accessibility and security considerations.

Competenze

• 0-2 years of professional software development.
• Strong knowledge of JavaScript, HTML, CSS.
• Experience with React and Node.js.
• Familiarity with PostgreSQL and RESTful APIs.
• Good Git version control skills.

Mansioni

• Build features across the stack using React components and Node.js endpoints.
• Write clean code and tests following existing patterns.
• Track down defects and collaborate to resolve issues beyond a single change.
• Use AI coding tools in daily workflow and review outputs critically.
• Ensure accessibility and responsive design to WCAG 2.1 AA.

Conoscenze

JavaScript

HTML/CSS

React

Node.js

PostgreSQL

Git

Communication

Problem solving

Formazione

Bachelor’s in CS/Engineering or related field

Equivalent practical experience

Strumenti

Jest

AWS

CI/CD

Containers

Descrizione del lavoro

Junior Full Stack Engineer (React, Node.js)

Neumo - Remote

About Neumo

Neumo builds the software that runs local government: records, tax and licensing, courts, DMV, and payments. We serve communities across the country, and our platform is the shared foundation every Neumo product is built on. Build something here and it ships to dozens of applications and the governments and citizens who depend on them.

About The Role

We're hiring early-career engineers for our Platform team. Platform builds the shared services every Neumo application consumes: reporting, payments, search, authentication, messaging, file handling, and more. Our guiding principle is build once, use everywhere. When three products need the same capability, Platform owns it.

You’ll work across the stack - React on the front end, Node.js services and PostgreSQL behind them. On any given day you might build a component against our design system, add an endpoint to an existing service, write the tests that cover it, or trace a bug back through the stack to find where it actually started.

This is a first or second engineering job, and we’ve written it that way on purpose. You’ll take on well‑scoped pieces of larger features, with a senior engineer close at hand and review on everything you ship. We don’t expect you to arrive knowing our stack or how county government works. We expect you to learn both fast, ask questions early, and own what you’re given.

We move fast, we own what we ship, and we use modern tools (including AI) aggressively to do it.

What You’ll Do

• Build features across the stack: React components on the front end, Node.js endpoints and the PostgreSQL queries behind them.
• Write clean code that follows the patterns already in the codebase, and the tests that go with it. Untested code isn’t finished code.
• Track down and fix defects in the code you’ve written, and pull in help when a problem turns out to run deeper than your change.
• Use AI coding tools (Claude Code, Cursor) as part of your daily workflow, and learn to review what they produce as critically as you’d review your own work.
• Build to our accessibility and responsive standards, including WCAG 2.1 AA, using the shared design system rather than rebuilding components from scratch.
• Take part in design reviews and code reviews. Listen first, then start contributing. Sprint estimates and blockers are yours to raise, early and honestly.
• Treat security as part of the definition of done, and build an understanding of how SOC 2, PCI, and GDPR shape what we do on sensitive paths.
• Learn the domain. Our users are clerks, courts, and citizens, and knowing what they’re actually trying to do will make you a better engineer here than any framework will.

What We’re Looking For

• 0-2 years of professional software development experience. Internships, apprenticeships, boot-camp work, open-source contributions, and a portfolio you can walk us through all count.
• Working knowledge of JavaScript, plus HTML and CSS fundamentals.
• Exposure to a modern front-end framework. React preferred; Angular or Vue.js also fine.
• Exposure to Node.js or another back-end language, and a grasp of what a RESTful API is and how it gets consumed.
• Foundational SQL and an understanding of relational data — how tables relate, how a query returns what it returns. We use PostgreSQL.
• Comfort with Git: branching, pull requests, and resolving the occasional merge conflict.
• A methodical approach to problems you haven’t seen before, and the judgment to ask for help before a day disappears.
• Clear written and verbal communication. Much of our team is distributed, so clear async communication matters.
• Bachelor’s degree in Computer Science, Engineering, or a related field, or equivalent practical experience.

Bonus points for

• Experience with automated testing tools such as Jest.
• Any exposure to AWS, or to CI/CD pipelines and containers.
• Experience working with AI-assisted development tools on something real.
• Anything you’ve built and shipped that people other than you have used.
• An interest in civic technology, or any experience with how local government actually works.

How We Work

We build reliable, fast, shared software that the whole company depends on. We bias toward action, we own our work end to end, and we hold ourselves to being a model for the rest of the engineering org. We’re remote-first and we work in two-week sprints.

We hire early-career engineers because we intend to grow them. This role sits at Software Engineer 1 in Neumo’s engineering career framework, and what it takes to reach Software Engineer 2 is written down rather than left to guesswork: delivering your work predictably, debugging on your own, giving your peers code review feedback worth having, and understanding how a request travels through our stack from end to end. Your manager will use that framework in your growth conversations from your first month, not your first review.