Our main office is in Chattanooga, TN but we are a virtual company so working remotely is standard. Although candidates can be located anywhere within the United States, preference is for candidates to be in the Chattanooga or Atlanta area.

At CodeScience, our Salesforce Engineers are the real deal. We take on some of the most challenging Salesforce application development in the business. We look for masters of the Apex language (you’ve written batch, schedulable, bulk and you like it). Our Engineering team is tasked with creative technical implementation, so you must have the desire to push the platform to its boundaries and think outside the box to deliver solutions. The kicker: you have exceptional communication skills balanced with firecracker technical capabilities. This is a crucial position in our ability to deliver value to our customers.

Success predictors

• You have both compiled and interpreted language experience (and you know that)

• You possess a desire to work with interesting clients and projects that challenge you

• You loathe cubicles and value flexibility and challenging work over the 9-to-5 beige office job

• You have a solid handle on building configurable, high performing and appealing applications on the Salesforce ecosystem.

• You love building things that solve client needs elegantly and balanced with long term maintainability

• You are highly motivated, highly intelligent, highly inquisitive and at least moderately funny.

Duties & Responsibilities

• Work with PMs and Architects across multiple projects.

• Provide solution implementation using a variety of technologies listed in the requirements above. Be inquisitive, but practical.

• Perform code review.

• Record hours worked on a daily basis. We like to get paid too.

• Follow development life cycle processes including, but not limited to:

• Adhere to solid coding patterns and comment your code accordingly. Use best practices in both the coding and maintenance.

• Use of Git on each project and practice of team development using pull requests.

• Write test methods as a feature of your codebase, and not just a deployment requirement.

• Smoke test you work before you forward for testing.