SchooLinks is a globally distributed, remote-friendly, and venture-backed startup. SchooLinks is an ed-tech company that is changing how students explore and pursue their post-high school goals. We have a suite of over 80 tools for students and school staff including college application management, course planning, financial situations, personality assessments, college profiles, and many others.We presently do not have the ability to sponsor H1-B VisasSchooLinks is looking for a highly motivated software engineer to support our Partner Success and Sales team in onboarding and maintaining our customers' data within the SchooLinks Platform.  People who have done well in this role have come from very technical backgrounds and enjoy customer or client-facing interactions.What you'll do:<ul><li>Maintain and expand a Python-ETL framework to consume this data and load it into our database (write production quality python code)</li><li>Iterate and innovate upon our existing processes and code base to handle data at scale</li><li>Support our partner success team in data-related onboarding tasks and ongoing support of existing customers</li><li>Deeply understand the context and data generating process of our inputs</li><li>Develop reporting tools for districts to use on the data inside our platform</li></ul>We're looking for people who have:<ul><li>5+ years of Python experience (specifically with Pandas)</li><li>5+ years of experience modeling and writing queries for relational databases (SQL)</li><li>Experience working with US K-12 Education data</li><li>Experience in a client-facing engineering role</li><li>Experience with modern software development and project management tools such as Git and JIRA</li><li>Experience writing production-quality code</li></ul>Nice to haves -- experience with the following technology that we use regularly:<ul><li>Experience with Django</li><li>Knowledge of data interoperability standards such as OneRoster, Ed-Fi, and others</li><li>Experience working at an early-stage startup</li><li>Domain experience/interest in the following areas are a bonus:<ul><li>ETL and data integration with third party systems such as Student Information Systems</li><li>Educational data</li><li>Workforce development and career exploration</li><li>Predictive analytics around educational outcomes</li></ul></li></ul>FAQs<ul><li>What is the team size we'll be working with? <ul><li>You'll be working within one of our pods of 4-5 engineers, a designer, engineering lead, and QA engineer</li></ul></li><li>What's your tech stack and other tools you use daily? <ul><li>FE: React (16.14 with JS), React-query, some redux, but moving away from it and making more use of hooks and component state, GraphQL, Webpack. MUI, Nivo, Final Form</li><li>BE: Django, DRF, Celery, MySQL, Redis</li><li>AWS</li><li>Sentry</li><li>Jenkins</li><li>Github, Jira, Slack, Notion, Loom</li></ul></li><li>Tell us about your dev practices <ul><li>Pragmatic is the best way to describe. We use eslint and prettier to keep code clean. We have some tests for code that we know is going to be around for a while or many modules depend on, but we're not strictly TDD. We tend to ship MVPs quickly and then go back and refactor and/or rebuild when we have more learnings and better ideas about how to abstract products. The name of the game for us is speed to market. We ship major releases every two weeks</li></ul></li><li>Tell us about your general working style <ul><li>Asynchronous - we tend to try to get as much communication into structured formats as possible -- PRs, documentation, comments, Jira tickets vs. scheduling meetings. We do try to have the majority of our meetings around our standup to make sure that our teammates have as much focused deep work time as possible</li><li>Remote- we have a small number of engineers on-site, but many distributed as well as much of our leadership distributed, so you can be a full-fledged member of our team and not be in the office in Austin (this was from before the pandemic and will be the case after the pandemic)</li><li>Driven- our team members really believe in what we're doing and we work hard because we're personally invested in the outcome and take ownership over the work we do</li></ul></li><li>Will you consider slightly less experienced candidates? <ul><li>Absolutely. We may consider exceptional candidates that have slightly less experience, but this is not a role for junior engineers.</li></ul></li></ul>Benefits<ul><li>Competitive Salary</li><li>Part of a remote-friendly company and a fully remote team/pod</li><li>Flexible working hours and healthy asynchronous working practices</li><li>Long-term employment with considerations for promotion and raises every 6 months</li><li>For US-based candidates:</li><li>Full health (healthcare, vision, dental, ClassPass, etc.)</li><li>Company 401k Program with up to 1% matching</li><li>Career Development and Progression</li></ul>

Software Engineer (Data Operations)

SchooLinks is a globally distributed, remote-friendly, and venture-backed startup. SchooLinks is an ed-tech company that is changing how students explore and pursue their post-high school goals. We have a suite of over 80 tools for students and school staff including college application management, course planning, financial situations, personality assessments, college profiles, and many others.We presently do not have the ability to sponsor H1-B VisasWe're looking for an experienced Django back-end engineer who will write high-quality code, make sound and scalable architectural decisions, and grow our team by bringing and evangelize best practices.What you'll do:<ul><li>You'll be working with a talented team of engineers, designers, and product people who have shipped 50+ features in the last 2 years and have established SchooLinks as a company that has found product-market fit and transitioned us into a hyper-growth phase. </li><li>You will be an individual contributor on one of our three pods. Depending on your career aspirations you can move to move senior IC roles towards an engineering management track </li><li>Participate in the product development process from start to finish, reviewing requirements and user stories to provide timely and meaningful feedback.</li><li>Design and build solutions that will scale to millions of users</li><li>Ship clean, readable, and maintainable back-end Django code</li><li>Actively review code and mentor junior members of our engineering team</li><li>Contribute and proactively elevate the quality of our codebase by writing tests and addressing technical debt</li></ul>We're looking for people who have:<ul><li>4 + years of Python and Django/ DRF experience</li><li>3 + years of experience working with AWS</li><li>3+ years of experience working with SQL database in production</li><li>Experience building, supporting, and planning production</li><li>Experience with asynchronous task management </li></ul>Nice to haves -- experience with the following technology that we use regularly:<ul><li>Celery</li><li>Redis</li><li>AWS Lambda</li><li>Jenkins</li><li>React.js</li></ul>Domain experience/interest in the following areas are a bonus:<ul><li>ETL and data integration with third party systems such as Student Information Systems</li><li>Educational data</li><li>Workforce development and career exploration</li><li>Predictive analytics around educational outcomes</li></ul>FAQs<ul><li>What is the team size we'll be working with? <ul><li>You'll be working within one of our pods of 4-5 engineers, a designer, engineering lead, and QA engineer</li></ul></li><li>What's your tech stack and other tools you use daily? <ul><li>FE: React (16.14 with JS), React-query, some redux, but moving away from it and making more use of hooks and component state, GraphQL, Webpack. MUI, Nivo, Final Form</li><li>BE: Django, DRF, Celery, MySQL, Redis</li><li>AWS</li><li>Sentry</li><li>Jenkins</li><li>Github, Jira, Slack, Notion, Loom</li></ul></li><li>Tell us about your dev practices <ul><li>Pragmatic is the best way to describe. We use eslint and prettier to keep code clean. We have some tests for code that we know is going to be around for a while or many modules depend on, but we're not strictly TDD. We tend to ship MVPs quickly and then go back and refactor and/or rebuild when we have more learnings and better ideas about how to abstract products. The name of the game for us is speed to market. We ship major releases every two weeks</li></ul></li><li>Tell us about your general working style <ul><li>Asynchronous - we tend to try to get as much communication into structured formats as possible -- PRs, documentation, comments, Jira tickets vs. scheduling meetings. We do try to have the majority of our meetings around our standup to make sure that our teammates have as much focused deep work time as possible</li><li>Remote- we have a small number of engineers on-site, but many distributed as well as much of our leadership distributed, so you can be a full-fledged member of our team and not be in the office in Austin (this was from before the pandemic and will be the case after the pandemic)</li><li>Driven- our team members really believe in what we're doing and we work hard because we're personally invested in the outcome and take ownership over the work we do</li></ul></li><li>Will you consider slightly less experienced candidates? <ul><li>Absolutely. We may consider exceptional candidates that have slightly less experience, but this is not a role for junior engineers.</li></ul></li></ul>Benefits<ul><li>Competitive Salary</li><li>Part of a remote-friendly company and a fully remote team/pod</li><li>Flexible working hours and healthy asynchronous working practices</li><li>Long term employment with considerations for promotion and raises every 6 months</li><li>For US-based candidates:<ul><li>Full health (healthcare, vision, dental, ClassPass, etc.)</li><li>Company 401k Program with up to 1% matching</li></ul></li></ul>

schoolinks.com

schoolinks.com jobs for JavaScript developers

Categories

Locations

Collections