What are the responsibilities and job description for the IAM Platform & Developer Tooling Engineer - Jersey City / Houston TX (Onsite) position at Jobs via Dice?
Dice is the leading career destination for tech experts at every stage of their careers. Our client, ICS Global Soft, Inc., is seeking the following. Apply via Dice today!
Hi,
Hope you are doing well.
This is Sunil from ICS Global Soft. Kindly find the below job description and let me know your availability.
Role: IAM Platform & Developer Tooling Engineer
Location: Jersey City / Houston TX (Onsite)
Duration: Long Term
Must have: Go Python, Java (working level), IaC ownership, ForgeRock / IAM production, ArgoCD Jenkins, AI / Agent engineering, C4 architecture docs,
Role Identity:
This person extends the platform, integrates AIassisted tooling into engineering workflows, and pulls the team forward on what is technically possible. They are equally strong in code and infrastructure — not a specialist in either.
They have the same ForgeRock or equivalent IAM production requirement as Profile A. The differentiation is that their AI and developer tooling depth is a must-have, not a nice-tohave, and their primary language orientation skews toward Go and Python over Java.
This is the hire you make after Profile A is in place, or in parallel if headcount allows.
Must-Have Requirements
IAM & ForgeRock Domain
Sunil
Lead Technical Recruiter
Phone:
E-mail:
Linkedin:
Hi,
Hope you are doing well.
This is Sunil from ICS Global Soft. Kindly find the below job description and let me know your availability.
Role: IAM Platform & Developer Tooling Engineer
Location: Jersey City / Houston TX (Onsite)
Duration: Long Term
Must have: Go Python, Java (working level), IaC ownership, ForgeRock / IAM production, ArgoCD Jenkins, AI / Agent engineering, C4 architecture docs,
Role Identity:
This person extends the platform, integrates AIassisted tooling into engineering workflows, and pulls the team forward on what is technically possible. They are equally strong in code and infrastructure — not a specialist in either.
They have the same ForgeRock or equivalent IAM production requirement as Profile A. The differentiation is that their AI and developer tooling depth is a must-have, not a nice-tohave, and their primary language orientation skews toward Go and Python over Java.
This is the hire you make after Profile A is in place, or in parallel if headcount allows.
Must-Have Requirements
IAM & ForgeRock Domain
- Has shipped production IAM systems using ForgeRock Identity Platform,
- PingFederate, Okta, or Keycloak at enterprise scale
- Understands SAML 2.0, OAuth 2.0, OpenID Connect, and SCIM at an implementation
- and debugging level — not just conceptually
- Has designed or contributed to identity architecture: SSO, MFA, delegated administration, policy-based access control across multiple application integrations
- Can articulate IAM failure modes and their production mitigations
- Has shipped production AI-powered systems — not demos, not prototypes on a laptop. Real systems with real users, real failure modes, and real operational considerations.
- Has designed multi-agent architectures — understands memory management, tool orchestration, context window limitations, and agent failure modes at a production level
- Has built or integrated MCP servers or equivalent tool ecosystems — custom tool definitions, AI-to-system integrations, or LLM-assisted engineering workflows
- Has worked with at least one major LLM API (Anthropic Claude, OpenAI) at the integration level — prompt engineering, RAG pipelines, agentic loops, not just API calls
- Has navigated enterprise AI constraints — data residency requirements, security review of AI tooling, local LLM stack deployment (Ollama or equivalent) when external APIs are not permitted
- Strong working knowledge of Terraform — has written and contributed to module architectures, understands workspace-centric state management, can own IaC delivery independently
- ArgoCD on AWS EKS — has configured and maintained GitOps delivery pipelines on Kubernetes in a production environment
- Multi-account AWS at a working level — understands the account structure, IAM trust relationships, and cross-account patterns
- Jenkins at a contributing level — can write and maintain pipelines, understands the trigger chain, does not need to be the pipeline architect
- ArgoCD at an ownership level — this is their primary CI/CD surface
- Understands GitOps principles at an implementation level, not just conceptually
- Go — production-quality. Primary language for platform services and agent backends.
- Python — production-quality. Primary language for AI/agent development, automation, and tooling.
- Java — working level minimum. Must be able to read, debug, and contribute to existing Java services without requiring a Java specialist alongside them.
- Identical requirements to Profile A on C4 modeling, stakeholder presentations, ADR authorship, and professional operating standards.
- C4 model architecture diagrams as a primary design artifact
- Technical documentation written for broad, mixed audiences
- ADR authorship and design defense under questioning
Sunil
Lead Technical Recruiter
Phone:
E-mail:
Linkedin: