2

Mrb Engineer Remote Jobs in New York (NOW HIRING)

Remote Apply Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and ...

Mrb Engineer Remote information

What is an MRB engineer?

An MRB (Material Review Board) Engineer is responsible for evaluating and resolving issues with nonconforming materials or parts in manufacturing processes, ensuring compliance with quality and safety standards. In a remote role, MRB Engineers review documentation, analyze defects, provide technical dispositions, and coordinate with production, quality, and design teams through digital platforms. They play a crucial role in maintaining product integrity and minimizing production delays, even while working offsite.

What are the key skills and qualifications needed to thrive as an MRB engineer in a remote setting?

To thrive as an MRB (Material Review Board) Engineer remotely, a strong background in aerospace engineering, quality control, and problem-solving is required, usually backed by a relevant engineering degree and industry experience. Proficiency with CAD software, PLM systems (like Teamcenter), and familiarity with industry standards and regulatory requirements are essential. Excellent communication, attention to detail, and self-motivation are vital soft skills for effective collaboration and independent work in a remote environment. These skills ensure accurate disposition of non-conforming materials, regulatory compliance, and smooth cross-functional teamwork despite physical distance.

What are some common challenges faced by MRB engineers working remotely, and how can they be effectively managed?

MRB Engineers working remotely often encounter challenges such as coordinating with cross-functional teams across time zones, accessing up-to-date engineering documentation, and ensuring timely resolution of nonconformances. To manage these challenges, it's important to establish clear communication channels—like regular virtual meetings—and use collaborative platforms for document sharing and issue tracking. Being proactive in seeking clarification and maintaining detailed records can also help ensure smooth workflow and compliance with quality standards.

What is the difference between Mrb Engineer Remote vs Mechanical Engineer?

AspectMrb Engineer RemoteMechanical Engineer
Required CredentialsBachelor's in Mechanical, Mechatronics, or related field; certifications varyBachelor's or higher in Mechanical Engineering; PE license optional
Work EnvironmentPrimarily remote, collaborating via online toolsOn-site or hybrid in manufacturing or design facilities
Employer & Industry UsageTech companies, startups, remote engineering firmsManufacturing, automotive, aerospace industries
Common Search & ComparisonYesYes

The Mrb Engineer Remote typically involves designing and testing mechanical systems remotely, often with flexible work locations. In contrast, a Mechanical Engineer usually works on-site in manufacturing or design environments. While both roles require similar educational backgrounds, the Mrb Engineer Remote emphasizes remote collaboration, whereas the Mechanical Engineer often requires physical presence for hands-on tasks.

What cities in New York are hiring for Mrb Engineer Remote jobs?

Cities in New York with the most Mrb Engineer Remote job openings:

Forward Deployed Engineer

Anysphere, Inc

New York, NY • On-site, Remote

Full-time

Re-posted 14 days ago


Job description

Solutions • Full-time • San Francisco; New York; Remote
Apply
Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and engineering. Our organization is very flat, and our team is small and talent dense. We particularly like people who are truth-seeking, passionate, and creative. We enjoy spirited debate, crazy ideas, and shipping code.
About the role
Forward Deployed Engineers embed directly with customer engineering teams to ship production-grade Cursor workflows that measurably improve how they build software.
You'll figure out what's actually slowing a team down, design a practical solution, and own it end-to-end, from first discovery call through launch, iteration, and post-production support. This is not a demo role. You are responsible for systems that work in the real world.
What you'll do
  • Lead discovery with customer engineers to identify the real bottleneck and define clear success metrics
  • Design and build Cursor-powered workflows (e.g., large-scale refactors, migrations, PR review loops, incident → fix pipelines, spec → implementation systems)
  • Ship a fast first version in days, then harden it into something reliable over weeks with proper rollout plans, monitoring, and iteration based on real usage
  • Own production quality: tracing, evals, metrics, debugging model behavior, latency/cost tradeoffs, and failure modes
  • Work directly with Staff+/Platform/Eng leaders - going deep in code while also communicating clearly about tradeoffs and results
  • Turn what you build into reusable patterns and push improvements back into the core Cursor product

You may be a fit if
  • You have 5+ years of experience with software development and coding in Python, Javascript/Typescript
  • Experience includes 2+ years in a customer-facing role, leading discovery conversations and being accountable for customer outcomes
  • You thrive in ambiguity and can turn fuzzy problems into clear scopes and shipped systems
  • You've built and owned AI-native workflows in production, not just prototypes, and have debugged real-world model failures
  • You build end-to-end - if it needs frontend, backend, infra, or prompt iteration, you'll own it
  • You've handled production reliability before (metrics, alerts, safe rollouts, incident response)