Principal Software Engineer

About the role

We are hiring a Principal Software Engineer to be the technical anchor for our eFlow platform and the eFlow Automator integration and rules engine. You will own architectural direction for how Automator rules, JEXL scripts, and FreeMarker templates power event-driven workflows across the platform including high-volume integrations with NetSuite, internal Workbench data, and external partner APIs over both REST and ActiveMQ-based messaging. This role combines deep hands-on engineering (writing and reviewing scripts, debugging production rule failures, designing new template patterns) with technical leadership (mentoring engineers, setting standards, and partnering with product, support, and implementation teams). You will also help shape how the team leverages AI-assisted development tools to ship faster and with higher quality.

What you’ll do

• Own the architecture and roadmap for eFlow Automator: the rule execution chain (event rule field mappings JEXL template action), the template library, and the surrounding tooling.
• Design and review JEXL scripts and FreeMarker snippets (SQL-snippet and JSON-payload types) used in production integrations, with particular focus on idempotency, error handling, and avoiding rule re-entry / infinite-loop patterns.
• Lead complex NetSuite and third-party integration work design new sync templates, harden existing ones, and own incident response when integrations break.
• Design and operate ActiveMQ-based messaging flows that underpin eFlow: queue and topic design, message contracts, redelivery and DLQ strategy, consumer scaling, and monitoring for stuck or back-pressured queues.
• Triage and resolve high-severity Automator issues: analyze jexl.log and automator.log, identify root cause across the 110+ REST endpoints and rule library, and produce durable fixes rather than hotfixes.
• Set engineering standards for scripting, logging (eConsole.print), error surfacing (data.setRealTimeError), template versioning, and cross-template state management via eGlobalContext.
• Partner with the support team on JIRA-tracked Automator tickets — both fixing them and identifying systemic patterns that need platform-level improvements.
• Champion the team’s use of AI-assisted development tooling (Claude Code, Claude API, and similar agentic coding tools): define where it adds leverage, set guardrails for code review and security, and build internal skills, prompts, and workflows that the rest of engineering can reuse.
• Contribute to the broader eFlow application where Automator intersects it: REST endpoint design, Workbench query patterns, lifecycle triggers, and data model evolution.

What you’ll bring

• 8+ years of professional software engineering experience, with at least 3+ years in a senior or principal role owning a significant platform or integration surface.
• Strong proficiency in Java (eFlow’s runtime), JavaScript-family expression languages, and SQL.
• Hands-on production experience with ActiveMQ (or a directly comparable JMS broker such as Artemis, RabbitMQ, or IBM MQ): producer/consumer design, queues vs. topics, durable subscriptions, transactions, redelivery policies, and DLQs.
• Experience with scripting / rules engines (JEXL, MVEL, Drools, Groovy, or similar) and templating engines (FreeMarker, Velocity, or similar). Direct eFlow Automator experience is a strong plus; transferable rules-engine experience is acceptable.
• Track record building and operating event-driven integrations against REST APIs — bonus points for NetSuite, SuiteTalk, or similar ERP integrations.
• Practical experience using AI-assisted coding tools (Claude Code, Claude API, Cursor, Copilot, or comparable) in real day-to-day work — not just demos. You can speak to where they help, where they hurt, and how to keep humans in the loop on review and security.
• Production-grade debugging skills: comfort reading large log files, distinguishing symptoms from root causes, and recognizing recurring failure patterns (recursive triggers, null-guard misses, type coercion bugs, message redelivery storms).
• Strong system-design instincts around idempotency, retry/backoff, observability, and graceful degradation in integration and messaging code.
• Excellent written and verbal communication — you will be documenting templates, writing post-incident notes, and explaining technical tradeoffs to non-engineering stakeholders.

Nice to have

• Background in manufacturing ERP, or order-to-c…