Software Development Lead / Engineering Team Lead— Labor Management System (LMS)

About SocioSquares

SocioSquares is the official brand name of 2 companies: Socio Digitech Inc. (USA) and SocioSquare Digitech Pvt. Ltd. SocioSquares is a digital marketing company that combines creativity and technology to help businesses scale their digital presence in India and the United States. A mix of software and heartware. At SocioSquares, we’re a team of 40\+ creative and online marketing experts in the US and India, 17 years in business with offices in Houston, Texas, California, and India. Hiring requirements for a contractor role were established alongside improved metrics and performance tracking goals. The project structure is defined as a 1099 contractor role for the duration of the 8 to 10-month engineering lead assignment.

We are rapidly expanding our presence in the US and looking for a Software Development Lead Role.

About the role

This role owns the technical success of the replacement end-to-end, and it demands fluency in two worlds. The first is the legacy estate: how Blue Yonder actually behaves, assignment operations, clock-punch and schedule interpretation, job-code mapping, engineered standards, integrator transactions and batch feeds, and the PAY/INC output the mainframe depends on, including the realities that documentation does not capture. The second is the target platform: a Python microservice architecture on Kubernetes with Kafka event streaming, PostgreSQL as the immutable system of record, and a Next.js supervisor UI. As Technical Lead, you will translate the approved product and technical requirements into a working system, serve as the authority on legacy behavior during discovery and validation, make and document the architectural decisions, lead the engineering team through the build, and be accountable for byte-equivalent payroll reconciliation during each DC’s parallel run before cutover.

What you will do

Architecture and platform ownership

• Own system architecture across all services: WMS API receiver, legacy file bridge, pay engine, ELS engine, supervisor web UI, and mainframe file emitter.
• Define and defend the data architecture: immutable append-only fact tables, supersede chains for punch corrections, JSONB audit snapshots, and 7–10 year SOX retention.
• Make and document key technical decisions and trade-offs, including open questions such as the MODAPTS re-derivation vs. delivered-element-library path for the standards engine.

Legacy authority and migration

• Serve as the technical authority on legacy Blue Yonder LMS behavior, resolving ambiguities in how the current system pairs punches, applies standards, and produces pay, and closing the open questions in the current design.
• Own the integration architecture across the transition: the four inbound batch feeds (clock punches, job sign-ons, work records, quality audits), the target REST/Kafka ingestion path with idempotency and gap detection, and the fixed-format mainframe payroll interface that must remain byte-identical.
• Design the legacy file bridge, parsing of the existing colon-framed .bch files, error-state handling, and clean per-DC decommissioning as each WMS API client goes live, and coordinate the OpenAPI contract with the WMS team.
• Drive data migration and validation from the legacy system, working within the constraint that only \~2 weeks of discrete detail survive the legacy purge window at any time.

Delivery, quality, and leadership

• Lead the engineering team day to day: design reviews, code reviews on payroll-affecting components, mentoring, and technical direction across the pay-engine, ingestion, ELS, and UI tracks.
• Own the parallel-run validation strategy: field-level and byte-level comparison of new-system PAY/INC output against Blue Yonder for 4–8 weeks per DC, discrepancy triage, rollback plans, and go/no-go input for each cutover.
• Partner with DC admins, supervisors, payroll/HR, finance, and the mainframe team; translate operational knowledge into requirements the build team can implement.
• Enforce SOX §404 controls in the engineering process: segregation of duties in RBAC, complete audit trails on pay-affecting actions, and two-person approval on payroll-affecting deployments.

Required qualifications

• The role requires an engineering team lead with 10\+ years of experience. The candidate must have prior experience developing a Labor Management System or Warehouse Management System and possess significant knowledge of how systems like Blue Yonder Labor Management Systems operate. Hands-on Blue Yonder (RedPrairie/JDA) WMS/LMS experience — implementation, configuration, or development, including labor management concepts: assignment operations, labor standards and goal times, scheduling, and labor performance reporting.
• Deep integration expertise: integrator transactions, EDI/batch file feeds, host-system mapping (SAP, AS400, or mainframe), and modern event streaming (Kafka or comparable).
• Strong proficiency in Python (or deep Java with demonstrated Python capability) and expert-level SQL — Oracle, DB2, or PostgreSQL — including performance tuning of production WMS/LMS workloads and high-integrity transactional data modeling.
• Experience designing or building cloud-native, event-driven microservice architectures deployed on Kubernetes (GCP).
• Track record leading legacy-to-modern migrations: data mapping, parallel-run or shadow-mode validation, phased multi-site go-lives, and production cutover support.
• Demonstrated technical leadership: solution-design workshops, code reviews, technical governance, and mentoring engineers across concurrent workstreams.

Preferred qualifications

• Prior work on financially material systems, payroll, timekeeping, incentive pay, billing, with audit and reconciliation requirements; familiarity with FLSA regular-rate rules and state wage-and-hour variation.
• MOCA and Blue Yonder page-builder / report development (Jasper or similar), useful for decoding legacy behavior during discovery and validation.
• PostgreSQL-specific depth: partitioning, JSONB, replication, and operational tuning.
• Multi-DC production support background, including on-call triage of labor and integration incidents.
• Experience operating under SOX §404 change-management and access controls.

Pay: $65\.00 - $90\.00 per hour

Application Question(s):

• Are you a US citizen or Green Card Holder?
• 2\. Which of the following Blue Yonder modules have you worked on? Warehouse Management System (WMS), Labor Management System (LMS), MOCA Development, Integrator, Page Builder, Jasper Reports, None of the above
• 3\. Have you led the design or migration of a Labor Management System (LMS) or Warehouse Management System (WMS)?
• Which programming languages are you proficient in? 1\.Python,2\.Java,3\.SQL,4\.C#,5\.Go
• Which databases have you worked with in production? 1\. PostgreSQL, 2\. Oracle, 3\. DB2, 4\. SQL Server, 5\. MySQL
• Have you led the implementation or migration of a Warehouse Management System (WMS) or Labor Management System (LMS)?
• Have you worked on payroll, labor management, timekeeping, or other financially sensitive systems requiring audit trails and compliance (e.g., SOX)?
• Have you integrated enterprise systems using batch files, EDI, REST APIs, or message queues? If yes, elaborate.
• Have you designed event-driven microservices using Kafka and Kubernetes?
• Are you willing to go to on site sometime like once a month?
• How soon can you join?
• Your email id

Work Location: Remote