• Own and evolve the core architecture of our platforms • Define and guide the strategy for our cloud environments • Own the design and governance of data systems • Design and evolve automated pipelines for code deployment • Serve as the technical voice during product ideation • Partner with Engineering Manager to manage technical debt

Role Description We are seeking a Full-Stack Technical Lead to guide application architecture, full-stack engineering delivery, API integration strategy, and hands-on implementation across a modern secure software platform. This role will lead technical decisions across user interfaces, backend services, service integration, and engineering quality while mentoring developers and ensuring delivery consistency from design through deployment readiness. Key Responsibilities - Lead full-stack design and development across frontend, backend, and integration layers. - Define application architecture, coding standards, and integration patterns. - Own technical decomposition of requirements into implementable user stories and engineering tasks. - Guide backend API design, service interactions, validation patterns, and application security controls. - Lead portal or web application architecture including role-based interfaces, user workflows, and data interaction patterns. - Review code, pull requests, technical designs, and implementation approaches across the team. - Troubleshoot complex technical issues spanning frontend, backend, and environment concerns. - Support release planning, technical validation, and production-readiness activities. Qualifications - Bachelor's degree in Computer Science, Software Engineering, or related field, or equivalent practical experience. - 7+ years of experience in full-stack software development. - 3+ years of experience in a technical lead or senior engineering leadership role. - Strong experience designing and delivering modern web applications and backend APIs. - Experience building applications in security-sensitive environments with strong access control, logging, and audit requirements. - Familiarity with secure application design patterns that support NIST SP 800-171 objectives, including role-based access, session management, traceability, and secure error handling. - Ability to guide engineering teams on implementing features in ways that preserve compliance and auditability. Preferred Qualifications - Experience working with approved cryptographic libraries, security boundaries, and application integration patterns that must align to FIPS 140-3 expectations. - Exposure to higher-assurance engineering patterns associated with NIST SP 800-172 environments. - Experience building admin portals, operational dashboards, or workflow-heavy enterprise applications. - Familiarity with observability, auditability, and operational support requirements. Success Profile - Strong technical ownership. - Balances speed and engineering rigor. - Mentors others effectively. - Comfortable in hands-on and leadership modes. This is a remote position.

Hi! I'm Ryan, the Head of Marketing at Modash. I'm looking for a GTM Engineer to join our marketing team for the first time. Here's a little background, examples of the things you might work on, and things you probably want to know. Background & reason for hiring There are two major gaps in our team that are driving this hiring decision: The first is a gap in ownership between marketing & sales around call bookings. For context, we have a hybrid go-to-market that includes both self-serve free trials, and sales-led demo calls. Marketing is responsible for all pipeline generation (both trial & call booking KPIs), but there isn’t one clear person responsible (in either marketing or sales) for various things on the call bookings side. Things like: - How do we qualify demo requests? Who should our sales team spend their time with? - What happens when we decline a demo request? Is the user experience as good as it should be? - Improving the percentage of ICP trial sign ups who book with sales (since sales-closed deals are more likely to close, adopt, and retain long-term). The second gap relates to outbound. We’ve grown to 8-figure ARR solely with inbound marketing, but now it’s time to introduce outbound. I've already taken the first steps to get off the ground, but this needs dedicated ownership to make it world-class. I believe these two things can be handled together by the right person! Scope of the role & example projects The background above covers the broad scope pretty well, but here I'll elaborate a little more on what these initial projects might look like for you. Example 1: Taking ownership of call qualificiation We use a custom internal AI tool (lovingly referred to as “Leadgate”) that sits in front of our demo booking flow. Your job will be to own this end-to-end. You’ll need to collaborate with leadership to iterate on how we qualify calls, and what kind of prospects make the most sense to spend human sales time with. You’ll also own our demo booking page. The copy, the design, the form fields, everything. That means you can test & iterate on what expectations we set, what information we gather, and how that is used to route demos. Example 2: Building the “rejection experience” We want to focus our human sales time on ICPs, which means declining some demo requests (as above). However, “non-ICP” doesn’t mean “gets zero value from Modash”. We want to route those people through self-serve, with the best possible experience. Currently, the experience & flow is simply not good enough — because, once again, nobody owns it. You could create resources, implement demos with AI agents, write better copy, imagine new flows, and more. The goal is to improve brand perception, and increase self-serve revenue from non-ICP segments. Example 3: Taking ownership of the cold outbound program Our outbound cold email program is being run by an external agency, managed by me. Initially, it will be your job to replace me as their point of contact. That includes, for example: - Approving outreach lists - Approving / writing email copy - Strategizing new ideas (e.g. what happens when folks respond negatively) - Ensuring everything runs smoothly & quickly with positive replies Further into the future, you will decide how things run. You can double-down and scale with external agencies, you can build in-house, or a mix. Example 4: Reaching out to ICPs who start trials, but don’t book calls Approximately 10% of trial sign ups that we identify as ICP speak to the sales team. We believe that there’d be significant business impact if we can increase that. Currently, absolutely nothing is being done here. It’s a blank slate for you to come in and figure it out. Team structure To clarify again, this role is in the marketing team. You will report to me (Ryan), your primary KPIs will be around API call bookings, and you’ll collaborate often with the sales team. A few more things that may be useful to know about the team: - Our early-stage outbound project is currently ran by an external agency - We have a full-time software engineer in the marketing team (e.g. for iterations on Leadgate) - You will always write copy yourself; no assistance from a copywriting resource - We have a Product Marketer who will provide product messaging guidance where needed - Our CRM is managed by Steven Perroto (sales team); you will likely collaborate closely

Hi! I'm Ryan, the Head of Marketing at Modash. I'm looking for a GTM Engineer to join our marketing team for the first time. Here's a little background, examples of the things you might work on, and things you probably want to know. Background & reason for hiring There are two major gaps in our team that are driving this hiring decision: The first is a gap in ownership between marketing & sales around call bookings. For context, we have a hybrid go-to-market that includes both self-serve free trials, and sales-led demo calls. Marketing is responsible for all pipeline generation (both trial & call booking KPIs), but there isn’t one clear person responsible (in either marketing or sales) for various things on the call bookings side. Things like: - How do we qualify demo requests? Who should our sales team spend their time with? - What happens when we decline a demo request? Is the user experience as good as it should be? - Improving the percentage of ICP trial sign ups who book with sales (since sales-closed deals are more likely to close, adopt, and retain long-term). The second gap relates to outbound. We’ve grown to 8-figure ARR solely with inbound marketing, but now it’s time to introduce outbound. I've already taken the first steps to get off the ground, but this needs dedicated ownership to make it world-class. I believe these two things can be handled together by the right person! Scope of the role & example projects The background above covers the broad scope pretty well, but here I'll elaborate a little more on what these initial projects might look like for you. Example 1: Taking ownership of call qualificiation We use a custom internal AI tool (lovingly referred to as “Leadgate”) that sits in front of our demo booking flow. Your job will be to own this end-to-end. You’ll need to collaborate with leadership to iterate on how we qualify calls, and what kind of prospects make the most sense to spend human sales time with. You’ll also own our demo booking page. The copy, the design, the form fields, everything. That means you can test & iterate on what expectations we set, what information we gather, and how that is used to route demos. Example 2: Building the “rejection experience” We want to focus our human sales time on ICPs, which means declining some demo requests (as above). However, “non-ICP” doesn’t mean “gets zero value from Modash”. We want to route those people through self-serve, with the best possible experience. Currently, the experience & flow is simply not good enough — because, once again, nobody owns it. You could create resources, implement demos with AI agents, write better copy, imagine new flows, and more. The goal is to improve brand perception, and increase self-serve revenue from non-ICP segments. Example 3: Taking ownership of the cold outbound program Our outbound cold email program is being run by an external agency, managed by me. Initially, it will be your job to replace me as their point of contact. That includes, for example: - Approving outreach lists - Approving / writing email copy - Strategizing new ideas (e.g. what happens when folks respond negatively) - Ensuring everything runs smoothly & quickly with positive replies Further into the future, you will decide how things run. You can double-down and scale with external agencies, you can build in-house, or a mix. Example 4: Reaching out to ICPs who start trials, but don’t book calls Approximately 10% of trial sign ups that we identify as ICP speak to the sales team. We believe that there’d be significant business impact if we can increase that. Currently, absolutely nothing is being done here. It’s a blank slate for you to come in and figure it out. Team structure To clarify again, this role is in the marketing team. You will report to me (Ryan), your primary KPIs will be around API call bookings, and you’ll collaborate often with the sales team. A few more things that may be useful to know about the team: - Our early-stage outbound project is currently ran by an external agency - We have a full-time software engineer in the marketing team (e.g. for iterations on Leadgate) - You will always write copy yourself; no assistance from a copywriting resource - We have a Product Marketer who will provide product messaging guidance where needed - Our CRM is managed by Steven Perroto (sales team); you will likely collaborate closely