MS2

Software Engineer

MS2 is a national leader in transportation data management and analysis and has the largest traffic count database in North America. More than 270 agencies in 31 US States, and 3 Canadian Provinces, including 28 state Departments of Transportation, are using MS2 software to manage their transportation data.

MS2 is located in the beautiful city of Ann Arbor, Michigan, the home of high-tech industries and the University of Michigan. Residents of the city enjoy beautiful parks, mature neighborhoods, amenities of the Huron River and easy access to downtown Detroit or to colorful "Pure Michigan" woods and waterways.

MS2 is a friendly, open team working to support our clients' software needs. Staff members work on a variety of tasks and are given a high degree of responsibility. We offer an excellent environment for transportation professionals and Software Engineers with competitive compensation and benefit packages. We're a small team and you'll have an opportunity to make a big impact!

We are seeking a Software Engineer who can reliably deliver features end-to-end with occasional direction, while growing toward the independence and ownership expected of a Senior Engineer. You will contribute across the SDLC, collaborate closely with product, QA, and other engineers, and steadily take on more complex work over time.

Responsibilities:

• Deliver small to moderately complex features across the SDLC, from understanding requirements through implementation, testing, and release.
• Write clean, maintainable, and testable code, following team standards and established patterns.
• Collaborate with stakeholders and other engineers to clarify requirements and translate them into workable technical tasks (including constraints, risks, and tradeoffs).
• Contribute to system reliability and supportability through automated tests, debugging, and incremental improvements.
• Triage and resolve defects in production and non-production environments, escalating and pairing as needed.
• Participate in code reviews as both author and reviewer, and incorporate feedback to improve engineering quality.
• Create and maintain lightweight technical documentation (implementation notes, runbooks, and operational considerations).
• Grow ownership over one or more modules, workflows, or services over time, including knowledge sharing with the team.