Description

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.

Responsibilities

Build specific components within an established architecture following team patterns.
Write clean, compilable code with unit tests that meet quality standards.
Ask the right questions about acceptance criteria and error states before building.
Identify and fix bugs in well-defined tasks, working with senior engineers.
Handle low-priority support tickets as a first responder and participate in on-call rotations under supervision.
Contribute to basic observability by adding error and info logging to help debug issues.
Keep the team's process running smoothly by updating Jira daily and following the Definition of Done.
Show up fully in team rituals like standups, backlog grooming, and demos.
Use AI tools like Cursor to reduce boilerplate and understand error messages while owning final code quality.
Update documentation when finding inaccurate or missing information.

Requirements

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.
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, contributin 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.

Job Details	Information
Job Title	Software Development Engineer 1
Role	Software Development Engineer 1
Company	WEX

Software Development Engineer 1

Description

About the Team & Role

Responsibilities

Requirements

Required Skills

WEX

Recent Jobs