Sentry jobs in Jersey City, NJCreate job alerts

Job Description:\n\nWe’re looking for a curious, rigorous, problem-hungry platform engineer (who codes!) to carry the ball as we bring Ashby to the big leagues. Ashby builds software that lets talent teams build an efficient, delightful, respectful hiring process. Similarly, you’re an engineer who wants to build a “paved road” that excellent engineering teams can safely take to the moon and back. 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 😅. We’ve listed this role twice: as a Platform Engineer and Site Reliability Engineer – our team does both, and we are open to candidates who lean towards one or the other. About the role and how we work Hi 👋 I’m Colin, Head of EMEA Engineering. I’ve spent a number of years leading engineering teams in startups, and that has always included being close to infrastructure teams - no matter what name they’ve worn (SRE, infrastructure, platform, etc). I’ve got my hands dirty building the initial infrastructure for startups and know the value a talented infrastructure engineer brings. The rigour, the discipline, the peace and quiet when everything just hums along. Our infrastructure is in a good place for now. Nothing is static. Ashby continues to grow rapidly, putting strain on our existing infrastructure. We’re always looking to give our customers more powerful hiring software, and building new product features often requires new pieces of infrastructure. Having herded plenty of snowflakeservers in the past, I’ve learned there’s a better way. I (and Ashby) place a lot of value on code-as-infrastructure. As a Platform Engineer at Ashby, you’ll get to dive into scaling problems, add new capabilities to our platform, and think about how our entire team interacts with infrastructure. All our own engineers own their projects end-to-end and ship with minimal oversight. We don’t put roadblocks to ensure security when common sense will do and we don’t build processes like change management boards around the lowest common denominator. But with great power comes great responsibility: we handle personal and confidential data about some of the biggest decisions we ever make at work. As we grow, more and bigger customers rely on us to be reliable and secure and how we operate internally will need to evolve. We’re at an inflection point where our ability to scale and deliver a seamless experience has a make-or-break impact – we have some of the fastest growing companies using our platform every day to hire hundreds of people per month. We need someone like you to make good decisions, debug thorny issues, and build us a future-proof platform that can withstand this scale. Our small but mighty infrastructure team has set up a secure and simple environment (we don’t believe in spinning up a new service unless necessary!) for our growing product team to build in. That’s where you come in: you, too, will own projects end-to-end and have an impact on core parts of the Ashby developer and user experience. For instance, you could work on: Optimize our homegrown ultra-dynamic recruiting DSL-to-SQL compiler, and create tools to help developers do so Create automated guardrails for the security and privacy of our customer data Help our developers ship features fast through canary deploys, gradual rollouts and feature flags, while keeping complexity manageable and reducing downtime Work with the business and the engineering team to define SLOs and implement the corresponding SLIs. Ensure all communication with external services supports retries and circuit-breakers. Implement the infrastructure to support an event-driven architecture and data warehouse. We’re looking for someone who can build systems that an engineer would like to work with: mature and boring but open-minded and approachable. We have to balance reliability with flexibility. Software and its availability are now mission critical to almost every working professional. To be in an SRE in today’s world, you have to be extremely comfortable evaluating risk, those you take and those others take. Why you should or shouldn’t apply You should apply if: You never stop. You get weirdly obsessed about a problem that doesn’t yet make sense, turn it every which way in your head until the explanation dawns. You’ll search every rock, inventory every clue, hunt every mismatch. We do that, too - together we’ll be armed with state-of-the-art monitoring tools and an impressive amount of data, and join you in the adventure. You don’t take shortcuts. You’re speaking up for the future user, the edge case, the doomsday design. You know product engineers want to build it with you, and see them as allies, where you give them the power and knowledge to access greater things. You’re someone who cares about what you do and the team you do it with, and want to work with others who do as well. You’ll be on interview panels choosing your next colleagues, and you’ll take that seriously. You only want to work with people who make you better, and want to make you better. You’ve built infrastructure at a slightly later stage than Ashby is at - you know how to deal with millions of data points, have seen great (or not great) infrastructure make or break customer experience, and have automated everything from provisioning to monitoring and release process. You’re a Swiss army knife (all nationalities welcome ;) ). You’ll get every hard problem the company faces. You’ll get to do infrastructure updates, security enforcements, database optimization, Kubernetes debugging, and digging through Typescript traces figuring out what doesn’t work. You probably don’t feel like an expert at at least some of that... and that appeals to you. All that makes for a pretty specific kind of role, and the job isn’t to everyone’s tastes! You should not apply if: You don’t want to make your own decisions on what is the best paved road to build for Ashby, and expect a lead or manager to make the final call on what that is. Our leads (and managers) give ample commentary and feedback on technical decisions and how they’re made, but you ship what you want to build and are accountable for it. You hate SQL. We have a lot of features built around making the best out of data, and our platform engineers also sometimes dive into a gnarly report or advise engineers on a more performant data model to use. You don’t want to code. Our SREs are some of our best software engineers and they are just as responsible for the application as the other engineering teams - albeit at a platform level. Reviewing code and submitting code changes will be part of your day to day. Your primary mode of communicating best practices to engineers is live meetings. We’re a very async culture and written communication (and code) is how changes get made. As an Ashby SRE, you will need to share new tooling and best practices with engineers faster than your next meeting opportunity will take you. You’ve never delivered a project, on your own, without someone prodding you for updates. We have no project or delivery managers to fill your calendar with busy work, but the flip side is you have to do your project management, seek the help you need to get unstuck and cut scope when it’s worthwhile. Technology Stack I’m sharing our tech stack with the caveat that we don’t require previous experience in it: TypeScript (frontend & backend), Node.js, React, Apollo GraphQL, Postgres, Redis. We use Datadog and Sentry on 100% cloud-based (AWS) infra. We take developer experience and reliability seriously: all engineers are on call in a follow-the-sun model, and everyone contributes to developer tooling. 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 Abhik and Benji’s (our co-founders) 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 (Abhik 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 technical design, debugging incidents, 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 b

Job DescriptionTechnical skills • Must possess basic knowledge of our platforms and systems: EC2, Elastic Beanstalk, CloudWatch, Docker, ActiveMQ, RDS/Postgres, Firebase and Sentry., • Must possess knowledge of languages including Java, Kotlin and SQL. Optionally React, HTML/CSS and JavaScript, as well, for frontend work., • Knowledge of React Native and Kotlin is desired but not required., • Knowledge of our SaaS providers is desired but not required: GitHub, GitLab, Sentry, Intercom, Airtable, Expo. Domain knowledge • Prior working knowledge of railroad operations., • Prior working knowledge of GIS or location-based data and systems (including Mapbox and ESRI). Experience and education • Bachelor’s degree in computer science or related field is required. Demonstrated equivalent experience and education may be considered in lieu of the degree, subject to approval., • Prior experience designing customer-facing applications., • Must possess prior experience running projects, writing technical documents including scopes of work, software requirements, and estimates.

Job DescriptionDevOps / Site Reliability Engineer (Remote) Location: Remote (US-based) Reports to: CTO, SportsRecruits About SportsRecruits SportsRecruits is the leading sports recruiting network, connecting athletes, clubs, events, and college coaches in the recruiting process. The company’s network and tools are trusted by sports organizations such as the IWLCA, IMLCA, NFHCA, and Junior Volleyball Association. Every year, millions of connections are made on the network, resulting in commitments to the best academic and athletic institutions. SportsRecruits is part of IMG Academy, the world's leading sports education brand. IMG Academy provides a holistic education model that empowers student-athletes to win their future, preparing them for college and for life. IMG Academy provides growth opportunities for all student-athletes through an innovative suite of on-campus and online experiences: • Boarding school and camps, via a state-of-the-art campus in Bradenton, Fla., • Online coaching via IMG Academy+, with a focus on personal development through the lens of sport and performance We’re looking for a DevOps / Site Reliability Engineer to join our team. You will play a key role in ensuring that our systems are efficient, reliable, and scalable, while helping us improve developer productivity and application performance. You’ll collaborate closely with developers, QA, product, and our cloud security engineer to streamline builds and deployments, maintain application infrastructure, and proactively solve issues before they impact our users. Our stack includes: • Laravel + PHP8 backend APIs, • Vue.js (v2 and v3) + Inertia.js + Tailwind frontend, • React Native mobile applications, • Python for internal tools and ML/LLM-based features, • Infrastructure as code managed by Terraform, • AWS ECS Fargate, AWS RDS, AWS ECS, SQS, MediaConvert, and more, • CI/CD & Deployments, • Configure, manage, and improve Bitbucket pipelines for deploying our applications to staging and production., • Improve CI pipeline speed, reliability, and security in collaboration with our Cloud Security Engineer., • Assist developers and QA teams with deployments., • Work with Docker and AWS ECR for container builds and deployment workflows., • Monitoring & Incident Response, • Review and investigate system issues flagged by Sentry, NewRelic, and CloudWatch., • Monitor application performance, identify bottlenecks, and propose solutions., • Respond to production and staging issues, including database latency, unresponsive resources, or failed jobs., • Environment & Infrastructure Management, • Maintain and support non-production environments used by developers and QA., • Maintain and improve AWS infrastructure and Terraform resources., • Perform updates and upgrades to AWS services as needed to ensure reliability and ability to scale., • Collaboration & Continuous Improvement, • Partner with engineers to design systems that are scalable, observable, and resilient., • Work closely with our cloud security engineer to ensure secure configurations in CI/CD, AWS, and containerized workloads., • Contribute ideas and improvements to workflows, automation, and monitoring strategies. About YouMust-Haves:, • 3+ years of experience in DevOps, SRE, or related engineering roles., • Strong experience configuring CI/CD pipelines (Bitbucket Pipelines, GitHub Actions, or similar)., • Experience configuring, debugging and deploying PHP applications, • Hands-on experience with Docker and AWS ECR for container builds and deployments., • Strong experience with AWS services (EC2, RDS, ECS, Lambda, etc.) and Terraform for infrastructure as code., • Familiarity with monitoring and observability tools such as New Relic, Sentry, CloudWatch, or similar., • Strong troubleshooting skills for debugging performance issues in databases, applications, and distributed systems., • Experience with modern software development workflows (agile teams, code reviews, branching strategies)., • Strong scripting and automation skills (Bash, Python, or similar)., • Experience with ECS orchestration., • Familiarity with PHP/Laravel or JavaScript/React/Vue applications., • Previous experience supporting high-traffic SaaS platforms., • Laravel, Vue, or TailwindCSS experience, • Familiarity with containerized deployments (Docker, ECS, etc.), • Experience working with 3rd-party APIs and async job queues (SQS, Redis), • Knowledge of AI tooling, LLM integration, or computer visionWhy Join Us?, • Meaningful Work: Help shape a platform that impacts thousands of student-athletes’ futures., • Modern Stack: Work with Laravel, Vue, React Native, Python, and AWS, backed by great tooling and infrastructure., • Growth-Oriented Culture: We prioritize learning, experimentation, and continuous improvement., • Competitive salary: $100,000 – $145,000 per year, • Remote-first team culture, • Health, dental, and vision coverage, • 401(k) with company match kxmgntuxQ2

Job Description:\n\nWe’re looking for a curious, rigorous, problem-hungry platform engineer (who codes!) to carry the ball as we bring Ashby to the big leagues. Ashby builds software that lets talent teams build an efficient, delightful, respectful hiring process. Similarly, you’re an engineer who wants to build a “paved road” that excellent engineering teams can safely take to the moon and back. 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 😅. We’ve listed this role twice: as a Platform Engineer and Site Reliability Engineer – our team does both, and we are open to candidates who lean towards one or the other. About the role and how we work Hi 👋 I’m Colin, Head of EMEA Engineering. I’ve spent a number of years leading engineering teams in startups, and that has always included being close to infrastructure teams - no matter what name they’ve worn (SRE, infrastructure, platform, etc). I’ve got my hands dirty building the initial infrastructure for startups and know the value a talented infrastructure engineer brings. The rigour, the discipline, the peace and quiet when everything just hums along. Our infrastructure is in a good place for now. Nothing is static. Ashby continues to grow rapidly, putting strain on our existing infrastructure. We’re always looking to give our customers more powerful hiring software, and building new product features often requires new pieces of infrastructure. Having herded plenty of snowflakeservers in the past, I’ve learned there’s a better way. I (and Ashby) place a lot of value on code-as-infrastructure. As a Platform Engineer at Ashby, you’ll get to dive into scaling problems, add new capabilities to our platform, and think about how our entire team interacts with infrastructure. All our own engineers own their projects end-to-end and ship with minimal oversight. We don’t put roadblocks to ensure security when common sense will do and we don’t build processes like change management boards around the lowest common denominator. But with great power comes great responsibility: we handle personal and confidential data about some of the biggest decisions we ever make at work. As we grow, more and bigger customers rely on us to be reliable and secure and how we operate internally will need to evolve. We’re at an inflection point where our ability to scale and deliver a seamless experience has a make-or-break impact – we have some of the fastest growing companies using our platform every day to hire hundreds of people per month. We need someone like you to make good decisions, debug thorny issues, and build us a future-proof platform that can withstand this scale. Our small but mighty infrastructure team has set up a secure and simple environment (we don’t believe in spinning up a new service unless necessary!) for our growing product team to build in. That’s where you come in: you, too, will own projects end-to-end and have an impact on core parts of the Ashby developer and user experience. For instance, you could work on: Optimize our homegrown ultra-dynamic recruiting DSL-to-SQL compiler, and create tools to help developers do so Create automated guardrails for the security and privacy of our customer data Help our developers ship features fast through canary deploys, gradual rollouts and feature flags, while keeping complexity manageable and reducing downtime Work with the business and the engineering team to define SLOs and implement the corresponding SLIs. Ensure all communication with external services supports retries and circuit-breakers. Implement the infrastructure to support an event-driven architecture and data warehouse. We’re looking for someone who can build systems that an engineer would like to work with: mature and boring but open-minded and approachable. We have to balance reliability with flexibility. Software and its availability are now mission critical to almost every working professional. To be in an SRE in today’s world, you have to be extremely comfortable evaluating risk, those you take and those others take. Why you should or shouldn’t apply You should apply if: You never stop. You get weirdly obsessed about a problem that doesn’t yet make sense, turn it every which way in your head until the explanation dawns. You’ll search every rock, inventory every clue, hunt every mismatch. We do that, too - together we’ll be armed with state-of-the-art monitoring tools and an impressive amount of data, and join you in the adventure. You don’t take shortcuts. You’re speaking up for the future user, the edge case, the doomsday design. You know product engineers want to build it with you, and see them as allies, where you give them the power and knowledge to access greater things. You’re someone who cares about what you do and the team you do it with, and want to work with others who do as well. You’ll be on interview panels choosing your next colleagues, and you’ll take that seriously. You only want to work with people who make you better, and want to make you better. You’ve built infrastructure at a slightly later stage than Ashby is at - you know how to deal with millions of data points, have seen great (or not great) infrastructure make or break customer experience, and have automated everything from provisioning to monitoring and release process. You’re a Swiss army knife (all nationalities welcome ;) ). You’ll get every hard problem the company faces. You’ll get to do infrastructure updates, security enforcements, database optimization, Kubernetes debugging, and digging through Typescript traces figuring out what doesn’t work. You probably don’t feel like an expert at at least some of that... and that appeals to you. All that makes for a pretty specific kind of role, and the job isn’t to everyone’s tastes! You should not apply if: You don’t want to make your own decisions on what is the best paved road to build for Ashby, and expect a lead or manager to make the final call on what that is. Our leads (and managers) give ample commentary and feedback on technical decisions and how they’re made, but you ship what you want to build and are accountable for it. You hate SQL. We have a lot of features built around making the best out of data, and our platform engineers also sometimes dive into a gnarly report or advise engineers on a more performant data model to use. You don’t want to code. Our SREs are some of our best software engineers and they are just as responsible for the application as the other engineering teams - albeit at a platform level. Reviewing code and submitting code changes will be part of your day to day. Your primary mode of communicating best practices to engineers is live meetings. We’re a very async culture and written communication (and code) is how changes get made. As an Ashby SRE, you will need to share new tooling and best practices with engineers faster than your next meeting opportunity will take you. You’ve never delivered a project, on your own, without someone prodding you for updates. We have no project or delivery managers to fill your calendar with busy work, but the flip side is you have to do your project management, seek the help you need to get unstuck and cut scope when it’s worthwhile. Technology Stack I’m sharing our tech stack with the caveat that we don’t require previous experience in it: TypeScript (frontend & backend), Node.js, React, Apollo GraphQL, Postgres, Redis. We use Datadog and Sentry on 100% cloud-based (AWS) infra. We take developer experience and reliability seriously: all engineers are on call in a follow-the-sun model, and everyone contributes to developer tooling. 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 Abhik and Benji’s (our co-founders) 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 (Abhik 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 technical design, debugging incidents, 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 b

Job DescriptionJob Title: Production Database Administrator Location-Type: Remote (EST or CST hours preferred) Start Date Is: ASAP Duration: Permanent Compensation Range: $160-180 K Job Description: * Monitor systems and proactively manage and maintain configurations to ensure performance, availability, and stability. * Submits, Coaches and Assists in Implementation of recommendations for solutions that require the definition of the physical structure and functional capabilities of databases and require data security and data backup and recovery specifications. * Provides database mentoring, problem support, and solutions to application developers, business analysts, and business users. * On-Call Rotation (approximately 1 week a month). * Development of SQL scheduled/periodic code, reports and ad hoc queries to support critical SQL based business systems. * Performs and oversees scheduled backup, index defragmentation, AG maintenance and operations, and, when necessary, restore operations. * Analyzes system performance to plan for capacity management and scalability. * Act as a SQL Server subject matter expert for large/long term Enterprise projects. * Conducts research and prepares recommendations for database tools, software, and/or hardware requirements. Requirements: * 5-10 years managing enterprise-level database environments in production that deal with high transaction volume. Hands on experience with highly concurrent VLDB SQL Server environments. * Extensive knowledge of Microsoft SQL Server 2016& 2017 (2019, 2022 a plus). * Solid experience with SQL Server High Availability (HA) configuration via Availability * Groups (AG) cluster setup. Specific details of AG Experience needed: * o Build, maintain, and add nodes specifically in AWS using EC2 instances. * Troubleshoot performance related AG issues in a Production Environment. * Read-scale secondaries with routing. * o Logins/SQL Agent jobs in AGs. * o Experience troubleshooting redo latency in secondaries. * o Failover/failback in a Production environment. * Advanced T-SQL skills. * Hands on experience with Powershell. Hands on experience with dbatools.io, as well as * SQLServerDSC is a plus. * Production monitoring and alerting using DMVs and 3rd party tools. Ability to quickly triage and troubleshoot production issues using the DMVs and 3 rd party tooling to remove bottlenecks. * Experience with replication and change capture, including setup, troubleshooting, and creating replication scripts. Experience with log shipping, mirrors * Experience with QLIK (Attunity) a plus * Expert performance troubleshooting skills. * Strong understanding of Windows Clustering, Always-On, and Partitioning. * Able to implement Disaster Recovery methods. Real disaster recovery experiences in production, such as corruption/bad drives etc * 3rd Party monitoring tools, including but not limited to SQL Sentry Monitoring and * SolarWinds Database Performance Analyzer (DPA). * Ability to review developer code to ensure integrity of deployment and stability of the environment. * Proven, demonstrable history of taking a proactive role in a DBA support team. Clear, concise communication. * Bachelors Degree Required

This team provides Commercial Lines of Insurance, 401(k), and Life Insurance needed in today's world to safeguard the businesses across the North Region. As a Region Manager, you'll hire and develop a team of Account Executives who will sell our Sentry products including commercial insurance, 401(k)

Job DescriptionCompany Description Vichara is a Financial Services focused products and services firm headquartered in NY and building systems for some of the largest i-banks and hedge funds in the world. Job Description Job Summary COMPANY DESCRIPTION Vichara is a Financial Services focussed products and services firm hedquartered in NY and building systems for some of the largest i-banks and hedge funds in the world. ROLE Lead Development of the Order Management System - Broadridge, Charles River Allvue Black Mountain Everest , BMS and its integration for Vichara's investment management clients Responsibilities and Duties JOB DESCRIPTION • Oversee end-to-end implementation of Broadridge's Sentry platform, ensuring timely and efficient delivery., • Work closely with client stakeholders to gather requirements, define project scopes, • Troubleshoot and resolve technical issues during and post-implementation., • Implement interfaces to third party systems like Advent Geneva and others using XSLT, XML, and SQL technologies, • Work with Business users on defining spec, • QA and Testing, • Qualifications, • Required Experience, Skills and Qualifications • 7 plus years of product management experience with investment systems like Geneva, OMS, Markit EDM, • Atleast 3 years of experience on Broadridge Sentry or Allvue Everest, • Strong understanding of Loans, Credit, Debt and other asset classes., • Experience working directly with business users Additional Information Benefits Compensation -140K base plus 401K, guaranteed bonus

We help drive business transformation for our clients, including asset managers, with solutions for enriching engagement, navigating risk, optimizing efficiency, and growing revenue. Broadridge is hiring a General Manager, Sentry.

Front End Developer With AWS Cloud Expertise. Must possess basic knowledge of our platforms and systems: EC2, Elastic Beanstalk, CloudWatch, Docker, ActiveMQ, RDS/Postgres, Firebase and Sentry.

Front End Developer With Cloud Expertise.Duration: 12 Months Contract Position.Required Skills: Overall 3+ years' experience.Must possess basic knowledge of our platforms and systems: EC2, Elastic Beanstalk, CloudWatch, Docker, ActiveMQ, RDS/Postgres, Firebase and Sentry.

Job Description#TeamNextdoor Nextdoor (NYSE: NXDR) is the essential neighborhood network. Neighbors, public agencies, and businesses use Nextdoor to connect around local information that matters in more than 340,000 neighborhoods across 11 countries. Nextdoor builds innovative technology to foster local community, share important news, and create neighborhood connections at scale. Download the app and join the neighborhood at nextdoor.com. Meet Your Future Neighbors At Nextdoor, Cloud Engineers are responsible for building, deploying, managing, and securing the underlying cloud-based architecture that powers communities on the Nextdoor platform worldwide. These engineers have designed, built and implemented a globally scalable container and "serverless" based infrastructure that serves billions of requests a day, millions of active users, and hundreds of developers. We build infrastructure and tooling that is iterable, scalable, and secure. We write everything in code from network infrastructure to server management, database provisioning, and data pipelines. Recently we have focused on scaling up our Kubernetes infrastructure. We created a dedicated management cluster to run ArgoCD, Loki, Prometheus, and Grafana. Additionally, we have created a second Kubernetes cluster for Nextdoor applications to ensure we can scale beyond the limitations of a single cluster. This will ensure Nextdoor's infrastructure is able to scale for many years to come. Additionally our team has focused efforts to modernize our Infrastructure as Code (IaC) by leveraging CDK to manage our AWS resources and Pulumi to manage our other core infrastructure systems such as PagerDuty, Datadog, and Sentry. At Nextdoor, we offer a warm and inclusive work environment that embraces a hybrid employment experience, providing a flexible experience for our valued employees. The Impact You'll Make You will be responsible for building an efficient and scalable container and serverless computing environment for our product developers. In this team you will work in the ways of reliability engineering, design scalable systems from the ground up, and generally build systems that never page you. You serve all of our engineering teams by providing them with reliable and scalable infrastructure. Here are just some of our team's most recent deliverables: • Operationalizing a second Kubernetes cluster to ensure Nextdoor can continue to scale beyond the limits of a single Kubernetes cluster, • Building automation for our developer's workflows including applying 3rd party dependency updates automatically as well as distributing Helm chart updates, • Modernizing our Infrastructure as Code (IaC) by leveraging CDK and Pulumi, • Optimizing our Kubernetes resource management by leveraging Spot Ocean and Karpenter, • Providing self-service infrastructure-as-code systems to developers that automate the full lifecycle of managing, deploying and operating cloud services including blob/block storage, relational databases, key-value databases, caches and document search services, • Developing tooling for horizontally and vertically autoscaling our developers compute workloads, • Providing upstream open source patches to well known community projects like AWS Bottlerocket, the Istio Service Mesh, Keiko IAM Manager, Kyverno, Strimzi.io's Kafka Operator and more!What You'll Bring to The Team, • 7+ years experience in a DevOps or Cloud role, • Solid understanding of Kubernetes (k8s), • Experience using TypeScript, • Experience with infrastructure as code (CDK, Pulumi, CloudFormation, Puppet, Salt, Ansible, Terraform, Packer), • Thorough understanding of Linux and networking protocols (TCP/IP, UDP, HTTP/S, eBPF), • Strong debugging and performance tuning skills using software like gdb, perf, strace, ltrace, tcpdump, Wireshark, etc., • Experience with performance, automation, monitoring, and capacity planning, • Experience automating configuration and bootstrapping of Linux systems, • Eagerness to explore and apply AI and emerging technologies to reimagine how work gets doneBonus Points, • Experience using Docker or other containerization software, • Linux certifications such as Linux+, Network+, RHCSA/RHCE/RHCA or similar The starting salary for this role is expected to range from $187,000 to $238,000 on an annualized basis, or potentially greater in the event that your 'level' of proficiency exceeds the level expected for the role. We expect to award a meaningful equity grant for this role. With quarterly vesting, your first vest date will take place within 3 months of your start date. When it comes to benefits, we have you covered! Nextdoor employees can choose between a variety of health plans, including a 100% covered employee only plan option, and we also provide a OneMedical membership for concierge care. At Nextdoor, we empower our employees to build stronger local communities. To create a platform where all feel welcome, we want our workforce to reflect the diversity of the neighbors we serve. We encourage everyone interested in our mission to apply. We do not discriminate on the basis of race, gender, religion, sexual orientation, age, or any other trait that unfairly targets a group of people. In accordance with the San Francisco Fair Chance Ordinance, we always consider qualified applicants with arrest and conviction records. For information about our collection and use of applicants' personal information, please see Nextdoor's Personnel Privacy Notice, found here.

Job Description Title: Product Lead Engineer – AI-Driven Healthcare Automation Overview We’re building advanced AI tools that automate critical administrative processes in healthcare, starting with home health. Our platform streamlines workflows like prior authorization, eligibility checks, and benefit verification by integrating deeply into provider systems — freeing healthcare teams to focus on patient care instead of paperwork. This role combines product ownership and technical leadership, requiring a strong understanding of healthcare operations, product strategy, and engineering execution. You’ll collaborate closely with engineers, domain experts, and customers to turn complex workflows into measurable wins, with a clear growth path toward leading product engineering for your domain. What You’ll Do 1. Own the Automation Vision * Map entire user journeys — from initial data capture (e.g., clinician notes) to successful claim payment. * Translate operational needs into clear product roadmaps with measurable goals. * Define success metrics and set data-backed OKRs for your area. * Prioritize feature development in small, testable increments for rapid feedback and improvement. 2. Design & Deliver Cross-Domain Features * Lead discovery sessions, develop quick prototypes, and create detailed product specifications. * Collaborate with engineering to select appropriate AI models, business rules, and APIs. * Manage customer pilots, gather structured feedback, and iterate to maximize impact. * Example projects: * Implementing a voice capture pipeline for a Voice Scribe product. * Refining LLM-based medical coding workflows. 3. Drive Quality, Compliance, & Continuous Improvement * Monitor system performance in real time (accuracy, latency, financial KPIs) and address outliers quickly. * Design human-in-the-loop review systems and feed results back into AI model or rule tuning. * Ensure HIPAA compliance, robust audit trails, and payer-rule updates in every release. RequirementsPreferred Expertise Experience in one or more of the following areas is highly valued: * Voice Scribe – AI-driven clinical transcription workflows. * LLM-based Medical Coding – Applying large language models to accelerate accurate coding. * Accounts Receivable / Billing – Streamlining payment collection and reducing denial rates. Qualifications * Proven experience shipping production-grade automation in a healthcare or regulated environment. * Strong analytical skills — ability to measure and improve KPIs through iterative releases. * Excellent communication skills — comfortable interfacing with engineers, leadership, and end-users. * Deep understanding of privacy and security best practices for PHI. * Bachelor’s degree in Computer Science or related field (or equivalent hands-on experience). * Drive to take ownership and scale into a product or engineering leadership role as the company grows. Our Tech Stack Infrastructure / Ops: AWS, Terraform, Docker, Datadog, Sentry, Modal Frontend: Next.js, React, Posthog, Amplify AWS Backend: FastAPI, Pydantic, PostgreSQL BenefitsFull Benefits