Tines provides a vendor-agnostic, no-code drag-and-drop workflow automation platform for security and IT teams that connects to any API, runs cloud or on-premises, and automates incident response.
<div class="content-intro"><p>Founded in 2018 with co-headquarters in Dublin and Boston, Tines powers some of the world's most important workflows. Our intelligent workflow platform applies AI, automation, and integration with human ingenuity to drive real business results. </p> <p>Tines serves a diverse range of customers, from startups to public companies, including Canva, Databricks, Elastic, Kayak, Intercom, and McKesson. As an integrator across the entire tech stack, Tines is vendor-agnostic integrating with any API-enabled service. This flexibility enables our customers to achieve their highest-priority goals faster. And because Tines is secure and private by design, it’s popular with security, IT, engineering, finance, and other security-focused teams.</p> <p>At Tines, we're driven by our values of Simplicity, Speed, and Soundness. We're committed to delivering exceptional customer experiences while fostering a company culture that nurtures individual curiosity, growth, and integrity. We’re excited about what’s next, and we’re looking for others to join us on our journey.</p></div><p>You’ll join the team primarily responsible for scaling the throughput and performance of the backend job processing system and code execution engines that power Tines’ intelligent workflows. However, since we’re still a small but growing software engineering organization, this role is not strictly limited to any single part of our product or stack.</p> <p>This role is about more than writing code: you'll have an influential voice in shaping our technical direction, our product, and our culture. We have a hugely supportive and collaborative engineering team that takes great pride in the work we do and the challenges we solve. We’re eager to help grow and nurture each other’s abilities and also create an environment where we have the ability to do our very best work.</p> <p><strong>Location:</strong> US Eastern states ideally. </p> <p>You can work fully remotely from anywhere in EST states, with a preference for the Boston area. You can make use of our Tines office space in Boston to meet up with other members of the engineering team when you wish.</p> <h4><strong>In this role, you’ll:</strong></h4> <ul> <li>Lead the technical direction for some of Tines’ most critical systems. </li> <li>Make valuable changes in our codebase in your first week, and see them live in production minutes after merging them.</li> <li>Shape how jobs and code are executed at the very heart of our application, to help us <a href="https://www.tines.com/about/">power the world’s most important workflows</a>.</li> <li>Write and review high-quality, well-tested code to ensure that we’re creating a stable product for our customers, and a stress-free codebase for ourselves.</li> <li>Identify areas for improvement, both in our codebase and in how we work, and share the responsibility of making our team better.</li> <li>Own the problems you’re solving - and the software you write to solve them - all the way to production and beyond, responding to customer feedback to improve those solutions.</li> <li>Use your knowledge to mentor other engineers in our team, providing support and guidance to help them grow their abilities.</li> </ul> <h4><strong>Projects you might work on:</strong></h4> <ul> <li>Build robust, high-availability systems that can support massive data throughput requirements. </li> <li>Improve <a href="https://www.tines.com/docs/actions/">action</a> throughput to meet our growing customers’ scale.</li> <li>Create internal and customer-facing controls that allow Tines and our customers to configure job prioritization levels, ensuring the most critical workflows are executed in a timely manner.</li> <li>Build features that allow customers to <a href="https://www.tines.com/docs/actions/tools/run-script/">execute code</a> in our product.</li> <li>Ensure customers’ jobs are executed in a <a href="https://explained.tines.com/en/articles/9887588-what-is-action-run-orchestration">balanced and fair manner</a>, particularly on multitenant stacks. </li> <li>Write <a href="https://www.tines.com/blog/engineering">a blog post</a> to share something interesting we learned with the community.</li> </ul> <h4><strong>Is this role right for you?</strong></h4> <ul> <li><strong>Typically 10+ years as a professional software engineer.</strong> Proven track record of success as a staff software engineer. We’re looking for candidates with a well of experience to draw from, including some of:</li> <ul> <li>Linux systems expertise in namespaces, file descriptors, Unix sockets, mounts, networking, and process isolation.</li> <li>Experience with container runtimes, orchestration, or code execution platforms.</li> <li>Filesystem and storage experience, including POSIX behavior, content-addressed storage, and crash recovery.</li> <li>Experience in building and owning low-level system primitives in Rust or Go.</li> <li>Strong debugging skills: able to build focused reproducers for complex kernel, runtime, and storage issues, and use logs, traces, metrics, and tests to isolate root cause.</li> </ul> <li><strong>Your abilities matter, not your education or exactly where you’ve worked. </strong>We just need you to show us that you have accumulated the foundational skills and knowledge needed to succeed.</li> <li><strong>This role is broad, not specialized.</strong> While your main focus will be on our backend job processing system and code execution engines, you’ll work across our stack, from infrastructure changes to the frontend. You don’t need to have experience in all of these areas, but you will need to be excited to pitch in anywhere when needed, with the support of your teammates. This allows us to be more effective as a team, and provides a lot of opportunities for you to learn.</li> <li><strong>We’re focused on the most important problems, not the most interesting ones.</strong> Your time and energy are limited, so in