Senior Software Engineer | Remote | AI SaaS Software Role

Process Street is an AI software and compliance operations platform startup from San Francisco. We help our customers build, document, automate, and track recurring workflows. Our platform automates the work, enforces the standards, and proves compliance so our global customers can run their businesses. We service over 3k customers around the world, and are VC-backed by Accel, Salesforce, and Atlassian.

To make recurring work fun, fast, and faultless for teams everywhere.

Process Street was founded on a strong belief in the work-life benefits of a healthy, collaborative remote culture. We value flexibility because many of us are parents, travelers, or just creatives who aren't inspired by the construct of a mundane 9-to-5. Spread across 9 different time zones, we communicate asynchronously, work autonomously, and take real ownership of our work. We know human connections are what make teams strong, so we regularly do coffee chats, game-playing, story-telling, and more, to build strong relationships.

If you’re entrepreneurial and seek an environment that values impact, ownership, and flexibility we look forward to meeting you! 

We’re looking for a Senior Software Engineer to help architect and evolve Process Street into an AI-native product and engineering organization.

This is not a traditional “just ship tickets” role. We’re looking for someone who is deeply comfortable working in multi-session coding environments, leveraging tools like Claude Code, Codex, and other agentic workflows to design, build, and iterate faster than conventional development allows.

You’ll operate at the intersection of:

• Product engineering (React / Scala / APIs)
• AI-assisted development systems
• Internal tooling, agents, and developer workflows

You’ll help us rethink how software is built - from how code is written, to how systems evolve, to how teams collaborate with AI.

• →Architect and evolve backend systems (Scala / Play / Postgres / AWS)
• →Design and deploy scalable APIs and AI-assisted services
• →Own feature development from end 2 end (ideation to production)
• →Build frontend features using React, Chakra, Storybook, and modern state tools
• →Develop and maintain agent-driven development workflows
• →Use tools like Claude Code / Codex to accelerate implementation, debugging, and refactoring across multiple sessions in parallel
• →Create internal tooling, prompts, and “engineering systems” that improve velocity and code quality
• →Optimize performance across frontend, backend, and AI-assisted pipelines
• →Help define best practices for AI-native software development
• →Eventually lead a small team (2–3 engineers) and shape how they work with AI

• 7+ years of software engineering experience
• Strong experience with backend systems (Scala, or Java / Ruby / C#)
• Strong experience with JavaScript and React
• Experience building and scaling SaaS products
• Deep familiarity with AI coding tools (Claude Code, Codex, Cursor, etc.)
• Comfort working across multi-session, agent-driven workflows
• Strong intuition for when to rely on AI vs. manual implementation
• Experience designing systems, not just implementing features
• Excellent written communication (async-first culture)

• You live in a timezone between UTC -6 to UTC+2 (North American Central Time through Central European Summer Time). 
• You think of coding as a collaboration with AI, not a solo activity
• You’re a Claude Code / Codex power user - you understand configuration deeply, know how to structure contexts, and can reliably steer long-running coding sessions
• You’ve experimented with or built:
• Custom dev workflows using LLMs
• Internal tools, prompts, and “skills” for engineering
• Agent-like systems that operate across files, repos, or tasks
• You’re comfortable jumping between:
• Writing code
• Designing systems
• Prompting / guiding AI agents
• Debugging AI-generated output
• You care about leverage. Getting more done with smarter workflows, not just more effort.

• You want agency. PMs provide a problem statement and some guidelines – no tickets, no detailed specs, no high-fidelity solutions, and no estimates. Designers and engineers are trusted to craft the best solution possible in the cycle using user research, data, experience, and grit. During the 2-week cooldowns, you have the autonomy to work on what's important to you – including code maintainability or making the team faster. If a lot of responsibility, freedom, and ambiguity sounds refreshing, this role is for you.
• You love the process but loathe meetings, bureaucracy, and ceremony. We think process is a tool. Used well, it makes us a better, faster team. But when it's not doing that, we drop it. We avoid unnecessary meetings whenever possible. A typical week for our engineers and designers has fewer than 5 hours of meetings.
• You want to have a big impact. We're a small team, and we're still at an early stage. We don't have designated areas of responsibility, and everyone wears the product hat. Every cycle brings new challenges, and your sphere of influence is wide. You love the variety and don't want to be shackled to a single project for years.

• 6-week cycles: solve problems, not tickets
• 2-week cooldowns: improve systems, tooling, or explore ideas

• Thrive in ambiguity and autonomy
• Prefer ownership over instructions
• Care about shipping real outcomes
• Want to rethink how product and engineering are done in an AI-first world

• Backend: Scala 3 / Play 3, Postgres, Redis
• Frontend: React, Redux, React Query, Chakra, XState
• Infra: AWS, Docker, CircleCI
• AI Workflow: Claude Code, Codex, agent-based tooling (evolving rapidly)

This is not just a “use AI to go faster” role.

• How engineers collaborate with AI
• How codebases are structured for agent interaction
• How workflows evolve when AI is a first-class participant

• Experience with functional programming
• Experience building internal dev tools or platforms
• Experience designing prompt systems or reusable AI workflows
• Opinions about how coding will change in the next 3–5 years (and the ability to act on them)

• The Inside Secrets of a Process Street Full Stack Engineer
• An Insider Look Into How We Built the Process Street Slack App (In 2 Weeks!)