No experience modeling jobs in New York, NY - Page 4Create job alerts

Job DescriptionA Better Built World At Miter, we’re on a mission to help construction contractors build with confidence. If we’re successful, we’ll make it easier and faster to build critical physical infrastructure - roads, bridges, utilities, data centers, housing, etc. For decades, construction and field services contractors have had to run their businesses on outdated software: clunky, on-premise systems created in the 1980s and 1990s. That’s where Miter comes in. We’re using AI and embedded payments to rebuild the core HR, finance, and operations systems that underpin our physical economy. Using Miter, contractors like Marathon Electrical, W.J. O’Neil, and Truebeck Construction are building stronger teams, controlling job costs, and accelerating jobsite execution. This idea is resonating. Since we launched in 2022, we’ve grown to thousands of customers and tens of millions in ARR, making us one of the fastest growing vertical software companies ever. To double-down on our momentum, we’ve raised $50M+ from top investors (Bessemer, Coatue, and Battery) who share our belief that we’re just getting started. Hybrid Strategy: We believe the magic of Miter comes from working side by side. Our hybrid approach—four days a week in the office—gives us the chance to connect, brainstorm, and build stronger relationships. One flexible day each week lets us recharge and focus, keeping us energized for the work that matters most. About the Team and How We Work: Building the OS for the built world is no small feat. We’ll need to ship a LOT of high quality code in the coming years, and to do so, we’re building an engineering culture centered around craft, ownership, and collaboration. >25% of our engineers and product managers are ex-founders, and we hire for slope, not intercept. Being a place where you can just build things requires talent density and some unique ways of doing things. A few ways we’re different: * No rules…rules: Many engineering teams design processes and rules around the lowest common denominator. Not us! We trust brilliant engineers to deliver magical customer outcomes and introduce processes and rules only when necessary. * Full-full-stack: Our technology stack (TypeScript everywhere!) and processes are designed to encourage engineers to run their projects end-to-end. This usually involves writing technical blueprints, implementing full-stack solutions, and talking to customers directly to get feedback. * Lean and AI-native: AI is turning 10x engineers into 100x engineers. We believe lean, talent-dense, AI-native teams will outship much larger teams with less talent density. * Blueprints and building blocks: One of our core Miter values is “build the blueprint”. Writing things down clarifies our thinking and aligns our teams. This also applies to building fundamental building blocks and abstractions that make developers’ lives easier. * We feel our customers’ pain and celebrate their success: We encourage engineers to build direct relationships with customers, feel their pain, and celebrate their success. We love fast feedback loops. * We’re meritocratic: We value results and hard work. We reward engineers who consistently ship and deliver for customers with increased scope and compensation. What You'll Do: * Lead the design and implementation of products and systems end-to-end. * Collaborate with cross-functional teams to shape product architecture and technical roadmap. * Improve technical quality on the team by giving detailed technical feedback on blueprints and in code review. What You'll Need: * 4+ years of software engineering experience with a track record of delivering production systems. * Expertise in technical problem solving, data modeling and API development. * Curiosity to deeply understand business context and user needs. * Strong work ethic and reliability when owning tasks and deliverables. * Strong communication skills, with the ability to simplify complex ideas in writing. * Collaborative nature with humility, empathy, and a drive to elevate those around you with thoughtful technical feedback. Our Tech Stack: * React + React Native * Node/Express * MongoDB * Render * Check * Stripe (Issuing, Treasury) * Typescript Our Interview Process: * Recruiter and/or Hiring Manager Intro * A technical screen where we pair on a real-life problem * A (virtual) onsite! * Practical coding exercise * Systems design exercise * Miter values with CEO * Product collaboration with PM Our Benefits: * Competitive Compensation: We offer competitive (well above “market”) salary, commission, and equity packages. * Medical Insurance: Comprehensive medical, dental, FSA, vision plans to suit you and your family’s needs. * 401(k) Retirement Plan: Company-matched contributions to help you plan for your future. * Unlimited PTO: Take the time you need to recharge and be your best self. * Parental Leave: Generous 16-week paid leave for all parents, including adoptive and foster parents. * Learning & Development: We offer every employee an annual educational allowance to explore external professional development. * Office Extras: Snacks, coffee, lunch, and commuter benefits for in-office Mitosaurs. * Community: Multiple company-wide and team-specific offsites per year. Equal Opportunity: Miter provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities. Compensation Range: $190K - $230K

Job Description Hi 👋🏾 I’m Abhik, Ashby's Co-Founder and VP of Engineering. As someone who could design and build software, this position is close to my heart. I always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique (thanks, React component system!). But, every company made me pick one —I couldn’t design and build. At Ashby, you can. While every engineer can design and build, you’ll tackle our most challenging design problems and help others improve their designs by expanding and enhancing our in-house design system and consulting on bespoke work. To ground it with examples, engineers who can design at Ashby have: * Redesigned our mobile web app by talking with customers who use it often, wireframing new flows, implementing its design system, and using it to make the wireframes a reality. * Built a set of flexible, composable components in our design system that allow other engineers to build custom autocompletes. These autocompletes can contain filters, options to create new records, etc. * Helped another engineer improve their design's information hierarchy and scannability for viewing a candidate’s assessments. Recruiters can quickly parse information and pick out anomalies. These projects reflect what we’re accomplishing at Ashby: improving the productivity of working professionals (starting with talent teams) with intelligent and powerful software. We put a lot of effort into designing products that are approachable to beginners but mastered & extended by power users. In many ways, spreadsheets set the bar here. We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, over 2500 customers, very low churn, and many years of runway. We’ll share more details once we meet, but you now probably have a good idea as to why we're hiring for this role 😅. What We’re Building As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back. Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help. As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are! Engineering Culture Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through: * Minimal process with ownership over decisions normally made by product and design * Natural collaboration and deliberate communication * Investing in tools and abstractions that give us leverage * Putting effort into building a diverse team Minimal Process & Lots of Ownership The best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise. Traditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive. Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here). To drive it home, here's a recent calendar of an engineer who has been with us for over 4 years: We also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region. Increase Leverage, not Team Size We built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in: * Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾. * Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below). Here’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby: And a demo of one of these building blocks: Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups. Today, 21% of engineers at Ashby are from underrepresented groups. It’s not great, and we are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more. Interview Process At Ashby, our team and interview process want to help you show your best self. We’ll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises. Our interview process is three rounds: * Introduction call with Hiring Manager (15 to 30m, live) * A technical screen where we pair in our actual codebase (1h, live) * Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days) Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter. Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback! Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together. It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture. Technology Stack I’m sharing our tech stack with the caveat that we don’t require previous experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis. When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Sergey). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile 😅. Benefits * Competitive salary and equity. * 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable. * Unlimited PTO, and we will encourage you to take it. * A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements. * Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! * $100/month education budget with more expensive items (like conferences) covered with manager approval. * If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us. Ashby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities. Compensation Range: $170K - $260K

Job Description:\n\nHi 👋🏾 I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for a versatile, persistent product engineer who’s not afraid to set up reusable building blocks across the stack and advocate for the time and space to do so. At Ashby, all our engineers ship features end-to-end at a high pace. Example is the best leadership. We’ll give you the room to do your best work, and you'll be our guide! If that speaks to you, read on. What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature. We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet. You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner). About the Role and How We Work Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software. I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings. I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation. Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey. At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have: Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building." Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it. Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features. What We’re Building As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back. Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help. As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are! Why You Should or Shouldn’t Apply Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for: You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team). You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems. You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team. You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it). You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here! You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc. Put another way, you shouldn’t apply if: To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off. You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges. You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs. You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront. You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them. You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited. Engineering Culture Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through: Minimal process with ownership over decisions normally made by product and design Natural collaboration and deliberate communication Investing in tools and abstractions that give us leverage Putting effort into building a diverse team Minimal Process & Lots of Ownership The best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise. Traditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive. Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here). To drive it home, here's a recent calendar of an engineer who has been with us for over 4 years: We also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region. Increase Leverage, not Team Size We built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in: Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾. Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below). Here’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby: And a demo of one of these building blocks: Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups. Today, 21% of engineers at Ashby are from underrepresented groups. It’s not great, and we are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more. Interview Process At Ashby, our team and interview process want to help you show your best self. We’ll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises. Our interview process is three rounds: Introduction call with Hiring Manager (15 to 30m, live) A technical screen where we pair in our actual codebase (1h, live) Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days) Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter. Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback! Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices.

Job DescriptionDescription: Senior Program Manager, Primary Care Consulting & Cardiovascular Health Improvement Lead Preferably New York Tri-state Primary Care Development Corporation (PCDC): Catalyzing Excellence in Primary Care Quality primary care is transformative and a cornerstone of healthy, thriving communities. PCDC, a nationally recognized 501(c)(3) community development financial institution (CDFI), provides capital financing, expertise, and advocacy to expand primary care access and advance health equity in communities that need it most. We offer capital financing products (loans, tax credits, etc.) and consulting services to health care providers to enable them to expand their reach, impact, and sustainability. Our two primary business lines focus on Federally Qualified Health Centers (FQHCs), independent health care practices, behavioral health providers, and hospitals and health systems. Built on its 30 years of experience, PCDC is a statewide convener and primary care expert that brings safety net providers together to develop the care models and business practices necessary to remain longstanding, viable businesses with measurable impact. In addition, we continue to support providers to succeed in various State and Federal-led transformation initiatives (e.g., AHEAD, the NY 1115 Medicaid Waiver, Patient-Centered Medical Home, etc.). To build on this momentum, we’re seeking a results-driven, well-established Senior Program Manager to drive improvement in practices’ quality, operations, and financial viability. This position will primarily support a NYC cardiovascular health improvement initiative - bringing together diverse stakeholders to drive improvement at a collective and practice level. Position is contingent upon continued funding for this three-year initiative. For consideration, send a thoughtful cover letter and resume by August 20, 2025. Work environment: Hybrid with business travel (10-15%) Staff should be based in the greater New York City metro area. Travel to the PCDC office will be 1-2 days/ week , remote the rest of the week with business travel to target market regions including upstate New York and industry conferences throughout the year as required.. Annual Salary Range: $110,000 to $125,000 depending on experience. Position Description: The Senior Program Manager / Cardiovascular Improvement Lead, reporting to Director of the NY Consulting Portfolio[LC1] ,[LC2] [IK3] works directly with primary care, behavioral health, and other healthcare delivery settings to improve their operations, quality, and financial viability. The position will work with practices to 1) scope consulting engagements with measurable improvements as the end point and 2) deliver direct coaching and training that achieves those improvements. In addition, the Senior Program Manager will be responsible for managing large, complex projects, bringing together organizations in learning collaboratives and other convening structures, and managing reporting to funders. The candidate should have experience with both the clinical operations and financial management (i.e., revenue cycle management, budgeting, financial planning, and analysis) of primary care and/or outpatient settings. Position Responsibilities (other duties may be assigned): 1. Direct Consultation and Client Services (85%) a. Drive NYC-wide, collaborative cardiovascular improvement initiative, bringing together health systems, FQHCs, city government, payers, CBOs, and other critical stakeholders to drive changes in health outcomes. Maintain accurate reporting to demonstrate impact. b. Plan and implement financial operations and clinical capacity building and improvement programs with independent practices, FQHCs, community-based behavioral health providers, health systems, departments of health, and health plans. Guide the collection of clinical, administrative, and financial data to inform client continuous quality improvement initiatives and PCDC evaluation activities. c. Develop and deliver virtual and in-person training, consultations, coaching and other modalities of capacity building. d. Facilitate, support and/or lead work through all components of project life cycle from initial scoping to close-out which may include assessment, workflow redesign, team building, evaluation, and other key pillars of project management and implementation. e. Manage resources to ensure goals are achieved on-time, on budget and within defined scope. f. Work with diverse teams – within PCDC, with the client and at health care organizations – to develop and execute improvement and implementation projects. g. Ensure positive client experience, mitigate risks, and inform potential scope and service revisions, including regular check-in with clients. h. Maintain current knowledge of trends and best practices in quality improvement, program development, integration of public health, SDoH, community health, home care, oral health, vision care, behavioral, sexual, and reproductive health, HIV prevention and care, and other related subjects. 2. Business Development & Portfolio Growth (15%) a. Participate in building the visibility and capacity of PCDC’s training and technical assistance efforts through partnership development and conference attendance and presentations. b. Increase PCDC’s reach, thought leadership (speaking engagements, presentations, committee participation, etc.), and relationship development to drive consulting engagements. c. Secure contracted engagements and revenue (mixture of grants, fee-for-service engagements, etc.); contribute to the achievement of departmental revenue goals. d. Monitor New York and industry trends (including evidence base, reimbursement reform, and delivery system transformation) and develop strategies that position PCDC as a key partner in supporting the safety net. e. Develop engagement scopes and foundation proposals, budgets, and contracts. Requirements: · Demonstrated subject matter expertise in current and emerging primary care delivery models, outpatient financial management/operations, practice transformation concepts, and community health: o Budgeting and financial modeling o Value-based Payment Models o Revenue Maximization/Billing Cycle Optimization o Quality Improvement and Performance Improvement Methodologies o Care Management • Demonstrated experience in project management, leading project teams through highly intensive, long-term, large-scale project work., • At least five years familiarity with New York and federal healthcare policy and program landscape including familiarity with the healthcare policy environment and payment reform initiatives., • Established relationships with healthcare policy, payer, and provider stakeholders across New York; demonstrated experience growing an organization’s presence and recognition with key stakeholders and decision makers across NY’s healthcare environment., • Demonstrated success writing proposals for fee-driven work, government procurement and grants, foundation support, or other revenue sources., • Able to work across a broad portfolio of transformation efforts. Works effectively both as a team member and on individual effort and timelines., • Effective communication skills, including the ability to create presentations, speak publicly, work with a wide array of client staff from executives to front-line staff., • Skilled in the use of software required to perform job duties, including Microsoft Office 365, Teams, and other software solutions, • Ability to travel throughout NY and CT. (up to 20%travel).