Consigue una respuesta de este empleador
Tu currículum y tu carta de presentación, adaptados exactamente a lo que buscan contratar.
AspenView Technology Partners is seeking a Salesforce Developer to build and extend custom functionality on enterprise Salesforce orgs. You will write Apex and Lightning Web Components, design integrations with surrounding systems, and uphold test coverage and release discipline.
You will work within a delivery squad alongside admins, business analysts, and an architect, advocating configuration over code where appropriate and pushing back on requirements that are better solved with
At AspenView, we are passionate about transforming the way organizations approach technology. We specialize in creating high-performing, nearshore IT teams to help North American clients innovate faster and more efficiently.
As we continue to grow, we're looking for exceptional people to join our team and help drive impactful change across industries.
At AspenView, we're more than a nearshore IT partner-we're a people-first, purpose-driven company that believes great culture drives great outcomes. We're passionate about connecting talent and technology to deliver measurable value for clients-and meaningful career paths for our people.
We are seeking a Salesforce Developer to build and extend custom functionality on enterprise Salesforce orgs where declarative configuration has reached its limit. The role writes Apex and Lightning Web Components, designs integrations to surrounding enterprise systems, and holds the line on test coverage, governor-limit discipline and release hygiene. It sits inside a delivery squad alongside admins, business analysts and an architect, and is expected to push back on requirements that would be better solved with configuration than with code.
This is a contributor role, not a task-execution role. The team already has people who deliver what they are handed. What it needs is people who question whether the right thing is being built, and say so.
Holds a point of view and states it, including to senior stakeholders and including after a decision has been made when new evidence warrants reopening it.
Asks why a process, data model, or delivery standard exists before extending it, rather than replicating an incumbent pattern because it is the incumbent pattern.
Surfaces risk, ambiguity, and weak requirements at the moment they are noticed - not at the sprint review, and not at go-live.
Works past the assigned ticket: proposes better approaches, improves what sits around the work, and leaves the team's practice stronger than it was found.
Argues from evidence and changes position on evidence. Comfortable being wrong in public, uncomfortable staying quiet.
Custom code volume falls or holds flat while delivered functionality grows, because con