Opportunity Backend Engineering work from LinkedIn, X, Reddit and Upwork, in one list. Find me work
techroles

SDK Java developer-----------Need GC and USC

USM Open
On-site Seattle Mid-level Backend Engineering

At a glance

Mid-level Backend Engineering role at USM. Seattle · no salary stated · we estimate $180,000–$207,800.

Estimated pay

USM has not published a salary for this role. The figure below is our estimate, not theirs.

$180,000 – $207,800
What the middle half of mid-level backend engineering roles in Seattle paid, among postings that did state a salary.
Worked out from 5 postings that stated pay, median $204,898. Last updated Nov 12, 2026.
RoleBackend Engineering
SeniorityMid-level
LocationSeattle
WorkplaceOn-site
PostedOct 18, 2016
Role brief

techroles summary, based on the employer's posting.

What you'll do

  • Build Java SDK libraries that let developers reuse code across applications and platforms
  • Create sample applications and document how developers should use the libraries and their methods
  • Review existing APIs and bring them into the library, including REST APIs and some SOAP exposure
  • Find duplicated code and shape reusable components across library workstreams
  • Research developer needs and contribute across both established and newly created libraries

What you bring

  • You have experience developing Windows Phone applications
  • You can build SDK libraries in Java
  • You hold U.S. citizenship or permanent resident status

Who this fits

This mid-level role is based on-site in Seattle and runs for two years. You’ll suit work that mixes research with coding, calls for curiosity about abstraction, and involves learning across different technologies. Expect tight timelines, overtime, and coordination across several workstreams.

From the employer

SDK Library Java developer

Duration: 2 years

Seattle, WA

Need GC and USC

TOP 3 Skills

  1. Windows Phone app development
  1. Building out SDK Libraries
  1. Java

Nice to have skills

• Security

• Single Sign On

• CI/CD

Additional Information:

Everyone has different criteria for success: Small, Mid size, Enterprise depending on what they are writing apps for and who. Some API's may be 1000 lines of code some may be 20. Some have high security and network performance some don't.

Features differ from phone to computer to watch, each OS is going to have their own lines of code as well and need to be maintained separately.

Developers are swamped with all of these things. Developers need to write these applications that is where libraries come into play. AT&T, Microsoft, Google all need their own libraries.

We are trying to reduce the lines of code, identify areas where we can leverage duplicate code and reusable components.

We want to get to the point where instead of using 500 devs we will only need 350.

Work Environment:

3rd party, maybe 2nd party development. Our timelines are tight, there is going to be overtime. This project was supposed to be done yesterday. There is a lot of connecting on this project. Several different work streams.

We are not sitting on one vertical of code some of our libraries are brand new some have existed for the past seven years.

There are a lot of handlers in this process. API's area already Most are REST, these people may get some exposure to SOAP but all need to be converted to the library. Some API's are brand new, some have been around for many years.

They'll be building sample applications, there's going to be tons of documentation and they need to understand how to use specific methodologies.

We are not looking for 10-20 years of experience but rather people who can apply business problems to solve for developers.

These people are going to come into a CDIC and devops environment with a lot of different technologies. We aren't looking for a language skill set but rather an attitude towards learning / reading and contributing great things.

You may be doing 80 days of research and 10 days of coding (example). We talk functions and features not languages. We need learner and people who have an open mind to match your code to the public...That is the key. People who are curious interested in abstraction.

If you are interested in the below position please forward your profile to preethib@usmsystems(dot)com or call me on 703 468 0398.

Opportunity

Backend Engineering work from LinkedIn, X, Reddit and Upwork, in one list.

Each morning you get everything that fits, strongest first.

Backend Engineering

Find me work

By the team behind techroles.

Find me work
Opportunity

Backend Engineering work from LinkedIn, X, Reddit and Upwork, in one list.

Each morning you get everything that fits, strongest first.

Find me work

By the team behind techroles.