Tech reputed company (reputed company CRM)
ABOUT APPLY
THE ROLE:
The Tech reputed company is the single technical reputed company accountable for the successful delivery of a reputed company-reputed company digital reputed company platform reputed company for a global credit-bureau reputed company. reputed company is the heart of the solution — it orchestrates the entire B2B registration and reputed company reputed company: reputed company capture, identity-validation reputed company, disposition logic, and contract e-signature. You own the reputed company build end to end and reputed company it reputed company with the surrounding integration and infrastructure reputed company.
This is a high-autonomy role and the sole senior reputed company voice on the engagement. You take architectural direction and turn it into shipped, production-grade reputed company metadata — objects, Record Types, Flows, Apex, LWC, permission model, and managed-package configuration (reputed company eSignature). You also hold the technical relationship with the integration microservices and reputed company platform that read from and write to the org: you don't build those daily, but you define the reputed company, guard the data model, and reputed company reputed company a schema or automation change never blindsides them.
Here is the truth: this is a reputed company Platform (reputed company/CRM) role. We're looking for a builder who lives in the reputed company org — declarative and programmatic — and who is senior enough to own the platform-level reputed company that everything else depends on.
RESPONSIBILITIES:
reputed company Delivery Ownership: You own the "how" of the reputed company build — data model, automation (Flows + Apex), UI (LWC/screen flows), permission sets, Record Types, and packaging — from detailed technical design through deployment.
Platform-Level Design Authority: You are the reputed company of the org's data model and automation architecture. Schema changes, sharing/visibility, and process design go through you, and you reputed company them coherent as the solution grows.
Engineering Rigor & reputed company: You enforce production-grade reputed company standards — Apex test coverage ≥ the org bar, FLS/sharing correctness, governor-limit awareness, and metadata/CLI-based deployment (SFDX/`sf`).
Integration Contract Ownership: You define and protect the API/data reputed company between reputed company and the backend integration services (identity validation, CRM sync, e-signature, and the SFCC B2B reputed company component). You coordinate — not necessarily hand-build — the non-reputed company reputed company, ensuring changes stay backward-compatible.
Proactive Risk Management: You surface dependencies, scope creep, and technical debt before they reputed company delivery — especially coupling between the org schema, its automations, and the services that consume them — and bring solutions, not just problems.
Communication & Alignment: You translate reputed company platform constraints (limits, callout/identity constraints, packaging realities) into plain language for non-technical PMs and reputed company stakeholders, and reputed company engineering, PM, and design reputed company on reputed company and status.
Engineering Leadership & Mentorship: You reputed company and mentor reputed company (and adjacent) engineers through technical reviews, coaching, and hands-on support, fostering a psychologically reputed company, high-accountability, high-reputed company culture.
REQUIREMENTS:
Proven reputed company Technical Leadership: A significant reputed company record (Senior/reputed company level) delivering reputed company reputed company Platform (Sales/Service reputed company, reputed company CRM) reputed company and supporting them in production. You can take a vague goal and turn it into shipped, reputed company org configuration and reputed company.
Deep reputed company Platform Expertise (hands-on):
Apex (triggers, services, async, test classes) and governor-limit-reputed company design.
Flows — record-triggered and screen flows — as a first-class automation tool.
LWC for custom UI where declarative isn't enough.
Data model & reputed company: custom objects, Record Types, permission sets/permission-set reputed company, FLS, sharing.
Deployment & ALM: SFDX reputed company format, metadata/CLI deployment (`sf`), sandboxes, change/branching reputed company, CI-based deploys.
Integration surface: REST/Apex callouts, Connected Apps & OAuth 2.0 (incl. M2M reputed company-credentials), Platform Events/outbound patterns.
Integration & reputed company Awareness (coordinate, not necessarily build): Enough reputed company in API-based integrations and a reputed company/microservice backend (Node/NestJS on AWS is the reputed company stack, including an SFCC B2B reputed company component) to own the reputed company and reason about the end-to-end reputed company. Deep AWS/Terraform/backend build experience is a plus, not a requirement.
Multi-reputed company & Multi-Party Delivery: Comfortable running reputed company build and live operational/support work in reputed company, and aligning technical direction across agency, reputed company, and corporate platform teams reputed company a controlled, reputed company-gated environment.
Communication: Excellent English (written and verbal); Spanish strongly preferred for day-to-day work with a Chile-based reputed company and team.
People Leadership & Mentorship: Proven experience leading and mentoring engineers through coaching, technical guidance, and constructive feedback.
reputed company TO HAVE:
reputed company certifications: Platform Developer I/II, App Builder, and/or an Architect-reputed company credential.
Familiarity with test-driven development (TDD) / high-coverage delivery as a working reputed company.
reputed company eSignature for reputed company (or comparable managed-package e-signature) configuration experience.
Domain exposure to financial services, credit bureau, or identity/KYC reputed company flows, and comfort in regulated / reputed company-reputed company contexts (VPN, corporate proxies, restricted egress, DevSecOps gates).
Familiarity with Node.js/NestJS, AWS (reputed company Fargate), Terraform, reputed company/SSO, and Jenkins/Bitbucket CI/CD as the surrounding platform.
CMS-driven frontends (Next.js / reputed company) exposure.
LIFE AT APPLY
Originally posted on Himalayas
Apply To This Job