BAKER LAW GROUP Salesforce Technical Architect and Consultant Contract · US-Based · Remote · Daytime Hours

ROLE SNAPSHOT

Engagement	Independent contractor (1099 or equivalent). Ongoing, not a full-time employee role — we prefer a contractor relationship over W-2.
Location	United States (remote). Domestic candidates only. Must work US business hours.
Time zone	Daytime / core-hours overlap with a US-based team.
Hours	Approx. 15–20 hours per week (solid part-time), flexing up when priority work demands it.
Positioning	Architect-level and hands-on. Owns the system design and writes the code that implements it. Senior to our current offshore developer, and the senior technical authority on the org.
Compensation	Open based on experience, current range is 125-175$/hour
Reports to	CTO / IT & Operations.
Platform	Salesforce Sales Cloud (Enterprise) with a live integration stack — Clio, CallRail, RingCentral, Google Ads, Zapier.

We are a growing law firm running a real, in-production Salesforce environment that ties directly to how we generate revenue: lead intake, call tracking, marketing attribution, and matter management all flow through it. This is not a greenfield build — it is a working, custom system with real records, real integrations, and real business decisions riding on the data. It is also actively evolving: we build, we see more, we improve. This is iterative custom work, not one-and-done configuration.

We are looking for a hands-on senior contractor who can do all of it — architect the data, build and fix directly in Salesforce, and run the project end to end. Concretely, that means one person who can engineer our data, handle both declarative admin work and programmatic customization (configuration and code), execute feature requests, solve bugs, manage the project, and sit as the chair of the working sessions — setting priorities, driving the meetings, and communicating status to leadership. It is the combination of running a project and doing the work that we are hiring for.

The bar, plainly. Senior to our current offshore developer and able to operate independently — someone well past the point of needing tasks handed to them. This is an architect-level seat. Whoever fills it owns the system design, writes the code that implements it, and sits with leadership to decide what gets built next — three capabilities we are replacing in one person. You should be the person who can take a messy dashboard or a broken sync, quickly understand what is wrong, and drive it to a fix — while keeping leadership informed the whole way.

• Integration architecture. Own the health and design of our Salesforce integration stack — how data moves between Salesforce, Clio, CallRail, RingCentral, Google Ads, and Zapier, and how we keep it accurate.

• Business-intelligence mapping. Identify the fields the business needs for reporting and attribution, map them properly across systems, and make sure the data that lands in Salesforce is trustworthy.

• Automation. Design and build the automations (Flow, Apex, triggers) that keep intake, attribution, and matter data flowing correctly without manual copy-paste work.

• Reporting & dashboards. Partner with leadership, marketing, sales, and intake to build reports and dashboards that people who are not in the data every day can actually read and trust.

• Project ownership. Run the work end to end — scope it, prioritize it, sequence the tickets, and drive it to completion. You own the plan, not just the pieces.

• Stakeholder communication. Chair the working sessions and communicate status clearly to leadership and department stakeholders — translating technical reality into decisions non-technical people can act on.

• Technical leadership. Set standards, review work, guide our other developer, and be the senior escalation point for hard problems. Own UAT and deployment discipline (sandbox → production) that protects live records.

• Documentation. Keep code and documentation together, tied to tickets, so knowledge does not live in one person's head. We already build documentation with the help of AI tooling and GitHub — you will add to that practice, not replace it.

The heart of this job is three capabilities in one person: architecture (you design the system), programmatic development (you build it), and consulting (you work directly with our leadership to decide what gets built). Depth in all three is the bar. Experience wiring up specific third-party products is genuinely a bonus, not the bar — more on that below.

Required

• Solution architecture on Salesforce. You have designed a layered custom system, not just configured one. You can explain why logic belongs in a service class rather than a controller, when to extract a reusable service, and how you keep a growing org from becoming a pile of one-off automations — including a position on Flow versus Apex trigger you can defend on bulk behavior, testability and maintainability. You will inherit an org built this way and you will decide how it evolves.

• Programmatic depth — Apex and LWC. Apex you can read, write, debug and extend in a live org, with test classes that actually assert something. Plus real Lightning Web Component work: a large share of our UI is custom LWC — intake, conflict check, AR and invoice dashboards, time-entry and marketing dashboards. If LWC is something you have only touched, this is not the role.

• Asynchronous Apex at scale. Batch, Queueable and Schedulable, with the governor-limit and bulkification instincts that go with them. Our largest integration runs on scheduled batch and queueable chains. This is where an org this size actually breaks, and it is not a Flow problem.

• Direct API integration experience. You have built and maintained a REST integration yourself — authentication and token refresh, pagination, rate limits, retry and idempotency, and error surfacing so that a sync which stops does not stop silently. Middleware fluency (Zapier or comparable) matters too, but knowing where Zapier stops being the right tool matters more.

• AI-assisted delivery, as a working method. Not familiarity — method. You have an established workflow using AI tooling (we use Claude) and GitHub that makes you materially faster than an unassisted developer, plus the review discipline to catch what it gets wrong: unbulkified loops, missing null handling, tests that pass without asserting anything. The hours in this engagement assume that leverage. Without it, this is a bigger job than the one we have posted.

• Business-data mapping and reporting. The ability to understand our business data once we explain it — to see the fields the business actually needs for reporting and attribution, map them correctly across systems, and automate on them — with the Report Builder and dashboard fluency to make the result legible to people who are not in the data every day.

• Consulting judgment and project ownership. You can sit with a non-technical stakeholder, find the need underneath the request, say so when the ask is wrong, and come back with a design they understand — then scope it, sequence it, chair the working session and keep leadership informed. You will do this directly with our COO, CRO and CEO. Not a ticket-taker.

• Deployment discipline on a live system. Sandbox validation, test classes, second review on high-blast-radius changes, and a healthy respect for production data. Our intake and intake-conversion workflows are production-hardened; changes there are root-caused and approved before they ship.

• US-based and available. US-based (domestic), able to work core US business hours, and available to collaborate live with the team and leadership.

Strongly preferred (bonus, not the bar)

Experience linking specific third-party products to Salesforce is a plus, but it is explicitly not the deciding criterion — the integration judgment above matters far more than whether you have touched any one of these tools. Any of the following is a meaningful bonus:

• RingCentral (telephony / IVR integration).

• Google Ads (campaign attribution, GCLID / offline conversion data into Salesforce).

• CallRail (call tracking and lead-source attribution).

• Clio (legal matter management) or comparable practice-management integrations.

• Marketing attribution and multi-touch revenue reporting in Salesforce.

• Agentforce or Einstein — we run Agentforce-based lead qualification at meaningful weekly volume, and it is part of what this role inherits.

• Logical. You think through positive and negative scenarios and question requirements rather than building blindly.

• Technically sound. You know best practices and can choose the right tool — Flow vs. trigger vs. automation — for the job.

• Priority-minded. You treat urgent work as urgent, regardless of the hour count.

• Accountable and responsible. You deliver on time, with test classes and complete work, and you stand behind it.

Our process is designed to find people who can actually do the work, not just describe it:

1. A rubric-scored technical interview with the CTO and members of our leadership and operations team.

2. A paid working interview: we hand you a real problem from our environment and ask how you would solve it. We care far more about how you think through a live challenge than about a résumé.

3. Final alignment with leadership before an offer.

Please note: all scheduled meetings in our hiring process are recorded.

Baker Law Group is an equal-opportunity employer. All qualified applicants will receive consideration without regard to race, color, religion, sex, national origin, disability, veteran status, or any other protected characteristic.