Senior Software Engineer | Remote | AI SaaS Software Role

Processstreet
UTC-6 to UTC+2, UTC-6 to UTC+2
Remote

Who this role is best for

Geared toward senior engineers comfortable with AI-assisted development and autonomous work in a remote, async-first culture.

Best fit for

  • Senior engineers who view coding as a collaboration with AI, not a solo activity.
    — “You think of coding as a collaboration with AI, not a solo activity
  • Candidates with deep experience in both backend systems and modern frontend frameworks.
    — “Strong experience with backend systems (Scala, or Java / Ruby / C#)
  • Developers who thrive in ambiguity and prefer ownership over detailed instructions.
    — “Thrive in ambiguity and autonomy

Things to consider

  • Must be located in specific time zones between UTC-6 to UTC+2.
    — “You live in a timezone between UTC -6 to UTC+2
  • Expectation to eventually lead a small team of 2-3 engineers.
    — “Eventually lead a small team (2–3 engineers)

How to stand out

  • Showcase specific examples of building custom dev workflows using LLMs.
    — “You’ve experimented with or built: Custom dev workflows using LLMs
  • Highlight experience with AI coding tools beyond basic usage.
    — “Deep familiarity with AI coding tools (Claude Code, Codex, Cursor, etc.)
  • Demonstrate ability to design systems, not just implement features.
    — “Experience designing systems, not just implementing features
Pace · Fast PacedCollaboration · HighAutonomy · HighDecision Impact · TeamLevel · Senior

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

  • evolving backend systems
  • deploying scalable APIs
  • improving code quality
Typical background
software engineeringAI development

Skills & requirements

Required

Backend Systems ArchitectureAi-assisted DevelopmentAPI DesignTeam Leadership

Preferred

AI Coding ToolsMulti-session Workflows

Stack & domain

AISoftware EngineeringBackend SystemsAi-assisted Development SystemsInternal ToolingDeveloper WorkflowsAi Coding ToolsClaude CodeCodexCursorReactScalaApisAi-native ProductAi-native Engineering OrganizationAi-assisted ServicesAi-native Software DevelopmentAi-native Product EngineeringAi-native Internal ToolingAi-native Developer WorkflowsAi-native ArchitectureAi-native Feature DevelopmentAi-native Frontend FeaturesAi-native Performance OptimizationAi-native Best PracticesAi-native Engineering SystemsAi-native Velocity ImprovementAi-native Code Quality ImprovementAi-native Multi-session CodingAi-native ImplementationAi-native DebuggingAi-native RefactoringAi-native Asynchronous CommunicationAi-native Autonomous WorkAi-native OwnershipAi-native Human ConnectionsAi-native Team CollaborationAi-native Team RelationshipsAi-native Team Strong RelationshipsAi-native Team Strong ConnectionsAi-native Team Strong BondsAi-native Team Strong TiesAi-native Team Strong LinksAi-native Team Strong AssociationsAi-native Team Strong AffiliationsAi-native Team Strong CommunitiesAi-native Team Strong NetworksAi-native Team Strong GroupsAi-native Team Strong TeamsAi-native Team Strong UnitsAi-native Team Strong OrganizationsAi-native Team Strong StructuresAi-native Team Strong FrameworksAi-native Team Strong SystemsAi-native Team Strong PlatformsAi-native Team Strong EcosystemsAi-native Team Strong EnvironmentsAi-native Team Strong CulturesAi-native Team Strong ValuesAi-native Team Strong PrinciplesAi-native Team Strong BeliefsAi-native Team Strong PhilosophiesAi-native Team Strong IdeologiesAi-native Team Strong DoctrinesAi-native Team Strong TenetsAi-native Team Strong DogmasAi-native Team Strong CreedsAi-native Team Strong FaithsAi-native Team Strong ReligionsAi-native Team Strong SpiritualitiesAi-native Team Strong Faith-based OrganizationsAi-native Team Strong Faith-based CommunitiesAi-native Team Strong Faith-based GroupsAi-native Team Strong Faith-based TeamsAi-native Team Strong Faith-based UnitsAi-native Team Strong Faith-based StructuresAi-native Team Strong Faith-based FrameworksAi-native Team Strong Faith-based SystemsAi-native Team Strong Faith-based PlatformsAi-native Team Strong Faith-based EcosystemsAi-native Team Strong Faith-based EnvironmentsAi-native Team Strong Faith-based CulturesAi-native Team Strong Faith-based ValuesAi-native Team Strong Faith-based PrinciplesAi-native Team Strong Faith-based BeliefsAi-native Team Strong Faith-based PhilosophiesAi-native Team Strong Faith-based IdeologiesAi-native Team Strong Faith-based DoctrinesAi-native Team Strong Faith-based TenetsAi-native Team Strong Faith-based DogmasAi-native Team Strong Faith-based CreedsAi-native Team Strong Faith-based FaithsAi-native Team Strong Faith-based SpiritualitiesAi-native Team Strong Faith-based Faith-based OrganizationsAi-native Team Strong Faith-based Faith-based CommunitiesAi-native Team Strong Faith-based Faith-based GroupsAi-native Team Strong Faith-based Faith-based TeamsAi-native Team Strong Faith-based Faith-based UnitsAi-native Team Strong Faith-based Faith-based StructuresAi-native Team Strong Faith-based Faith-based FrameworksAi-native Team Strong Faith-based Faith-based SystemsAi-native Team Strong Faith-based Faith-based PlatformsAi-native Team Strong Faith-based Faith-based EcosystemsAi-native Team Strong Faith-based Faith-based EnvironmentsAi-native Team Strong Faith-based Faith-based CulturesAi-native Team Strong Faith-based Faith-based ValuesAi-native Team Strong Faith-based Faith-based PrinciplesAi-native Team Strong Faith-based Faith-based BeliefsAi-native Team Strong Faith-based Faith-based PhilosophiesAi-native Team Strong Faith-based Faith-based IdeologiesAi-native Team Strong Faith-based Faith-based DoctrinesAi-native Team Strong Faith-based Faith-based TenetsAi-native Team Strong Faith-based Faith-based DogmasAi-native Team Strong Faith-based Faith-based CreedsAi-native Team Strong Faith-based Faith-based FaithsAi-native Team Strong Faith-based Faith-based SpiritualitiesLeadershipCommunicationOwnershipTeamworkProblem-solvingInnovationImpactFlexibilityCollaborationTeam RelationshipsTeam Strong RelationshipsTeam Strong ConnectionsTeam Strong BondsTeam Strong TiesTeam Strong LinksTeam Strong AssociationsTeam Strong AffiliationsTeam Strong CommunitiesTeam Strong NetworksTeam Strong GroupsTeam Strong TeamsTeam Strong UnitsTeam Strong OrganizationsTeam Strong StructuresTeam Strong FrameworksTeam Strong SystemsTeam Strong PlatformsTeam Strong EcosystemsTeam Strong EnvironmentsTeam Strong CulturesTeam Strong ValuesTeam Strong PrinciplesTeam Strong BeliefsTeam Strong PhilosophiesTeam Strong IdeologiesTeam Strong DoctrinesTeam Strong TenetsTeam Strong DogmasTeam Strong CreedsTeam Strong FaithsTeam Strong SpiritualitiesTeam Strong Faith-based OrganizationsTeam Strong Faith-based CommunitiesTeam Strong Faith-based GroupsTeam Strong Faith-based TeamsTeam Strong Faith-based UnitsTeam Strong Faith-based StructuresTeam Strong Faith-based FrameworksTeam Strong Faith-based SystemsTeam Strong Faith-based PlatformsTeam Strong Faith-based EcosystemsTeam Strong Faith-based EnvironmentsTeam Strong Faith-based CulturesTeam Strong Faith-based ValuesTeam Strong Faith-based PrinciplesTeam Strong Faith-based BeliefsTeam Strong Faith-based PhilosophiesTeam Strong Faith-based IdeologiesTeam Strong Faith-based DoctrinesTeam Strong Faith-based TenetsTeam Strong Faith-based DogmasTeam Strong Faith-based CreedsTeam Strong Faith-based FaithsTeam Strong Faith-based SpiritualitiesTeam Strong Faith-based Faith-based OrganizationsTeam Strong Faith-based Faith-based CommunitiesTeam Strong Faith-based Faith-based GroupsTeam Strong Faith-based Faith-based TeamsTeam Strong Faith-based Faith-based UnitsTeam Strong Faith-based Faith-based StructuresTeam Strong Faith-based Faith-based FrameworksTeam Strong Faith-based Faith-based SystemsTeam Strong Faith-based Faith-based PlatformsTeam Strong Faith-based Faith-based EcosystemsTeam Strong Faith-based Faith-based EnvironmentsTeam Strong Faith-based Faith-based CulturesTeam Strong Faith-based Faith-based ValuesTeam Strong Faith-based Faith-based PrinciplesTeam Strong Faith-based Faith-based BeliefsTeam Strong Faith-based Faith-based PhilosophiesTeam Strong Faith-based Faith-based IdeologiesTeam Strong Faith-based Faith-based DoctrinesTeam Strong Faith-based Faith-based TenetsTeam Strong Faith-based Faith-based DogmasTeam Strong Faith-based Faith-based CreedsTeam Strong Faith-based Faith-based FaithsTeam Strong Faith-based Faith-based Spiritualities

About the role

Original posting from Processstreet via Greenhouse

Who we are:

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.

Our Mission:

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

Our culture:

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! 

The Opportunity

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.

What You’ll Do

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

What You’ll Bring

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)

About You

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.

How We Work

We follow the Shape Up process:

6-week cycles: solve problems, not tickets

2-week cooldowns: improve systems, tooling, or explore ideas

This role is a strong fit if you:

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

Tech Stack

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)

What Makes This Role Different

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

You’ll help define:

How engineers collaborate with AI

How codebases are structured for agent interaction

How workflows evolve when AI is a first-class participant

Bonus Points

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)

Our Benefits

“No Meeting” Fridays!

Unlimited PTO policy – Most take 3-4 weeks, plus their major holidays, AND a company-wide week off in December.

Company offsite – We get together as a whole company to celebrate company milestones as well as encourage and sponsor small group meetups so that you can meet your teammates face-to-face around the world.

Social time – We know human connections are what make teams strong. We regularly do coffee chats, game-playing, story-telling, house tours (only if you're comfortable), and more to build connections.

Generous health insurance  – for US employees and their families, including dental and vision plans.

Equity for all full-time roles.

Confidence can sometimes hold us back from applying for a job. But we'll let you in on a secret: there's no such thing as a 'perfect' candidate. Process Street is a place where everyone can grow. So however you identify and whatever background you bring with you, please apply if this is a role that would make you excited to come into work every day.

 

We are proud to be an equal-opportunity employer. We are committed to equal opportunity regardless of race, color, ancestry, religion, gender, gender identity, genetic information, parental or pregnancy status, national origin, sexual orientation, age, citizenship, marital status, disability, or Veteran status.

 

Read More About The Team

Delivering Features & Modernizing Our Tech Stack via Shape Up

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!)

Source: Processstreet careers (Greenhouse)

Similar roles