At CourtDrive.com, we are building an AI Docketing Assistant that enables law firms and other power courthouse website users to become more efficient by automating daily tasks. We’re based in Los Angeles but have a remote team worldwide (Canada, Europe, Armenia to name a few). Your role as Principal AI Engineer will be to lead CourtDrive's AI strategy through model evaluation, fine-tuning, and data collection. You'll work alongside our engineering team to bring AI features from concept to production, while elevating the team's understanding of language model capabilities and best practices. Your expertise will be crucial in determining how we can best leverage AI to enhance our solution.
This role offers a unique opportunity to apply deep language model experience in a product focused on transforming how law firms practice the business of law.
Testimonial from a team member: “Long story, but I worked there for maybe 6ish months part time a while back. They offered me full time, but I ended up going to a startup because I wanted to learn some specific technologies + up my skills in Data Science. That job was definitely good for some people, but it wasn’t as remote as they advertised it (had me fly in a lot), and the team was somewhat difficult to work with ;) I ended up starting my own consulting and at the same time CourtDrive reached back out to me (perfect timing). Point I was trying to make was that I went back to work with them because they were so nice to work with. Not super demanding and very open to listening to ideas/suggestions - just a pleasant environment.”
An awesome addition to this would be to illustrate the effect of investor liquidation preferences during an exit. A graph of sale price vs your take would be really helpful for this since it’s nonlinear.
UI suggestion: allow click-drag on percentage boxes. I was tweaking percentages between 4 founders in order to come up with certain amounts post-round and it was a bit trial and error. On mobile it would have been tons easier if I could just nudge the values up and down rather than having to type them all in again.
At CourtDrive.com and our sister website, CourtAPI.com, we are building solutions that enable law firms and other power courthouse website users to become more efficient by automating daily tasks. Conceptually we’re building an ETL system with fuzzy data sources and an API in front of the end results. We’re based in Los Angeles but have a remote team worldwide (Canada, Europe, Armenia to name a few). We’re looking for a Perl developer to help us advance our mission by: building new webservices by scraping state court websites and court emails, building and supporting our CourtAPI solution, and helping keep our modern Perl codebase well oiled. Currently on Perl 5.38.
Testimonial from a team member: “Long story, but I worked there for maybe 6ish months part time a while back. They offered me full time, but I ended up going to a startup because I wanted to learn some specific technologies + up my skills in Data Science. That job was definitely good for some people, but it wasn’t as remote as they advertised it (had me fly in a lot), and the team was somewhat difficult to work with ;) I ended up starting my own consulting and at the same time CourtDrive reached back out to me (perfect timing). Point I was trying to make was that I went back to work with them because they were so nice to work with. Not super demanding and very open to listening to ideas/suggestions - just a pleasant environment.”
At CourtDrive.com and our sister website, CourtAPI.com, we are building solutions that enable law firms and other power courthouse website users to become more efficient by automating daily tasks. Conceptually we’re building an ETL system with fuzzy data sources and an API in front of the end results. We’re based in Los Angeles but have a remote team worldwide (Canada, Europe, Armenia to name a few). We’re looking for a Perl developer to help us advance our mission by: building new webservices by scraping state court websites, building and supporting our CourtAPI solution, and helping keep our modern Perl codebase well oiled.
Testimonial from a team member: “Long story, but I worked there for maybe 6ish months part time a while back. They offered me full time, but I ended up going to a startup because I wanted to learn some specific technologies + up my skills in Data Science. That job was definitely good for some people, but it wasn’t as remote as they advertised it (had me fly in a lot), and the team was somewhat difficult to work with ;) I ended up starting my own consulting and at the same time CourtDrive reached back out to me (perfect timing). Point I was trying to make was that I went back to work with them because they were so nice to work with. Not super demanding and very open to listening to ideas/suggestions - just a pleasant environment.”
I used this once when I was laid off. Worked for about 1/2 my salary to start, but was employed in like a day or two. (And still had 4 weeks of severance coming in). Once i had a bunch of 5* reviews I was able to command more than I was previously earning. (I was pretty Junior at the time).
One caveat is that Contracting time is kinda a career blackhole in that if you go back to employment you're both kinda weird because you're used to contracting, and a lot of managers/interviewers don't really know how to see you're experience when you're doing 3 month contracts, sometimes layered, over the span of years. They don't really get it. (Nor realize that contracting is usually really dense experience, so actually more valuable)
It's best to group all the contract work under a self-employed listing on your resume. Highlight the technical work but also the project managements skills used, the client facing tie and the delivery of work on a given timeline.
I did a few years of contracting/freelance and since i re-wrote my resume it looks better, and seems to be valued the same as fte.
Can you be more specific as to what was the nature of the work you were doing? Was it software dev, analytics, etc and can share a rough range of what your initial $ rate was? Also did you ever represent yourself as an agency?
A couple of friends and I have been doing a casual consulting agency for just under a year and I was thinking of ways to expand our client base and I am looking at Upwork as a possibility.
This might work for some people, but it's not really a substitute for salaried work for me, nor would I hope to stick around long enough for my rates to rise to something approaching the low end of the U.S. FTE market.
