About the Team & Role

Team builds the infrastructure that keeps commercial drivers and fleets moving from fuel payments

at the pump to the apps and backend services that power authorizations, loyalty, and real-time

transaction data. As an SDE I, you'll join one of two full-stack engineering teams within WEX's

Mobility organization.

Both teams own their systems end to end. The 10-4 (OTR) team builds the over-the-road platform

customer-facing APIs, event-driven microservices (Java/Spring Boot, Python), Kafka-based async

processing, payment and identity integrations (Fiserv, Okta), and the Android and iOS apps that

drivers use in the field. The NA Mobility Platform team builds and owns the shared frontend

infrastructure that product teams across the organization depend on Angular micro-frontends with

NestJS BFFs, Module Federation, a shared component library (Theseus UI), brand theming, and app

scaffolding via Theseus Builder.

In both cases, you'll work across layers of a real production stack, ship to real users, and be

supported by engineers who care about doing the work well. We value clean APIs, strong testing

habits, and engineers who improve the systems they touch. You'll work closely with the product,

other OTR teams, and your peers on features from design through implementation, testing,

deployment, and production support.

How You'll Make an Impact

• Build specific components within an established architecture. You'll follow the patterns your team
• has set, whether that's microservices, event-driven design, or component-based frontend, and
• implement features correctly within those structures rather than redefining them.
• Write clean, compilable code with unit tests that meet the team's quality standards. Before you
• start building, you'll ask the right questions about acceptance criteria and error states so you're
• solving the right problem, not just writing code.
• Identify and fix bugs in well-defined tasks. You'll reproduce issues, pinpoint where in the code
• they're happening, and work with senior engineers to land the right fix rather than just patching
• the symptom.
• Handle low-priority support tickets as a first responder and participate in on-call rotations under
• supervision. During incidents, you'll run specific checks and scripts as directed, building your
• confidence with live systems gradually and safely.
• Contribute to basic observability by adding error and info logging that helps the team debug
• issues. You won't be expected to triage complex production problems alone, but your logs should
• make it easier for others to do so.
• Keep the team's process running smoothly. That means updating Jira daily, following the
• Definition of Done, moving tickets through the right stages, and raising a flag immediately if
• something is at risk. You don't deviate from the team's agreed process without checking first.
• Show up fully in team rituals like standups, backlog grooming, and demos. You'll listen to
• stakeholder feedback during demos to understand how your work actually lands with users, not
• just whether it passed the acceptance criteria.
• Use AI tools like Cursor or similar to reduce boilerplate, get unstuck faster, and understand error
• messages more quickly. You own the quality of everything you ship though, which means
• validating AI-generated output rather than passing it through unchecked.
• Update documentation when you find something inaccurate or missing. Good documentation is
• part of the job, and you'll be expected to keep it honest as you learn the system.

Experience You'll Bring

• You have a solid grounding in data structures, algorithms, and software design from a B.S. or M.S. in Computer Science from a reputed institution, with 0 to 1 year of professional experience.
• You're comfortable writing clean, compilable, tested code in at least one of Java, Python, or TypeScript/JavaScript, and you understand what makes code maintainable, not just functional.
• You understand the testing pyramid and have written unit tests as part of coursework, an internship, or a personal project. You see tests as part of the feature, not an afterthought.
• You know never to hardcode secrets, you have a basic understanding of IAM and role-based access control, and you're willing to learn which compliance requirements like PCI or SOC apply to the systems you work on.
• You know your way around Git and pull requests, can deploy to an existing CI/CD pipeline, and can tell when your specific commit caused a build failure.
• When you're blocked, you ask focused questions and explain what you've already tried. You flag a deadline risk the moment you see it, not the day before it's due.
• You receive code review feedback without getting defensive, you actively learn your team's standards and tools, and you're comfortable switching between tasks within a project when priorities shift.

Preferred Qualifications

• A degree in computer science software engineering from a reputed institution.
• Internship or co-op experience where you shipped real code to a production or staging
• environment as part of a team.
• Strong problem-solving and analytical skills.
• Excellent communication and collaboration skills.
• Ability to work independently and as part of a cross-functional team.
• Familiarity with cloud basics even through coursework or personal projects.
• Exposure to containerization through Docker. Reading and running existing Dockerfiles counts,
• you don't need to have written them from scratch.
• Some experience working in an existing codebase, contributing improvements, and navigating
• code you didn't write yourself.
• Awareness of AI tools beyond code completion, such as experimenting with prompt design or
• modifying a simple AI-powered script or agent.
• A genuine interest in the domain. Payments, fleet operations, or developer platform work are
• exciting problem spaces and it helps to be curious about the industry, not just the technology.