Skip navigation

Front end Developer

Seattle, WA (Hybrid)


Placement Type:


Salary (USD):


Start Date:



  • HTML
  • CSS, ideally including responsive layouts and Bootstrap 5
  • Javascript
  • Image editing/cropping/optimizing with Adobe Creative Suite
  • UX/UI Familiarity
  • Enterprise experience, preferably in a B2B marketing setting
  • Demonstrated experience working for/with Fortune 500 companies or similar
  • Familiarity with use of branding & style guide standards


  • Knowledge of accessibility and web standards
  • SEO skills
  • Experience with Kentico or other web-based content management systems
  • Effective verbal and written communication
  • Being able to convert a “flat design” (e.g. a PDF or image) to HTML/CSS
  • Demonstrated record of effectively working with cross-functional teams
  • Detail oriented and highly organized, with the ability to set priorities, deadlines and work independently in a fast paced environment

Sample items from project list:

  • Thorough QC of existing site for responsiveness (desktop/mobile/tablet), color consistency, image quality/sizing across device types
  • Convert and/or create existing page layouts to templates, including fields that may require code manipulation for graphic adjustments (like icons in headlines, FAQ pages, etc.)
  • Streamline the back end content management of station hours, locations, search and responsiveness for locations pages, with the ability to add additional facility data points as we grow.
  • Scrub for SEO, alternate text, accessibility requirements – entire site
  • Create landing for blog style/newsletter features, archive, campaigns, industry news and stories where we appear (as Cargo). Develop a plan to sunset content managed in WordPress including updated URLs and searchable Archive.
  • Refine Site Navigation (look and feel + organization)
  • Clean up and organize back end content tree, archive and label old pages, publish templates + a very simple how to guide for site administrators/content managers that is on the back of the QA site as a reference guide. Make sure that the QA Site structure and organization mirrors Prod to prevent issues in publishing/sync