Senior Salesforce Developer, Lead to Quote
- H-1B median · Software engineering
- $106k
- Opened · 30d
- +0
- Closed · 30d
- −2
- Opened · 7d
- +5376% of open
- All software engineering
- 75,157open
About Delinea
Delinea is the identity security platform that continuously controls what AI agents, humans and machines can do and for how long. It extends privileged access management from the point of access to the moment of action, using just-in-time authorization to reduce standing privilege across on-premises, multi-cloud and short-lived infrastructure, without adding friction for legitimate users. Delinea provides visibility across every identity type, scores the risk each one carries, and preserves the context behind access decisions, making them auditable and defensible. It supports both static and ephemeral access, letting teams apply Zero Standing Privilege where risk demands it without replacing existing infrastructure.
Summary
Delinea's global go-to-market organization runs on Salesforce, covering the full Lead-to-Quote lifecycle from first touch through territory planning, partner selling and quoting. Salesforce sits at the center of a broader GTM ecosystem of partner, forecasting, sales engagement and data tools.
You will be the senior technical owner on the Lead-to-Quote Business Systems team. Requests from Global Go-to-Market Operations, Marketing and Channel teams often arrive as a loose set of requirements. You will work with stakeholders and the Business Systems team to refine them, decide whether the answer is configuration, Flow, Apex, Lightning Web Components, an integration, or something outside Salesforce, and then get it built. Often that means writing it yourself; sometimes it means pairing with or guiding an Admin or Developer through it.
This is a hands-on role. You will also review code and designs, set patterns others build on, and make the Admins and Developers around you stronger.
Two halves of one job
We are explicit by design. Roughly 70% of your time is hands-on design, build, test and support. Roughly 30% is technical leadership: refining requirements with the Business Systems team, design and code review, and mentoring. The split shifts with the quarter.
This is not an architecture-only role, and it is not a people-management role. You will not supervise a team or assign its work. You will own hard problems and raise the bar for the people solving them with you.
The problems you'll solve
• Turn loose requirements into sound designs. Working with stakeholders, subject matter experts and our Business Systems Analysts, you get to the real problem, bring two or three options with the tradeoffs named, recommend one, and land on a design the business agrees with and the team can build.
• Decide configure, automate, code or integrate. Some problems belong in Flow. Others need Apex, LWC, an integration, or another system. You make the call, write down why, and see it through, whether you build it or guide someone else who does.
• Make integrations fail loudly and recover. Authentication, async processing, retries, error handling and monitoring, so a failure shows up as an alert and not as bad data three weeks later.
• Untangle what has grown too complicated. Overlapping automation, duplicated logic and brittle customizations, replaced with patterns the team can read and support.
• Raise the security bar on Salesforce and its integrations. We are an identity security company, and our own systems should show it. You will tighten access to least privilege, move integrations to secure authentication with scoped integration users, and make sure every external connection has an owner and a reason to exist.
• Ship changes people trust. Flow, Apex, LWC or configuration, every change moves through source control, review and testing with evidence attached.
What success looks like at 12 months
• At least one multi-part Lead-to-Quote initiative taken from a loose set of requirements through refinement, design and production, with the design note others built from.
• Every Salesforce integration in your domain has a named owner, documented failure handling, and monitoring that alerts before the business notices.
• A measurable reduction in overlapping automation on the core GTM objects, with the retired logic and its replacement documented.