Senior Software Engineer

About the role

This role focuses on transforming product ideas into production-grade software within small, cross-functional teams. You will own the full lifecycle of features from initial design through deployment and iteration, ensuring high quality and reliability. Success in this position requires turning complex business requirements into elegant technical solutions that scale. You will collaborate closely with product managers and designers to refine requirements and uncover edge cases early. The work demands clear written and verbal communication to align technical constraints with business goals. You will spend significant time in planning sessions, code reviews, and debugging to maintain a sustainable pace. Strong engineers can distill complex system behavior into plain language for both technical and non-technical audiences. This position is critical for building the core infrastructure that powers Iterable's customer engagement platform.

Key facts

What you'll do

Design and implement new features for Iterable's engagement platform using robust and maintainable code.

Lead technical discussions and architecture decisions that balance scalability, performance, and time-to-market.

Collaborate with product managers to translate ambiguous requirements into well-defined technical specifications.

Write clean, testable code that adheres to team standards and best practices across the software development lifecycle.

Debug complex issues in production systems by analyzing logs, metrics, and traces to identify root causes quickly.

Partner with cross-functional stakeholders to ensure delivered solutions meet business objectives and user needs.

Optimize existing services for reliability, latency, and resource efficiency through careful refactoring and tooling.

Participate in on-call rotations to support critical services and respond to incidents as they arise.

Mentor junior engineers through code reviews, pair programming, and constructive feedback on design choices.

Champion engineering best practices such as testing, observability, and documentation across your team and the wider organization.

Requirements

Bachelor's degree in Computer Science, Engineering, or a related field, or equivalent practical experience.

Proficient experience writing production code in statically typed languages such as Java or C#.

Strong understanding of data access patterns and SQL for working with relational databases in Linux environments.

Experience building and maintaining services on cloud platforms such as AWS, Azure, or GCP.

Solid grasp of software design principles, including modularity, separation of concerns, and testability.

Comfort with command-line tools, scripting, and automation in Unix-like environments.

Ability to manage multiple priorities and deliver high-quality work in a fast-paced, agile development cycle.

Effective communication skills to articulate technical trade-offs and collaborate with both technical and non-technical colleagues.

Practical notes

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Engineers use statically typed languages like Java and C# to build scalable services. Reliable data access depends on SQL skills in Linux environments. Cloud platforms host modern services, and clear communication aligns engineering with business goals.

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.

About the company

pages. Let's shape the future of customer engagement together! The Senior Technical Support Specialist role offers an exciting opportunity for individuals with a passion for learning, problem-solving, and technology.