Senior Software Engineer, Iru

• 5+ years of professional software engineering experience (or equivalent depth)
• Strong front-end engineering experience building complex web applications with clear ownership of architecture decisions
• Full-stack capability and willingness to contribute meaningfully beyond the UI (this is not a pure front-end role)
• Comfort working in environments with ambiguity (e.g., front-end stack decisions still being made) and taking initiative to drive clarity
• Experience building internal tools/admin surfaces and/or products used by technical or operational teams
• Strong engineering judgment and ability to communicate tradeoffs clearly
• Senior-level scope and maturity (this role is targeted at Senior level; not principal/staff scope)

Desirable

• As a Senior Software Engineer (Full‑Stack, Front‑End Dominant) on Iru’s Connect team, you’ll join a small, high-ownership group building an integrations platform (iPaaS) that powers workflows across third-party systems (e.g., Slack, Microsoft Teams, Google Calendar)
• You’ll play a leading role in establishing the front-end architecture for an internal admin product that’s expected to become more customer-facing over time—while partnering closely with a backend-heavy team and growing into deeper platform work
• This is a role for engineers who thrive with ambiguity, want to own technical direction, and can ship quickly with strong product and engineering judgment
• Own front-end architecture from the ground up: Bring structure to an ad hoc front end—establish patterns for UI architecture, state management, performance, quality, and maintainability
• Build an internal admin product (with a customer-facing trajectory): Deliver end-to-end experiences for internal tooling that will increasingly matter to external users
• Operate as a true full-stack engineer: Expect a split of roughly 65–70% front end / 30–40% backend, with the role trending more platform/backend over time (after ~6 months)
• Partner on platform and integrations work: Contribute to systems that abstract third-party vendor complexity and enable rapid integration development
• Make and document key technical decisions: Evaluate tradeoffs pragmatically and choose solutions that fit the team’s needs—not trends
• Work with high autonomy: Identify what needs to be built, propose solutions, and execute with minimal hand-holding in a fast-moving environment
• Collaborate closely with a small team: Engage in code reviews and design discussions, raising the bar on engineering quality as the team scales