Careers

Establish or continue your
IT career with Sparta Services

Dynamics Solutions Analyst (Finance and Operations)

Role Overview

 

You build and extend the finance, supply chain, and operations systems our clients run their businesses on.

 

Sparta Services LLC is a Microsoft Solutions Partner based in Kirkland, Washington. We work as a Managed Intelligence Provider across four verticals: Community Association Management, Manufacturing, Field Services, and CPA and Accounting. Power Studio is our build team, covering Power Platform, Dynamics 365, application development, data engineering, and AI.

 

As a Dynamics 365 Finance and Operations Developer you own how things get built. The work is code first: X++ extensions in Visual Studio, data entities and integrations, reporting and document output, and the pipelines that move all of it safely between environments. You sit in the Dynamics 365 group inside Power Studio alongside functional consultants who own process design, while you own the technical design and the build.

Analyst is our delivery level. You take a defined requirement or design and build it end to end with light supervision. You are expected to surface trade-offs and blockers early rather than quietly working around them, and to leave behind work the next person can pick up.

 

Business Impact

What changes for Sparta and for our clients because this role exists.

  • Client finance and supply chain processes run on changes that survive Microsoft’s service updates, because every customization is built as an extension rather than an overlay.

  • Integrations between Finance and Operations and the rest of the client estate move data reliably, and are observable when they do not.

  • Deployments are repeatable. Packages are built, tested, and promoted through a pipeline rather than applied by hand under time pressure.

  • Reporting and document output arrive in the format the client’s finance team actually needs, without manual rework at every period close.

  • Power Studio can take Finance and Operations work on directly instead of subcontracting it, which widens what we can sell into our Manufacturing and Accounting verticals.

 

Key Responsibilities

Grouped by where the week actually goes.

 

Build and Extend

(The core of the role)

  • Build X++ extensions using the Finance and Operations developer tools in Visual Studio: table, form, and extended data type extensions, Chain of Command, and event handlers. Overlayering is not an option on the current product.

  • Create and extend data entities for import, export, and integration, including Data Management Framework projects and recurring integration endpoints.

  • Build SSRS reports and Electronic Reporting configurations to the output specification the client has signed off.

  • Extend security with duties, privileges, and roles that match the client’s segregation of duties requirements.

  • Build and maintain number sequences, workflows, and batch jobs where the requirement calls for them.

 

Integration and Data

(Where most production incidents are won or lost)

  • Expose and consume OData endpoints, custom services, and business events, handling paging, batching, throttling, and retry behavior rather than assuming the happy path.

  • Build dual write and virtual table integration between Finance and Operations and Dataverse where a shared data story is required.

  • Use Power Automate, Logic Apps, and Azure Functions for orchestration that does not belong inside X++.

  • Write integrations that fail loudly and recover cleanly, with logging a support engineer can actually read.

 

Application Lifecycle and Release

(Nothing ships outside this)

  • Work in source control, Azure DevOps or GitHub, with branch and merge discipline. No development happens outside source control.

  • Build deployable packages through automated pipelines and promote them through sandbox tiers into production.

  • Keep environment, package, and asset records current in whichever platform governs the client’s environments, Lifecycle Services or the Power Platform admin center.

  • Write and run unit and regression tests before user acceptance testing, and triage defects raised during testing with a documented root cause.

 

Delivery and Collaboration

(The part that makes you re-hireable on the next engagement)

  • Turn functional designs into technical designs, and raise early when a requirement is better served by standard functionality than by code.

  • Document what you build: technical design notes, deployment steps, and handover material for Power Studio Care.

  • Support user acceptance testing and hypercare alongside the functional consultant.

  • Contribute reusable patterns and components back to the team rather than solving the same problem twice.

 

Qualifications

  • Two to four years of hands on Dynamics 365 Finance and Operations development, or equivalent AX 2012 experience plus demonstrable work on the current product.

  • Strong X++ and a working understanding of the Finance and Operations data model and application framework.

  • Practical experience with the extension model: Chain of Command, event handlers, and extension based customization.

  • Experience with data entities, the Data Management Framework, and at least one integration pattern in production.

  • Source control and release pipeline experience, including building and deploying packages.

  • Clear written English. The role touches client facing documentation.

 

Preferred

  • Dual write or virtual table integration between Finance and Operations and Dataverse.

  • Power Platform experience: Power Automate, Power Apps, or Power BI over Finance and Operations data.

  • Azure services used in integration work: Functions, Service Bus, Key Vault, Application Insights.

  • Working knowledge of a finance or supply chain domain: general ledger, accounts payable and receivable, inventory costing, or production.

  • MB-500 certification, or a credible path to it.

 

Competencies

How we expect the work to be done, not just what gets done.

  • Judgment on build versus configure. You can tell when a requirement is better met with standard functionality than with code, and you say so before writing any.

  • Upgrade discipline. You do not take shortcuts that make the next Microsoft release someone else’s problem.

  • Works in the open. Blockers surface in hours, not days. Estimates get revised out loud.

  • Writes it down. Technical design notes, deployment steps, and handover material are part of the work, not an afterthought.

  • Client awareness. You can explain a technical constraint to a finance lead without either talking down to them or hiding behind jargon.

    Please prove you are human by selecting the tree.

    CV* (Max file size 10MB).

    By submitting this form, you consent to Sparta Services contacting you regarding our services by telephone, text message and email. SMS/Test message and data rates may apply. Message frequency varies. You can reply “STOP” to opt-out of future
    messaging or “HELP” for more information.

    Is Your Data Ready for Copilot?​

    Discover hidden Copilot risks with a free AI Readiness Assessment.

    No Commitment Required