Work locations: Boston MA, Quincy MA, Stamford CT, Princeton NJ

Who We Are Looking For

Are you a hands-on engineer who would rather build automation than manage a roadmap? Were hiring a Process Automation Engineer to design and support automated business workflows. This is a makers role. Youll write code, wire up integrations, and turn manual processes into automation that holds up in a regulated environment.

The role sits within Process Engineering & Automation at State Street Investment Management (formerly State Street Global Advisors). Day to day, youll work with the Process Automation Lead, business architecture, business units, and technology teams to turn process designs into working software. Were moving toward a Product, Platform, and Service operating model. AI and agentic automation are part of the toolkit, but so are boring, reliable things like scheduled jobs, process models and well-tested APIs. Your job is to pick the right tool for the problem, build it well, and make sure it doesnt page anyone at 3am. No hype-driven adoption. Practical automation that runs in production without drama.

Key Responsibilities

• Build the automation. Design, build, test, and support automated business workflows in Appian (or whatever replaces it). This is where you spend most of your time. Youre hands-on, in the code, every week.
• Fix broken processes. Work with business architecture and business units to take manual, high-friction workflows and turn process designs into software that runs. Sometimes the process design is clean. Sometimes youll push back on it because it wont survive contact with real systems.
• Own your delivery end to end. Carry your work requirements through deployment and support. What you ship meets enterprise standards for security, resilience, controls, and maintainability. Regulated environment, no shortcuts.
• Connect systems. Build integrations between the orchestration platform and the systems around it. Clean APIs, sensible contracts, nothing held together with duct tape.
• Test and support what you build. Write the tests, fix the defects, and stay close to your solutions in production. Instrument processes so operations can see where things get stuck before users file a ticket.
• Try new tools. AI, agentic automation, whatever shows up next. Pilot what looks promising, be honest about what doesnt work yet, share what you learn with the team.
• Work across pods. We operate in a matrix model with cross-functional pods spanning product, platform, and service lines. Youll embed with different pods depending on the work, collaborating with product owners, platform engineers, and service teams who know the business domain. Your job is to bring automation engineering, not sit in a silo waiting for requirements to land in your lap.
• Raise the bar. Follow the teams delivery controls and engineering standards. Help improve them. If somethings slowing everyone down, say so and propose a fix.

Qualifications

Required:

• 5+ years in software engineering, process automation, or solution delivery. Youve built and shipped production systems, not just designed them on whiteboards.
• Hands-on builder. You write and review code regularly, and you want to keep doing that. This is not a step away from the keyboard.
• Youve built workflow automation on a low-code or orchestration platform (Appian, Pega, Camunda, similar) and wired it into the systems around it. If youve only dragged and dropped, thats not enough.
• Solid fundamentals: APIs, integration patterns, testing, SDLC. You can point to a process you improved and say what changed in specific terms.
• Youve worked in a regulated environment, or you can convince us you understand why controls exist and how to deliver in a matrixed org where nobody reports to you.
• Bachelors in Computer Science, Engineering, or related field.

Preferred:

• Investment management, asset management, or financial services background. You know what a NAV is. Youve seen what manual reconciliation actually looks like at scale.
• Appian experience. Bonus if youve touched process modeling tools like ARIS or architecture repositories like Ardoq.
• Youve used AI and agentic automation enough to have a real opinion on where they work and where they fall apart. Not just enthusiasm. Judgment.
• Exposure to BPMN, capability modeling, or value streams. Cloud experience in AWS, Azure, or GCP.
• A relevant certification (Appian Certified Developer, etc.) is a plus but wont make up for weak fundamentals.