The Role

At CodeScience, our Salesforce Devs are the real deal. We take on some of the most challenging SalesForce product development in the business. We look for wizards on the front-end (in the webapp/spa sense, not like Gandalf) and masters of the Apex language (you’ve written batch, schedulable, bulk and you like it). Our dev team is tasked with creative technical implementations based upon requirements and design and in coordination with other project team members. You have a high chance of succeeding at CodeScience if you are a little overzealous regarding technologies and you have the ability to think outside the box to push the envelope of SFDC . 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 for this role at CodeScience:

• 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 high pay over the 9-to-5 beige office job

• You have a solid handle on building flexible, 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.

Your responsibilities, if you choose to accept the mission:

• Work with PMs and Architects across multiple projects.

• Be agile and motivated.

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

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

• Be responsive to requests from project members and management

• Practice good development life cycle 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.

• Self test you work before you forward for approval.

• Expert use of SublimeText/MavensMate, http://Force.com IDE or comparable IDE