I am in SD and would love an invite. I am keep thinking about uniting more like minded people for a while. My email is r@seslu.com

Hear hear

Pex | REMOTE (Europe), FULL-TIME | https://pex.com/careers/

Pex is a digital rights technology company, enabling the fair and transparent use of copyrighted content at the speed and scale of the Internet. We serve everyone who uses the Internet to view, share or create content – from the largest platforms and rightsholders, to independent creators. Our advanced licensing infrastructure allows platforms to manage and license content before it’s published, empowering creators to upload freely while respecting copyright. In return, rightsholders are able to monitor and capitalize on the content they own.

We are hiring for Senior Reverse Engineer/Senior Data Harvesting Engineer (Europe) to help us bring our services to the masses! Reach out to jobs@pex.com.

We offer:

  - salary: $103,000 – $110,000 USD per annum
  - equity, with a 10-year exercise window
  - 30 days of paid time off + 9 local holidays + the day off on your birthday
  - generous paid parental leave
  - a fully remote work environment, supportive culture, and excellent work-life balance

To learn more about our hiring and culture, take a look in our blog posts titled:

  - Interviewing at Pex? Here's what you can expect during our hiring process [1]
  - Pex culture: Focusing on what really matters [2]

  [1] https://pex.com/blog/interviewing-at-pex-heres-what-you-can-expect-hiring-process/
  [2] https://pex.com/blog/pex-culture-focusing-on-what-really-matters/

There are 27 countries in EU with different motives, morals, interests, etc. Just because you agree with the decision of one country in one instance it doesn't mean you would agree with them all. But once you give them the powers it's impossible to take them back. It's a bad slippery slope.

Just to be clear here, your issue is with the number of member states in the EU?

In other words you would be fine with Canada arresting employees of Clearview if they tried to enter the country after Canada deemed them profiting members of an organization that was breaking the law in Canada?

The courts are altering their views on scrapping. This [0] is a good paper that explored the last 20 years of rulings (although it hasn't been updated with the most recent cases).

[0] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3221625

Quick note for the osohq team: The "Read the docs" button leads to 404

Doh, fixing now. Thank you!

Modus [himodus.com] | REMOTE (US Only) | Full-time | Staff/principal positions only | $300k + 5% stock

Modus is a continuous workforce management platform that makes headcount planning and reconciliation easy. The platform analyzes thousands of bits of data across the organization to help leaders optimize their workforce and increase forecast accuracy. With the help of AI, Modus synthesizes insights from HRIS, ATS, expense and finance systems so leaders can visualize and execute workforce plans, grow efficiently and compliantly, and unlock high performing teams in one unified workflow.

While we are just at the beginning, both founders have extensive experience in the industry. One of the co-founders was early Google engineer and built multiple companies in the past, writing significant amount of code at each company. The other cofounder has scaled from 100 to 2500+, through to IPO and beyond. Joining as our first engineer and designer means you have will have an outsized influence on the tech and design choices.

We are currently only looking for very senior colleagues to help us move much faster:

   - Staff level frontend engineer - At least 5 years of staff level frontend development experience with Svelte, React, Next.js, Vue (strong preference for Svelte)
   - Principal Product Designer - Preferably designer with strong rapid prototyping skills, 10+ years of experience with designing B2B software, especially complex dashboards with a lots of data (strong preference for either Fintech or HR tech experience)

All candidates must be physically located in the US. No exceptions. Bonus for being located in CA and even better, San Diego.

Interview process: phone call, interview with each founder separately, reference checks, and offer (can be done in less than a week).

If interested, please reach out to hire@himodus.com.

I think that's a valid criticism. What do you think would be a more ergonomic pattern?

I wrote a static config class that reads configuration for the entire app / server from a JSON or YAML file ( https://github.com/uber/zanzibar/blob/master/runtime/static_... ).

Once you've loaded it and mutated it for testing purposes or for copying from ENV vars into the config, you can then freeze it before passing it down to all your app level code.

Having this wrapper object that can be frozen and has a `get()` method to read JSON like data make it effectively not mutable.

I use similar pattern myself. Was curious if the OP is using some other, like for instance splitting the struct into two (im/mutable) and then passing them around, or what.

BTW kudos on zanzibar. Love the tech and the code).

Not the OP, but I mitigate the issue rather than use a different pattern. Like so:

type Server struct { val bool }

type Config struct { Val bool }

func NewServer(... config *Config ...) http.Handler { if config == nil { config = &Config{} } return &Server{ val: config.Val } }

It took me a long time to settle on this pattern and I admit it's tedious to copy configuration over to the server struct, but I've found that it ends up being the least verbose and maintainable long term while making sure callers can't mutate config after the fact.

I can pass nil to NewServer to say "just the usual, please", customize everything, or surgically change a single option.

It's also useful for maintaining backwards compatibility. I'm free to refactor config on my server struct and "upgrade" deprecated config arguments inside my NewServer function.

I just use a struct literal, and then I have the type define a `func (t *Thing) ready() error { ... }` method and call the ready method to check that its valid. I prefer this over self-referential options, the builder pattern, supplying a secondary config object as a parameter to a constructor, etc.

Modus [himodus.com] | United States | REMOTE | Full-time | $150-220k + very early shares, employee #1-5

Modus is a continuous workforce compliance and planning platform that enables various employees throughout the organization to stay compliant with labor laws, visualize and execute workforce plans, and make data-driven decisions to ensure fairness and equity. You can think of us as Vanta for HR. Our mission is integrity. We've all been through the pains of levels, benchmarks, compensation inequities. Why can't HR tech be intuitive, easy to use, and encompass workflows for everyone in the org?

While we are just at the beginning, both founders have an extensive experience in the industry. One of the co-founders was early Google engineer and built multiple companies in the past, writing significant amount of code at each company. Joining early means you have a significant say into tech and design choices.

We are looking for curious and motivated colleagues to turn our vision into a reality. All positions are 100% remote with no on-site requirements of any kind. We are currently looking for:

  - Javascript/frontend developers
  - Designers
  - Backend developers

Interview process: phone call, "take-home" exercise, interview with each founder separately, reference checks, and offer (can be done in less than a week)

If interested, please reach out to hire@himodus.com

Do you hire outside of US? what about Europe?

Are there alternatives to the "take home exercise"?

I've had several bad experiences with those where I waste dozens of hours of my own time only to be rejected or have to decline the offer shortly afterwards.

So now I pretty much don't apply anywhere that uses take home projects in the interview process.

I very much understand your sentiment. Unfortunately we haven't found any other functional way to achieve the same goal.

I am not sure about other firms, but we personally look for how the candidate thinks about the problem more than anything. Did they handle exceptions well. Are they focusing on efficiency, readability, speed, or?

We found out that from a simple assignment that shouldn't take more than 30 min, we learn more than sitting with the person for hours. Plus they can do at their own pace without someone breathing down on their neck.

If the assignment really only takes 30 minutes, why can't it be a live call if the candidate wants?

whether you like it or not, take home assignments just select for the people who can spend the most time on take home assignments.

Which means people like me who have a current job and a family and can't afford to spend several hours on a coding test to make sure they're above and beyond the competition either won't apply, or will send in results that will be much often worse than the competition because we actually only spent 30 minutes on it.

I understand your sentiment and makes sense.

Unfortunately, majority of candidates are interested in the take home challenge over doing live coding session. And we optimize for the widest reach.

In regards of the results, I can't speak for others, but I write code for 26 years. What I look for is how the candidate thinks of the problem. Here is one of my favorite exercises [0]. I would obviously love to do this live but people get super nervous and stop thinking. I then have tendency to help them too much and learn much about them.

[0] https://news.ycombinator.com/item?id=39263923

Do you really get people who "handle exceptions" and "focus on efficiency, readability, speed" in a 30 min take home exercise?

Let me give you an exercise I really like for this.

Imagine a file with endless list of URLs. For each URL check if it contains an image. If it does, identify the top 6 colors and store it memory so it can be printed/stored later.

In something like python this can be as short as 20 lines of code: - open the file - read line by line - validate if the URL is valid - call the URL - check if it's image - if image, read pixel by pixel and check the color - store it in dictionary/hashmap

Here is what I look for: - does it compile/work? - what language did you choose? (like python is fast to write this in few lines but hard to introduce concurrency) - have you introduced some kind of caching for the URLs? (so you don't waste resources) - are you checking if the URL is valid or you just run them all and wait for errors/timeouts? - are you checking the file type from HTTP header or body of the file? - how do you handle errors? - are you attempting concurrency? If yes, how?

I actually done this exercise myself in dozen or so languages to see what choices I make based on the language. Obviously one can spend significantly more time on it if they really desire, but the design choices are visible from the beginning.

What's the desired tech stack for a Backend dev role?

Honestly someone who understands the environment they are developing in. I don't care about the language as much as I care about understanding the choice they make.

But ultimately we are using SQL, queue, concurrency, single tenancy and monolith (few to none micro services).