Open role · Engineering

Software Engineer, Fullstack (Early Career)

Work mode: Remote (EST preferred) Engagement type: Full-time Contract Req ID: GDBI-3M5O7J1L

Role summary

Build real product and platform features across frontend, backend and data layers while growing alongside experienced engineers, designers and data teams.

What you’ll do

  • Plan, build and ship product features across frontend, backend and database layers.
  • Develop interfaces for data visualization, analytics and business applications.
  • Build APIs, integrations and backend services supporting product and platform workflows.
  • Work with SQL and NoSQL databases and learn sound data-modeling practices.
  • Improve performance, testing, accessibility and reliability of production experiences.
  • Contribute to internal tools and reusable engineering components that enable the team to move faster.

What you should bring

  • Strong software-engineering fundamentals demonstrated through work, internships, projects or open-source contributions.
  • Working knowledge of JavaScript/TypeScript and at least one backend language such as Python or Node.js.
  • Understanding of APIs, databases, version control and web application architecture.
  • Ability to learn quickly, ask precise questions and take ownership of defined problems.
  • Good written and verbal communication in a distributed team.
  • Interest in enterprise data, analytics, AI and operational software.

Useful additional experience

  • React or similar frontend framework
  • Cloud-development exposure
  • Data visualization projects
  • GitHub or portfolio demonstrating shipped work

How we work

NoèmeX teams stay close to the business problem and the production system. You may work across client delivery, platform development or internal capabilities depending on the role. We value clear specifications, maintainable architecture, disciplined execution and direct communication.

Hiring process

The exact assessment varies by role. Shortlisted candidates should expect an initial conversation followed by a role-relevant technical, practical or structured panel assessment before a final decision.

Submit your application.

Provide the information required for this role. Applications are reviewed using the recruitment process described in our recruiting privacy policy.

Your home address is required for this application and is handled under our recruiting privacy policy. Do not include passport numbers, SIN/SSN, financial account details or other sensitive government identifiers.

Used to send your verification link and updates for this application.
Used only if we need to clarify availability or interview scheduling.
Helps us understand work authorization constraints for client environments.
Add a second country of citizenship if you hold dual or multiple citizenship. Leave this blank if it does not apply.
Helps align timezone, tax/vendor setup, and client access requirements.
Select your address from the list to fill the fields below automatically, or enter them manually - this box does not need to work for your application to go through.
Please enter your rate in your local currency, based on your country of residence.
Consider Europe broadly here (for example the EU, the UK, or Switzerland). Work authorization is granted by individual countries, not the EU as a whole, so we'll ask which country if that matters for your answer.
An employer-specific (closed) work permit only authorizes you to work for the employer named on it.
Most US work visas are tied to a specific sponsoring employer - let us know which one applies.
Used for fast background context (roles, dates, industries). No automated posting.
Used to review work samples where relevant (code, dashboards, writeups).
This is required so we can score applications consistently. Please paste the text directly rather than emailing your resume separately - do not include passport numbers, SIN/SSN, financial account details or other sensitive government identifiers.
Optional supporting link. If provided, it must be accessible without logging in (e.g., "anyone with the link can view").