Software Engineering Manager - Mobile

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About DAT (company description), About The Team, About You, The Skills And Experience You’ll Bring, Why DAT? (benefits), and salary range for Colorado. Also there is Job Application Deadline (metadata) which we can fold into a short

or drop. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to appropriate headings. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. But we need to include a section only when posting has real, specific content for it. So we need to decide which sections apply. We have content: About DAT (company overview) - could be "About the role"? Actually "About the role" is generic heading for role description. But we have "About The Team", "About You", "The Skills And Experience You’ll Bring", "Why DAT?" (benefits). Also we have Pay (salary range). No explicit responsibilities list but we have bullet-like sentences under About You describing duties. Could treat as Responsibilities. Requirements could be skills/experience. Qualifications could be education. Skills could be technical stack. Benefits from Why DAT?. We must not invent sections with placeholder text. So we need to include sections only if we have substantive content. Let's map: - About the role: Could combine About DAT and About The Team? But maybe better to have "About the role" as a brief description of the role (Mobile Engineering Manager). The posting includes "About You" which describes role responsibilities. Could use "About the role" heading for that. However we also have "About The Team" which is separate. Could we make a section "About the team"? Not in allowed headings list but we could still use

for any heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. Thus we need to map content to those headings. We have: - About the role: maybe a brief summary: "Mobile Engineering Manager leading carrier mobile engineering team, building mobile platform, technical leadership, people management, operational excellence, partnership with product, UX, data scientists." That's from About You. - Responsibilities: list of duties: Deliver Customer Value at Speed, Ensure Operational Reliability, Act with Integrity and Ownership, Build and Mentor a World-Class Team, Collaboration. Those are bullet points under About You. So we can put those as

• . - Requirements: maybe the skills/experience needed: 8+ years combined experience, at least 3 years as technical people manager, experience managing a mobile team, experience working with geo distributed teams, proven ability to mentor and lead technical projects with high ambiguity, Bachelor's degree in CS or related or equivalent practical experience. Also technical stack: Typescript, React Native, Here and Google Maps, Widgets, OS integrations. Could be under Skills. - Qualifications: maybe education: Bachelor's degree in Computer Science, a related technical field, or equivalent practical experience. Could be separate. - Skills: technical stack and maybe soft skills: Technical craft, engineering excellence, intellectual curiosity, continuous learning, strong team collaboration, camaraderie, individual autonomy, ownership. Those are from culture values. Could be under Skills. - Benefits: from Why DAT?: hybrid work environment, medical/dental/vision/life/AD&D insurance, parental leave, flexible vacation time, additional 10 holidays, 401k matching (immediately vested), employee stock purchase plan, short- and long-term disability sick leave, flexible spending accounts, health savings accounts, employee assistance program, additional programs (employee referral, internal recognition, wellness), free TriMet transit pass (Beaverton Office), competitive salary and benefits package, work on impactful projects, collaborative supportive team culture, opportunity to make a real difference, employee resource groups. - Pay: salary range for Colorado-based candidates: $192,000.00 - $274,000.00 + target bonus. Also note factors considered. - Schedule: not mentioned. So we should not include Schedule section. We also have Job Application Deadline: 10/31/2026. Could fold into a short

  maybe under a generic metadata paragraph at top. But instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a

  with the deadline. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove duplicated lines, navigation, cookie, legal. So we need to strip out the EEO paragraphs at end. Also remove "For Colorado-based candidates, in compliance with the Colorado Equal Pay for Equal Work Act, the salary range for this role is $192,000.00 - $274,000.00 + target bonus." That's pay info, we keep. We must not repeat job title as heading. We must output only HTML fragment, no /, no markdown fences. Let's construct:

  Job Application Deadline: 10/31/2026

  Then sections:

  About the role

  As a Mobile Engineering Manager, you will be a technical leader building the mobile platform that powers our economy. You will combine your technical leadership with mission-driven impact. You will lead the application development process focusing on technical strategy, people management, and operational excellence; along with a strong partnership with Product Management, User Experience and Data Scientists.

  Responsibilities

  • Deliver Customer Value at Speed: Orchestrate the end-to-end delivery of high-impact features. You will collaborate with Product Managers and Designers to translate complex logistics workflows into intuitive, seamless user experiences.
  • Ensure Operational Reliability: Freight never stops, and neither do we. You will champion operational best practices, including rigorous code reviews, automated testing, and CI/CD pipelines, to maintain high availability and performance for our mission-critical services.
  • Act with Integrity and Ownership: Serve as a technical stakeholder who isn't afraid to dive into the code when needed to unblock the team or resolve high-severity production issues.
  • Build and Mentor a World-Class Team: Cultivate an inclusive and high performing culture by hiring, coaching, and retaining top engineering talent. You will foster an environment where engineers are empowered to innovate and grow their careers.
  • Collaboration: Work closely with cross-functional teams, including product managers, DevOps, user experience and data scientists.

  Requirements

  • 8+ years of combined experience in Software Engineering.
  • At least 3 years as a technical people manager.
  • Experience managing a mobile team.
  • Experience working with geo‑distributed teams.
  • Proven ability to mentor and lead technical projects with high ambiguity.
  • Bachelor's degree in Computer Science, a related technical field, or equivalent practical experience.

  Skills

  • Technical stack: TypeScript, React Native, Here and Google Maps, Widgets, OS integrations.
  • Technical craft and engineering excellence.
  • Intellectual curiosity and continuous learning.
  • Strong team collaboration and camaraderie.
  • Individual autonomy and ownership.

  Benefits

  • Hybrid work environment.
  • Medical, Dental, Vision, Life, and AD&D insurance.
  • Parental Leave.
  • Flexible Vacation Time (FVT).
  • Additional 10 holidays of paid time off per calendar year.
  • 401k matching (immediately vested).
  • Employee Stock Purchase Plan.
  • Short- and Long‑term disability sick leave.
  • Flexible Spending Accounts.
  • Health Savings Accounts.
  • Employee Assistance Program.
  • Additional programs – Employee Referral, Internal Recognition, and Wellness.
  • Free TriMet transit pass (Beaverton Office).
  • Competitive salary and benefits package.
  • Work on impactful projects in a cutting‑edge environment.
  • Collaborative and supportive team culture.
  • Opportunity to make a real difference in the trucking industry.
  • Employee Resource Groups.

  Pay

  For Colorado‑based candidates, the salary range is $192,000.00 – $274,000.00 + target bonus. DAT considers factors such as scope and responsibilities of the position, candidate's work experience, education and training, core skills, internal equity, and market and business elements when extending an offer.

  We should not include Schedule section. Check for any leftover boilerplate: We removed EEO paragraphs. Also removed "This position is not eligible for visa sponsorship**" maybe we could keep as minor metadata? It's a note about visa sponsorship. Could fold into a short

  maybe after Pay? But it's minor metadata; we could include a short

  after Pay: "

  This position is not eligible for visa sponsorship.

  " However instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." This is minor metadata, so we can include a short

  . Let's add after Pay. Also we have "About DAT" company description at start. We haven't used that. Could incorporate into About the role? Or maybe we could have a separate section "About the company"? Not in allowed headings. Could fold into About the role paragraph? Might be okay to include a brief company overview in About the role. But we already have About the role paragraph focusing on role. Could add a sentence about DAT being a leading SaaS freight marketplace etc. However we must preserve ALL substantive information; we cannot omit company description. So we need to include that somewhere. Where? Could add a preceding

  before About the role: maybe a short paragraph about DAT. Or we could incorporate into About the role as a preamble. Let's add a

  before About the role: "DAT Freight & Analytics is an award‑winning employer of choice and a next‑generation SaaS technology company that has been at the leading edge of freight and logistics innovation for nearly five decades. Founded in 1978, DAT operates the largest freight marketplace in North America — processing 250 million+ load posts annually and maintaining one of the largest repositories of freight market transaction data in the world. On a defined path to $1 billion in revenue, DAT deploys a suite of software solutions, machine learning models, and intelligent automation tools that help brokers, carriers, and shippers price freight accurately, source capacity, reduce risk, and operate more efficiently. With nearly 700 teammates across offices in Denver, CO; Portland, OR; Seattle, WA; Springfield, MO; Toronto, ON; and Bangalore, India, DAT combines the credibility of a multi‑decade market leader with the drive of a company that is not done disrupting the industry it helped build." That's substantive. Then About the role paragraph can focus on role specifics. We must not repeat job title as heading; we are not. Now ensure we didn't