Head of Data Apps Engineering
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. The posting includes: - Intro about Attain (maybe not needed as heading? It's not a section heading; we can put as
maybe under About the role? Actually "About the role" heading is present. The text after "About the role" includes description of role. So we can put that under
About the role
with paragraphs. - Then "Attain Office Hybrid Schedule (where applicable): ..." This is schedule info. So we can have a Schedule section. - Then "You'll be a great fit for the role if ..." That's requirements/qualifications. Could be Requirements or Qualifications. We'll need to decide. The bullet list after that is a set of criteria. Could be Requirements. Then later "Preferred Qualifications" list. So we have both Requirements and Preferred Qualifications. The instructions: use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Requirements and Qualifications sections. We could treat the "You'll be a great fit..." as Requirements, and the "Preferred Qualifications" as Qualifications. Or we could combine. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can have both. - Then "What a typical week will look like" - that could be Responsibilities. So we can put that under Responsibilities. - Then "Preferred Qualifications" heading already present; we can use Qualifications. - There's no explicit Benefits, Pay sections. The posting does not mention benefits, pay, etc. So we should not include those sections. - Also there is no Skills section explicitly; but we could infer skills from requirements. However instruction: do not create sections unless posting actually states them. So we should not add Skills if not explicitly stated. The posting does not have a "Skills" heading. So we skip. - Also we need to include meta info like Job ID? Not present. So ignore. - Remove boilerplate: The final paragraph "We're excited to hear from you..." is boilerplate/application instructions; we should remove it. - Also remove duplicated lines etc. Thus we will produce:About the role
... (the paragraph after About the role up until schedule? Actually the schedule is separate. We'll need to split.) Let's extract the About the role section text: "About the role Attain's consumer mobile apps are the front door of our data ecosystem: they deliver real value to consumers, and the permissioned data they generate powers everything our enterprise platform does. Each app has a different audience with its own acquisition and monetization approach, all running on a shared backend platform. As Head of Data Apps Engineering, you'll own the engineering side of that portfolio and be the consumer voice in with our ad-tech leadership team. This is a player-coach role by design: you'll lead a deliberately small team of mobile and backend engineers, write and review code yourself, and set the technical direction that lets us ship new apps at a marginal cost that shrinks with each launch. You'll work in lockstep with our Head of Product for the portfolio. And you'll represent the data apps business at the executive level, where your consumer expertise fills a gap the rest of the room knows it has. This role reports into the SVP of Engineering." We can put that as
...
. Then schedule: "Attain Office Hybrid Schedule (where applicable): Redwood City, CA: Mondays (in-office for stand-ups, all-hands) and choice of three days between Tues-Friday Chicago, IL: 4 days in office" We can put underSchedule
with...
. Then Requirements: The "You'll be a great fit for the role if" bullet list (actually sentences separated by line breaks). We'll convert each line to- . The text:
"You've built and scaled a consumer app with real ownership (as a founder, CTO, founding engineer, or the technical lead who was accountable for the outcome), and you can speak to what worked and what didn't from firsthand experience
You've held senior scope before and are excited to lead your team through hands-on building: you want a small, focused team and a big mandate, not a big org
You instinctively seek to collaborate with your Product counterpart to ship great products
You're a backend-heavy full-stack engineer who is genuinely fluent across the stack, including React Native, and you still love being in the weeds
You think like a product engineer: you'd rather pressure-test an idea with your product counterpart before a line of code is written than build the wrong thing beautifully
You're credible in an executive room: you can represent a business line to a leadership team, translate consumer strategy for an ad-tech-native audience, and hold your ground on what it takes to build for consumers
You read retention and engagement data across a portfolio of products fluently, and you use it to prioritize with your Product counterpart; you don't wait to be handed a metrics brief before you know which app or feature needs attention
You get energy from leverage: shared platforms, reusable components, and AI-assisted development that let a five-person team ship like a fifteen-person one
You've experienced consumer scale (real production load, real users, real growth curves) and know which scaling problems to solve now versus earn later"
We'll put under
- ...
- ...
- ...
- You've built and scaled a consumer app with real ownership (as a founder, CTO, founding engineer, or the technical lead who was accountable for the outcome), and you can speak to what worked and what didn't from firsthand experience
- You've held senior scope before and are excited to lead your team through hands-on building: you want a small, focused team and a big mandate, not a big org
- You instinctively seek to collaborate with your Product counterpart to ship great products
- You're a backend-heavy full-stack engineer who is genuinely fluent across the stack, including React Native, and you still love being in the weeds
- You think like a product engineer: you'd rather pressure-test an idea with your product counterpart before a line of code is written than build the wrong thing beautifully
- You're credible in an executive room: you can represent a business line to a leadership team, translate consumer strategy for an ad-tech-native audience, and hold your ground on what it takes to build for consumers
- You read retention and engagement data across a portfolio of products fluently, and you use it to prioritize with your Product counterpart; you don't wait to be handed a metrics brief before you know which app or feature needs attention
- You get energy from leverage: shared platforms, reusable components, and AI-assisted development that let a five-person team ship like a fifteen-person one
- You've experienced consumer scale (real production load, real users, real growth curves) and know which scaling problems to solve now versus earn later
- Lead architecture and hands-on development across the app portfolio: React Native front ends on a shared, multi-app backend platform
- Partner daily with the portfolio's product lead on roadmap, feasibility, and sequencing: you are the engineering half of that partnership
- Track retention and usage across every app in the portfolio and use it to decide what gets engineering attention next
- Drive the "factory" economics: harden the shared components (onboarding, account linking, loyalty, receipt OCR) so each new app is a configuration and a skin, not a rebuild
- Manage a small team of mobile and backend engineers: line management, code review, and career development, not layers of management
- Represent data apps at executive and planning forums: portfolio status, investment cases, and the consumer perspective on company-level decisions
- Raise the bar on modern engineering leverage: agentic/AI-assisted development is how this team punches above its size
- 10+ years of software engineering experience, with several years building consumer-facing mobile products
- Founder, CTO, VP Engineering, or founding-engineer experience at a consumer startup, or equivalent demonstrated ownership of a consumer product's technical outcomes
- Track record taking a consumer app from zero to meaningful scale (
Requirements
withResponsibilities
withQualifications
withAbout the role
Attain's consumer mobile apps are the front door of our data ecosystem: they deliver real value to consumers, and the permissioned data they generate powers everything our enterprise platform does. Each app has a different audience with its own acquisition and monetization approach, all running on a shared backend platform. As Head of Data Apps Engineering, you'll own the engineering side of that portfolio and be the consumer voice in with our ad-tech leadership team. This is a player-coach role by design: you'll lead a deliberately small team of mobile and backend engineers, write and review code yourself, and set the technical direction that lets us ship new apps at a marginal cost that shrinks with each launch. You'll work in lockstep with our Head of Product for the portfolio. And you'll represent the data apps business at the executive level, where your consumer expertise fills a gap the rest of the room knows it has. This role reports into the SVP of Engineering.
Schedule
Attain Office Hybrid Schedule (where applicable): Redwood City, CA: Mondays (in-office for stand-ups, all-hands) and choice of three days between Tues-Friday; Chicago, IL: 4 days in office.