kellysutton

Scholarly | Senior Software Engineer | Seattle, On-Site | Full-Time | $160k - $200k + equity + health benefits + equipment budget

Scholarly is building the HR operating system for higher education. We've built a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, tenure processes, leave workflows, and more. We are a venture-backed seed stage company of experienced, motivated, and collaborative folks. We are backed by leading investors in the industry and working with some of the best universities in the US. The team comes from Gusto, NASA JPL, Amazon, Outreach, and others.

We're looking for a full-stack candidate with 8 or more years of experience building web applications. We write Ruby and Rails, but we are considering candidates with other stack experiences. Engineering is based in Seattle and on site in Pioneer Square. Looking to get back to a collaborative, in-office culture post-COVID? Let's chat.

If interested, please apply here: https://jobs.ashbyhq.com/Scholarly/d4c84468-fd4b-4dd7-9b22-2...

Scholarly | Senior Software Engineer | Seattle, On-Site | Full-Time | $160k - $200k + equity + health benefits + equipment budget

Scholarly is building the HR operating system for higher education. We've built a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, tenure processes, leave workflows, and more. We are a venture-backed seed stage company of experienced, motivated, and collaborative folks. We are backed by leading investors in the industry and working with some of the best universities in the US.

We're looking for a full-stack candidate without about 5 years of experience building web applications. We write Ruby and Rails, but we are considering candidates with other stack experiences. Engineering is based in Seattle and on site in Pioneer Square. Looking to get back to a collaborative, in-office culture post-COVID? Let's chat.

If interested, please apply here: https://jobs.ashbyhq.com/Scholarly/d4c84468-fd4b-4dd7-9b22-2...

Scholarly | Software Engineer | Seattle, On-Site | Full-Time | $130k - $200k + equity + health benefits + equipment budget

Scholarly is building the HR operating system for higher education. We've built a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, tenure processes, leave workflows, and more. We are a venture-backed seed stage company of experienced, motivated, and collaborative folks. We are backed by leading investors in the industry and working with some of the best universities in the US.

We're looking for a full-stack candidate without about 5 years of experience building web applications. We write Ruby and Rails, but we are considering candidates with other stack experiences. Engineering is based in Seattle and on site in Pioneer Square. Looking to get back to a collaborative, in-office culture post-COVID? Let's chat.

If interested, please apply here: https://jobs.ashbyhq.com/Scholarly/1835336e-2b79-4531-82a0-f...

Scholarly | Full-stack Software Engineer | Seattle, On-Site | Full-Time | $130k - $200k + equity + health benefits + equipment budget

Scholarly is building the HR operating system for higher education. We've built a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, tenure processes, leave workflows, and more. We are a venture-backed seed stage company of experienced, motivated, and collaborative folks. We are backed by leading investors in the industry and working with some of the best universities in the US.

We're looking for mid-level and senior-level full-stack candidates without about 5 or more years of experience building web applications. We write Ruby and Rails, but we are considering candidates with other stack experiences. Engineering is based in Seattle and on site in Pioneer Square. Looking to get back to a collaborative, in-office culture post-COVID? Let's chat.

If interested, please apply here: https://scholarly.breezy.hr/p/f3bc050f524d-software-engineer

Scholarly | Software Engineer | Seattle, On-Site | Full-Time | $130k - $160k + equity + health benefits + equipment budget

Scholarly is building the HR operating system for higher education. We've built a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, tenure processes, leave workflows, and more. We are a venture-backed seed stage company of experienced, motivated, and collaborative folks. We are backed by leading investors in the industry and working with some of the best universities in the US.

We're looking for a junior- to mid-level full-stack candidate without about 5 years of experience building web applications. We write Ruby and Rails, but we are considering candidates with other stack experiences. Engineering is based in Seattle and on site in Pioneer Square. Looking to get back to a collaborate, in-office culture post-COVID? Let's chat.

If interested, please apply here: https://scholarly.breezy.hr/p/f3bc050f524d-software-engineer

As a PlanetScale MySQL user for the past 2 years, this is really exciting for the Postgres community. (Worked at a company that ran both, was a bummer our tooling didn’t match.)

Using PlanetScale for db management is like using an iPhone after being accustomed to a Treo. The experience is just better in every way.

Congrats to the PlanetScale team!

Scholarly | Software Engineer | Seattle, On-Site | Full-Time | $130k - $160k + equity

Scholarly is building the operating system for higher education. Our vision is to build the future system of record for the industry. We are building a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, tenure processes, leave workflows, and more. We are a seed stage company of experienced, motivated, and collaborative founders. We are a seed stage company of about 10 folks. We are backed by leading investors in the industry and working with some of the best universities in the US.

We're looking for a junior- to mid-level full-stack candidate without about 5 years of experience building web applications. We write Ruby and Rails, but we are considering candidates with other stack experiences.

If interested, please apply here: https://scholarly.breezy.hr/p/f3bc050f524d-software-engineer

Why did you do this again?

Because I was so preoccupied with whether or not I could that I didn’t stop to think if I should.

A+. A great hack.

Sorry. Will try to fix

I'd encourage you to spend an afternoon kicking the tires on Turbo/StimulusJS, HTMX, Laravel Livewire, or Phoenix LiveView!

The original post could have been a bit more precise on this point. Basically, this math assumes something where the server-provided data changes in concert with the frontend.

If we're using jsonapi, GraphQL, Thrift, or any other protocol that's not HTML, we need to do the following:

- Make the change on the server to support the new functionality. Deploy.

- Make the change on the client to adopt the new functionality. Deploy.

- Remove the old functionality from the server (optional)

Because the client is a separate application, it becomes riskier to deploy those changes together. I need to think about it more as a developer.

With server-authored HTML, this separate client + server deploy is not required.

I don't have a reason for switching away from Ruby at this point in my career. Things can always change down the line. Maintaining multiple languages at the same layer sounds like a personal nightmare to me. I'd rather learn to write PHP and have that be the only language, than to write Ruby+another language on the server-side.

We're building our company on Rails because we think it's the best choice for a young company, since it allows us to respond to customer feedback more quickly. That's what we're optimizing for right now!

Yes

Haven't written much TS, so can't speak to that.

I should have made the distinction between client-side and server-side JS/TS. Familiarity and expertise will be a main driver of productivity for a team, regardless of language/framework. For us, that's RoR.

Client-side JS however has a multiplying property, where we often need to write more server-side code to accommodate the growth in client-side code. If the client-side code is providing undifferentiated value (e.g. authoring HTML), we now have more pieces in our system to accomplish our goal (author HTML). What's been surprising to me is that you don't need to author HTML client-side to have a reactive experience. With Turbo, Stimulus, and server-rendered HTML, a great experience is possible with fewer layers.

A friend mentioned this made the front page. I'll try to answer any questions on our approach at Scholarly. Thanks for reading!

Scholarly | Software Engineer | On-site - Seattle, WA | $150k - $200k | 0.5%+ equity

Scholarly is building the operating system for higher education. Think: Gusto, Rippling, or Workday for universities.

We are hiring software engineer #4 for the team. This is a unique opportunity to have a major impact on the company’s success and the team culture.

We are based in Seattle and Denver, with engineering based primarily in Seattle. We are looking for an engineer with at least 5 years of experience in Ruby on Rails.

This position is in-office in Seattle.

Please apply using the following link: https://scholarly.breezy.hr/p/a8959b02b8bd-software-engineer

Scholarly | Software Engineer | On-site - Seattle, WA | $150k - $200k | 0.5%+ equity

Scholarly is building next-generation software for higher education with a focus on faculty. Think: Gusto, Rippling, or Workday for universities.

Higher ed is currently undergoing a generational shift in software and technology adoption, and our vision is to build the system of record for the industry. We are building a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, which will ultimately enable them to better serve both students and faculty. Our team comes from Gusto, Modern Health, and Vail Resorts.

We are hiring software engineer #3 for the team. This is a unique opportunity to have a major impact on the company’s success and the team culture. This engineer will work closely with the CEO and CTO to build the initial version of the product, work closely with customers, and help set the culture of the company. We expect you to be able to define and challenge product requirements, seek customer feedback, and stick with projects until customers are satisfied or we’ve removed the feature. We are looking for a true partner who loves the challenge of building great software from the ground up.

We are based in Seattle and Denver, with engineering based primarily in Seattle. Job Requirements

- At least 5 years working in Ruby on Rails

- Familiarity with JavaScript

- Experience working with a relational database, like MySQL or Postgres

- Able to work in the United States (citizen or permanent resident). We cannot sponsor visas at this time

Compensation and Benefits

- The salary range for this role is $150k - $200k, depending on experience.

- Substantial equity in the company

- Health, vision, and dental benefits with 100% of premiums covered by the company

- $3,000 equipment budget

Please apply using the following link: https://scholarly.breezy.hr/p/a260aae8c3dc-software-engineer

Scholarly | Software Engineer | On-site - Seattle, WA | $150k - $200k | 0.5%+ equity

Scholarly is building next-generation software for higher education with a focus on faculty. Higher ed is currently undergoing a generational shift in software and technology adoption, and our vision is to build the future system of record for the industry. We are building a software platform that enables our customers to make data-driven decisions and to automate essential processes like performance reviews, which will ultimately enable them to better serve both students and faculty. We are a team of experienced, motivated, and collaborative founders, and we are backed by leading investors in the industry.

We are hiring a software engineer for the team. This is a unique opportunity to have a major impact on the company’s success and the team culture. This engineer will work closely with the CEO and CTO to build the initial version of the product, work closely with customers, and help set the culture of the company. We expect you to be able to define and challenge product requirements, seek customer feedback, and stick with projects until customers are satisfied or we’ve removed the feature. We are looking for a true partner who loves the challenge of building great software from the ground up.

We are based in Seattle and Denver, with engineering based primarily in Seattle.

Job Requirements

- At least 5 years working in Ruby on Rails

- Familiarity with JavaScript

- Experience working with a relational database, like MySQL or Postgres

- Able to work in the United States (citizen or permanent resident). We cannot sponsor visas at this time

Compensation and Benefits

- The salary range for this role is $150k - $200k, depending on experience.

- Substantial equity in the company

- Health, vision, and dental benefits with 100% of premiums covered by the company

- $3,000 equipment budget

https://scholarly.breezy.hr/p/a260aae8c3dc-software-engineer

(Edit: Formatting)

This feels novel. Very interesting to turn a lifetime's worth of work into an LLM.

Scholarly Software | Founding Software Engineering | Remote (US Only), Seattle, or Denver | Full-Time | https://scholarlysoftware.com/careers

$140k - $200k. Substantial equity.

Scholarly is building next-generation software for higher ed with a focus on faculty. We are starting off with performance review software for faculty and hoping to grow into a broader HR platform over time.

We were founded in June 2023. We've raised $1M in pre-seed financing and are going live with our first customers. We're looking for a pragmatic, hands-on engineer who loves developing empathy with customers.

Rails, StimulusJS, Heroku, PlanetScale

Now feels like a good time to mention the talk "Ideology" by Gary Bernhardt. https://www.destroyallsoftware.com/talks/ideology

Tests and Types are useful for preventing errors, but the types of errors they can prevent differ. You probably need both!

This post resonates with a lesson I’ve learned in my career so far: It is always easier to relax constraints than tighten them.

Thanks for the compliments and thanks for the feedback!

I've forwarded these requests along to the team that owns our time tracking functionality.

Gusto | Software Engineer | SF, NYC, Denver, or Remote (US/Canada) | Full-time | $143-$243k base | https://boards.greenhouse.io/gusto/jobs/3441405

Gusto's hiring in just about every engineering department, but the above link is for our product infrastructure engineering team (the team I'm on). Gusto provides payroll, benefits, and HR tools to small businesses in the United States. We recently raised a Series E and have the privilege of serving over 200K small businesses.

Product Infrastructure is responsible for maintaining and improving the monoliths at Gusto. This means going deep into our core technologies like Rails, Ruby, Sidekiq, and React, to design and develop tools for our fellow engineers working on the product.

We often collaborate with some of the other big Ruby shops out there to improve tooling like Packwerk, Sorbet, Sidekiq, and Rails itself.

I've been at the company for 5 years and still find plenty of opportunity for impact, and love the teammates I'm working with. Feel free to apply using the link above or reach out to me directly.

We’ve got an episode on this. Check out “Tests should be deterministic.” https://youtu.be/PwWyp-wpFiw

To put some more to it: I like my tests to not use random data, but I’ll use a random data generator when coming with the test cases. That way I don’t get surprises in CI with a flakey test, but I can still generate interesting cases.

In the same vein of repair and things having a long life, I'm experimenting with the idea of giving unused things new homes. We own many things that are not utilized often, so why not move those things better homes?

https://cultofless.com

We use this pattern in our Ruby apps to safely move $1B+/month at Gusto.

You don’t need full blown monads to do this, just need to be cognizant to how you separate the what (functional core) from the how (imperative shell). I recommend giving it a try!

Do we need GraphQL? https://kellysutton.com/2017/01/02/do-we-need-graphql.html

(Disclaimer: From my personal blog)

This sounds like a good application of Gall's Law:

A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system.

Now is a good time to mention the great blog post, "So you want to write a package manager," by Sam Boyer: https://medium.com/@sdboyer/so-you-want-to-write-a-package-m...